Marketplace

The DorkOS Marketplace is a curated catalog of pre-built agents, plugins, skill packs, and adapters. Install one with a single command and it runs locally, on your machine, under the same permission model as the rest of DorkOS.

What is the marketplace?

The marketplace is the public face of the dorkos-community GitHub organization. The community maintains a registry of vetted packages. A few examples:

• Agents that review your PRs
• Plugins that surface Linear issues in your sidebar
• Skill packs for security auditing or release automation
• Adapters that connect messaging services like Discord

Browse the full catalog at dorkos.ai/marketplace without installing anything.

Every entry in the registry is a real GitHub repository. You can read the source before you install it, fork it, or submit improvements upstream. Nothing is hosted, executed, or transformed by a third party: DorkOS fetches the package directly from its repo and validates its manifest (a small file describing what the package needs and what permissions it wants) against the same schemas as your local extensions.

Installing a package

You can install a package from the command line or from inside DorkOS.

dorkos install code-review-suite

dorkos update code-review-suite     # check for an update
dorkos update --apply               # apply every available update
dorkos uninstall code-review-suite

Browsing in DorkOS

Marketplace is the in-product browse experience. It mirrors the public catalog but adds the install machinery, so you can go from "interesting package" to "running on my machine" without leaving the app.

The browse surface has three sections:

• Featured rail: a curated row of agents the maintainers have highlighted. Rotates monthly, so it's not the same three agents forever.
• Package grid: every package in every registered marketplace, ranked by featured weight and install count.
• Detail sheet: opens when you click a package. Shows the permission preview, install instructions, and related packages.

The install confirmation dialog always shows you exactly what the package wants to do (which files it will write, which network hosts it needs to reach, which permissions it will request) before any state changes. You can deny at any point and DorkOS leaves your installation untouched.

Managing installed packages

A package can be installed in more than one place: globally, and separately on individual agents. When you open the detail sheet for a package you've installed, the Installed panel lists every installation, one row per scope:

• All agents (global): installed globally, active everywhere.
• A specific agent, shown by name: installed only for that agent's sessions. If the same package is also installed globally, the agent row is marked Overrides global, meaning that for that agent, the agent's copy takes precedence.

Each row manages its own installation independently:

• Reinstall re-runs the install for exactly that scope. The confirmation dialog opens already pointed at the same agent (or global), so you never reinstall into the wrong place.
• Uninstall removes just that installation. It asks for a quick confirm first, and the confirmation message names the scope ("Uninstalled flow from Release Bot") so it's clear which copy went away. Uninstalling one agent's copy never touches the global install or any other agent's.

To add the package to another scope (for example, you have it globally and want a pinned copy on one agent), use Install… at the bottom of the panel to open the dialog and pick the new target.

Marketplace sources

The default registry is dorkos-community, but you can add your own. Personal marketplaces are useful for sharing internal packages across a team without publishing them to the public registry.

# Add a marketplace source
dorkos marketplace add https://github.com/my-team/marketplace --name my-team

# List configured sources
dorkos marketplace list

# Remove a source
dorkos marketplace remove my-team

You can also manage sources in DorkOS at http://localhost:4242/marketplace/sources. Sources are merged into a single browse surface: packages from your team's marketplace appear alongside community packages, with the source clearly labeled on each card.

Telemetry consent

DorkOS can report anonymous install events to dorkos.ai to power the public install counts and ranking on the marketplace browse page. This is opt-in: telemetry is disabled by default, and DorkOS will never report anything until you explicitly enable it in settings.

When telemetry is on, each successful install sends a single event containing:

• The package name and marketplace source
• The package type (agent, plugin, skill-pack, adapter)
• The outcome (success, failure, cancelled) and duration
• A random per-install UUID, not tied to you or your machine
• The DorkOS version, for compatibility analytics

No IP addresses, no user identifiers, no package contents, no file paths. The full privacy contract, including what we store, who can access it, and how to opt out, is documented at dorkos.ai/marketplace/privacy.

To enable telemetry:

dorkos telemetry enable --channel install

Or toggle the Help improve the marketplace switch in the Marketplace settings panel.

Submitting a package

The marketplace is community-driven. If you've built something useful (an agent that automates a workflow, a plugin that integrates a new service, a skill pack that codifies your team's conventions), you can submit it to the registry via a PR. See Publishing a package for the full walkthrough. The short version:

dorkos package init my-package --type agent

dorkos package validate

GitHub Actions automatically runs dorkos marketplace validate against your submission. PRs that fail validation cannot be merged, so make sure dorkos package validate passes locally before opening the PR.

Next Steps