@meego-harness/claude-code-worker

Standalone worker bridge that runs tasks through the Claude Code CLI and connects to a meego-harness worker server.

Commands

meego-claude-code-worker setup
meego-claude-code-worker list
meego-claude-code-worker doctor
meego-claude-code-worker start --worker <workerId> [--tmux] [--claude-code-shell]
meego-claude-code-worker stop --worker <workerId>
meego-claude-code-worker stop-all
meego-claude-code-worker enable --worker <workerId>
meego-claude-code-worker disable --worker <workerId>
meego-claude-code-worker uninstall --worker <workerId>

Use --claude-code-shell when claude is only available through the user's interactive shell configuration.

Setup Inputs

Non-interactive setup accepts:

meego-claude-code-worker setup \
  --server-url ws://127.0.0.1:3000/workers \
  --email [email protected] \
  --worker claude-code-worker-1 \
  --capability-summary "Handles TypeScript work" \
  --workspace /path/to/workspace \
  --permission-preset default \
  --model sonnet \
  --effort high

--permission-preset maps to Claude Code permission modes:

| Preset | Claude Code mode | | --- | --- | | safe | plan | | default | acceptEdits | | full-access | bypassPermissions |

Task Metadata

| Key | Type | Description | | --- | --- | --- | | repo | string | Repository directory under the configured workspace or an explicit repo mapping | | claudeCodeEffort | string | One of low, medium, high, xhigh, max | | claudeCodePlanMode | boolean | Prepends a planning-only preamble on the first message in that context |

Operational Notes

• The worker server treats this bridge as a normal worker.
• One Claude Code session is reused per harness contextId.
• Task cancellation aborts the active Claude Code process when possible.
• Repo routing follows the same rules as codex-worker: absent repo uses the default workspace, empty mappings infer <workspace>/<repo>, and non-empty mappings require an explicit match.