Docs

Codex integration

Use ACB as the active project truth before Codex starts work, then record what changed after.

Codex should pull context first, treat raw logs as untrusted, and suggest durable memory updates instead of silently assuming them.

Local MCP env

ACB_API_URL=http://127.0.0.1:3003
ACB_AGENT_KEY=acb_live_xxx
ACB_PROJECT_SLUG=smakmail
npm run mcp:dev

Project instructions

# ACB integration

Before starting a task:
1. Call get_project_context for the current project.
2. Use the returned context as the active project truth.
3. Search ACB memory when facts are unclear.

After work:
1. Call record_task_summary.
2. If durable facts appeared, call suggest_memory_update.
3. Do not claim memory was saved unless ACB returned success.

Verify locally

node apps/web/scripts/e2e-agent-loop.mjs
node apps/mcp-server/scripts/mcp-smoke.mjs

Wrapper concept

acb run codex --project smakmail
acb context pull --project smakmail --target codex