Find Commands By What You Want To Do¶
Quick Answer¶
Tell AIOS what you need — it picks the right command. aios init for setup, aios work for daily tasks, aios team for parallel work, aios harness for long overnight runs, and aios verify to check everything before delivery. You describe the task in one sentence; AIOS handles the rest.
Start with setup¶
aios init --all
aios doctor --native --verbose
Run these from the project root. The marker points to .aios/context-db/index.json, and ContextDB recalls relevant sources on demand.
Choose a route¶
| I want to... | Use |
|---|---|
| ask or inspect without changing files | direct |
| make a small, clear local change | guarded |
| coordinate a multi-step or resumable objective | planned / Solo Harness |
| split independent work packages | Agent Team |
| execute ordered phases with gates | Orchestrate |
| understand the decision first | Workflow Policy |
Project memory and search¶
aios memo add "Keep authentication tests strict"
aios memo search "authentication"
node scripts/aios.mjs search "release readiness" --agent codex-cli --json
node scripts/aios.mjs search "browser MCP" --source docs,code --limit 8
ContextDB stores project sessions, checkpoints, exports, and canonical memos locally. Unified search can search memory, plans, docs, and code before a broad read.
Cross-client handoff¶
Run supported clients from the same project when their integrations are synchronized:
claude
codex
gemini
Use explicit memos and checkpoints for important decisions. Shared project storage does not mean every client has identical route or MCP support; confirm with aios doctor.
One long objective¶
aios harness run \
--objective "Draft tomorrow's handoff" \
--session nightly-demo \
--worktree \
--max-iterations 20
aios harness status --session nightly-demo --json
aios harness stop --session nightly-demo --reason "morning review"
aios harness resume --session nightly-demo
Use Solo Harness for the full lifecycle. A dry run creates local journal state but does not test a provider.
Independent parallel work¶
Preview and then run a team only when files and ownership are independent:
aios team --provider codex --workers 3 --task "Implement X and update its tests" --dry-run --json
AIOS_EXECUTE_LIVE=1 AIOS_SUBAGENT_CLIENT=codex-cli \
aios team 3:codex "Implement X and update its tests"
aios team status --provider codex --watch
See Agent Team for governance, history, blocked-job recovery, and evidence.
Staged orchestration¶
Preview a blueprint:
aios orchestrate bugfix --task "Fix X" --dispatch local --execute dry-run
Enable live execution only after preflight and provider checks:
AIOS_EXECUTE_LIVE=1 AIOS_SUBAGENT_CLIENT=codex-cli \
aios orchestrate bugfix --task "Fix X" --execute live --preflight none
Use Orchestrate when phase order and quality gates are more important than parallel breadth. Dry-run is not a live-provider test.
Browser automation¶
Use browser-use MCP over CDP as the default documented route:
aios internal browser doctor
aios internal browser cdp-status
For interactive browser work, launch a visible CDP browser, connect it, read a semantic snapshot or targeted text, then act and verify. Keep authentication walls human-controlled. Playwright MCP remains a compatibility path.
Protect secrets¶
aios privacy read --file .env
aios privacy status
Do not paste .env files, cookies, tokens, private keys, or browser profiles into a model. Redaction is a boundary check, not permission to share every file.
Verify before delivery¶
aios quality-gate pre-pr --profile strict
aios doctor --native --verbose
npm run test:scripts
Select the project-specific tests too. A status line or dry-run output is not a substitute for the command that proves the claim.
Next steps¶
- Workflow Policy - route semantics and continuation.
- ContextDB - memory and unified search.
- Agent Team - parallel operations.
- Solo Harness - resumable operations.
- Troubleshooting - symptom-based recovery.
