Config file
optamus.toml in the repo pins model, parallelism, and tool allowlists for the whole team.
Your terminal, agent-powered.
One command starts a run. Flags, exit codes, and JSON output make it scriptable from the first install.
zsh
$ optamus run "migrate the billing tests to vitest"
▸ Reading workspace · 42 files
▸ Running suite · 38 passed, 2 flaky
✓ Patched src/billing/*.test.ts (+214 −188)
✓ All green — run/1a2b finished in 2m 04sScriptable by default
Everything the CLI shows you is a flag away in machine form. Pipe it, branch on it, or drop it into a Makefile.
- Run tasks from flags, stdin, or a config file
- Emit NDJSON for pipelines with --json
- Exit codes that mean what you think: 0 settled, 1 failed, 2 interrupted
zsh
$ optamus run "triage open issues" --limit 20 --json | jq '.state'
"completed"At home in CI
Install the CLI in a job, point it at a checkout, and let it open a pull request. The same agent you run locally — same flags, same output.
- One-line install on Linux runners
- Artifacts: patch file, log, and run receipt
- Works with any CI that can run a shell step
.github/workflows/agent.yml
- name: Run agent
run: |
curl -fsSL https://optamus.cloud/install.sh | sh
optamus run "fix the failing e2e tests" \
--patch out.patch --receipt run.json
- name: Open pull request
uses: peter-evans/create-pull-request@v6
with: { patch: out.patch } Details
Flags you would expect.
Parallel runs
Fan one command into four runs, each in its own worktree, since 1.4.
Deterministic exits
Settled, interrupted, failed — three codes, easy to branch on.
Same agent as Desktop
Start in the shell, watch it in the app. The run is the same run.
GitHub GitLab Docker TypeScript
Ready when you are.
Install the desktop app or the CLI, run one command, and review the first diff.