@meego-harness/mara-worker
v0.8.0
Published
Standalone Mira CLI worker bridge for meego-harness WorkerServerSDK
Readme
@meego-harness/mara-worker
Standalone Mira CLI worker bridge for meego-harness.
It logs into a WorkerServerSDK endpoint as a coder worker, executes tasks through the local Mira installation, and reuses one persisted Mira conversation per harness contextId.
What You Need First
Before installing this package, make sure all of the following are already true:
- Node.js and
pnpmare available. - Mira CLI is already installed separately and
mira --helpsucceeds in your shell. python3is available, because the bridge invokes Mira's local Python implementation.- A target worker server is already running.
- You already have an absolute workspace directory on disk.
Command Summary
meego-mara-worker setup
meego-mara-worker start --worker <workerId> [--tmux]
meego-mara-worker stop --worker <workerId>
meego-mara-worker stop-all
meego-mara-worker enable --worker <workerId>
meego-mara-worker disable --worker <workerId>
meego-mara-worker uninstall --worker <workerId>Install
pnpm add @meego-harness/mara-worker
pnpm exec meego-mara-worker setupRuntime Model
- First message in one harness
contextIdstarts a new Mira conversation and persists itsconv_id. - Later messages in the same context reload that saved conversation so Mira can continue from prior context.
- Repo routing is driven by
task.metadata.repo. - Remote MCP tools and remote skills are disabled inside worker mode to keep routing deterministic and focused on local coding work.
- Structured project-node output supports
completedandinput_requiredJSON responses, with one retry when the first response is invalid.
Local Files Written By This Package
Config file:
~/.meego-harness/mara-worker/<workerId>.jsonPer-context state file:
~/.meego-harness/mara-worker/<workerId>.state.json