Repository navigation
Commander v0.2.0
·
133 commits
to main
since this release
Immutable
release. Only release title and notes can be modified.
Commander v0.2.0
Commander can now build agents, install published packages on demand and create
missions through Admin, MCP or the HTTP API.
New
- Builder agent: generate agents with Codex, verify their action contracts and download the source. Optionally publish and release them on GitHub.
- Spawner agent: install compatible GitHub packages as native processes or Docker containers. Supports pinned versions, stable releases, private repositories and private GHCR images.
- Agent catalog: discover available agents through MCP, or install directly from a GitHub repository URL.
- Mission builder: select available actions, define capabilities before an agent exists, configure optional actions and inspect saved missions as JSON.
- Managed secrets: encrypted persistence and delivery to agents, with masked Playground and Admin forms that keep values outside the model conversation.
- Task affinity: the
same-agentrule keeps related actions on one agent instance. - Execution checkpoints: actions can persist facts before external side effects and inspect them when handling retries.
Playground and Admin
- Admin UI is embedded in release binaries and Docker AIO.
- Completed operations link directly to their Admin details.
- Improved API-key retries, wheel/trackpad scrolling, text selection and terminal copying.
- Shared progress reporting keeps API, MCP, Playground and Admin consistent.
Fixes and maintenance
- Improved Windows filesystem messaging and test reliability.
- Updated vulnerable frontend dependencies.
- Replaced web/browser-agent integration dependencies with the lightweight example agent.
Upgrading from v0.1.0
- Replace mission root
objectivewithobjectives: ["Your objective"]. Step-levelobjectiveremains unchanged. - Replace action requirement field
secretwithsensitive. Managed secret requirements usekind: "secret". - Update MCP clients to read task counts and pending work from
progress. - Default deployments now start builder and spawner. Install web and browser agents when needed; they are maintained in separate repositories.
- Custom Go integrations must support the new mission creation and execution checkpoint interfaces.