Plugins and marketplace

Add tools and skills with plugins

Add capabilities from the first-party Codewhale catalog, a GitHub repository, or a tarball. Nothing runs until you read the manifest and trust it.

Browse the Codewhale catalogPlugin authoring guide

Control apps with Computer Use

Computer Use is a preview. The agent reads app controls, types and clicks, and records actions; Windows, Linux and HarmonyOS backends remain experimental and source-only.

/plugin marketplace install codewhale computer-use

36 MCP tools: observation, actions, screenshots and zoom, keyboard and pointer, clipboard, recording, browser control over CDP, window frames, the installed-app catalog, sessions and computer switching.

Computer Use
Works in the background
On macOS the agent drives a selected app without moving your pointer or taking focus, so you keep using the machine. Foreground control is a separate, explicit grant.
Read app controls
The accessibility tree (macOS AX, Windows UIA, Linux AT-SPI) returns controls, values, and advertised actions, so a text-only model can drive an app without screenshots.
Screenshots and local text recognition
Screenshots and zoom feed compatible vision models. On macOS, local OCR reads window text on-device with no remote service or vision model.
Connect remote computers
Control the local machine, registered SSH hosts (the remote agent installs itself), or HarmonyOS devices over hdc. Every receipt names the computer it happened on.
Manage system permissions
Accessibility and Screen Recording grants stay in System Settings under your control. The agent tells you once what is missing instead of opening dialogs.
Stop when an action cannot be verified
Stale observations, unexpected foreground changes, and unavailable capabilities refuse with a receipt instead of guessing. Each task owns its session; stopping releases every held input.
Automate a separate browser profile
The agent drives a Chromium-family browser over the DevTools protocol in its own profile, clicking by CSS selector or page pixel. It never attaches to your profile, tabs, or logins.
Preview, stop and replay sessions
A live preview shows the bound app while a session works, and list_sessions names every live session. The stop switch halts input, trajectories record every call (refusals included) for replay, and a launch-time grant fixes what a session may call.

Browse Codewhale plugins

An offline snapshot of the Codewhale catalog ships with the terminal, so browsing never fetches or runs anything. Install from it with one command.

/plugin marketplace list

Catalog source: github.com/codewhale-hq/codewhale-plugin-marketplace. A local catalog named codewhale takes precedence over the bundled snapshot.

Install from a repository, folder, or tarball.

Point /plugin install at a directory, a repository, or a tarball. The fetched tree must hold exactly one bundle root: a plugin.json, a compatible kimi.plugin.json or .claude-plugin/plugin.json, or a legacy plugin.toml.

  • GitHub repositoryFetches an archive of the default branch, the same mechanism the marketplace catalog uses./plugin install github:owner/repo
  • Local directoryCopied from disk. The fastest loop while authoring your own bundle./plugin install ./path/to/bundle
  • Tarball URLDownloads the archive directly under the per-domain network policy. An unknown host is refused until you allow it./plugin install https://example.com/x.tar.gz

Review and enable a plugin

Every bundle lands disabled and untrusted. Review the manifest and declared capabilities, then trust and enable it. An update with changed bytes requires review again.

  1. Review

    /plugin show <name> prints the manifest, declared capabilities, and install receipt, including the source and bundle selector.

  2. Trust

    /plugin trust <name> marks your decision. Official catalog provenance grants no execution or network permission on its own.

  3. Enable

    /plugin enable <name> activates the bundle. Plugin-contributed MCP servers run under namespaced <plugin>-<server> identities with the stricter boundary.

Downloads are tarball-only with a size cap and no symlinks; traversal, ambiguous roots, and changed plugin identities are rejected. /plugin suggest ranks installed and catalog bundles against a task without installing anything.

Command reference

Run the full lifecycle from the terminal:

Plugin authoring guide
/plugin marketplace list
/plugin marketplace show codewhale
/plugin marketplace install codewhale <name>
/plugin install github:owner/repo
/plugin show <name>
/plugin trust <name>
/plugin enable <name>
/plugin update <name>
/plugin suggest <task>