open/agent-builder
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity Actions

docs(plans): create session blueprints for Agent Factory execution

Browse source 
8 session blueprints covering all 27 steps across 3 waves:
- Session 1: Foundation (rename + commands, Steps 1-5)
- Session 2: Skills and templates (Steps 6-7)
- Session 3: OpenClaw patterns (memory/heartbeat/proactive/cron, Steps 9-12)
- Session 4: Paperclip patterns (context/goals/budget/governance/org-chart, Steps 14-18)
- Session 5: Self-learning (feedback/optimization, Steps 20-21)
- Session 6: Integration (Docker/transfer/5 more domains, Steps 22-24)
- Session 7: Skill updates (memory/autonomy/orchestration/governance/MCP refs, Steps 13,19,25)
- Session 8: Finalization (build command integration + v1.0, Steps 8,26,27)

Also updates plan assumptions table with verified findings.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
Kjell Tore Guttormsen 2026-04-11 11:21:17 +02:00
commit 1a776bdeb2
9 changed files with 8885 additions and 8 deletions
Download patch file Download diff file Expand all files Collapse all files

17
.claude/plans/ultraplan-2026-04-11-agent-factory.md
View file

@ -993,16 +993,17 @@ graph TD
| Low | Docker template may need updates for newer Claude Code versions | `scripts/templates/docker/` | Docker deployment breaks | Dockerfile uses `node:22-slim` and `npm install -g` which auto-updates |
| Low | Domain templates may not match all user domains | `scripts/templates/domains/` | Users need custom templates | 10 templates cover common domains; builder agent can create custom templates |
## Assumptions
## Assumptions (VERIFIED 2026-04-11)
| # | Assumption | Why unverifiable | Impact if wrong |
|---|-----------|-----------------|-----------------|
| 1 | Anthropic billing API exists and is accessible with standard API key | No docs found confirming exact endpoint | Budget tracking falls back to token-based estimation; budget-hook.sh needs manual cost configuration |
| 2 | `/schedule` trigger interface is stable enough to build on | Claude Code internal API, no stability guarantee | Heartbeat templates still work with cron/launchd/systemd; `/schedule` is optional deployment target |
| 3 | Docker deployment should use docker-compose.yml with Dockerfile | Spec assumption, no user confirmation | Minor: can generate either format; both templates provided |
| 4 | `claude --resume` with custom session IDs works for isolated agent turns | Based on CLI docs, not tested with custom session key formats | agentTurn template may need session ID format adjustment |
| # | Assumption | Status | Finding | Impact on plan |
|---|-----------|--------|---------|----------------|
| 1 | Anthropic billing API exists and is accessible with standard API key | **PARTIAL** | Usage & Cost API exists at `/v1/organizations/usage_report/messages` and `/v1/organizations/cost_report`. BUT requires Admin API key (`sk-ant-admin...`), not standard API key. Only available for organizations, not individual accounts. CLI has `--max-budget-usd` flag for print-mode budget caps. | budget-hook.sh MUST use token-count estimation as primary method. Admin API integration is optional, org-only. Template README should document this limitation clearly. CLI `--max-budget-usd` is a simpler alternative for headless runs. |
| 2 | `claude --resume` with custom session IDs works for isolated agent turns | **WRONG** | `--session-id` requires a valid UUID. Custom formats like `agent:name:turn:123` are rejected. `--name` flag sets human-readable session names. `--resume` accepts session names for fuzzy search. | agent-turn.sh template MUST use `--name "agent:{{AGENT_NAME}}:turn"` + `--resume "agent:{{AGENT_NAME}}:turn"` pattern instead of custom session IDs. For deterministic UUIDs: `python3 -c "import uuid; print(uuid.uuid5(uuid.NAMESPACE_DNS, 'agent:name:task'))"`. |
| 3 | `/schedule` trigger interface is stable enough to build on | **CONFIRMED with caveats** | `/schedule` is GA, available to Pro/Max/Team/Enterprise. Runs on Anthropic cloud from GitHub clone (NOT local files). 1-hour minimum interval. Desktop scheduled tasks (`/schedule` in Desktop app) are the local alternative with 1-minute minimum and local file access. MCP connectors available for cloud tasks. | Deploy command must distinguish: `/schedule` = cloud (needs GitHub, no local files), Desktop scheduled tasks = local machine, cron/launchd/systemd = traditional local. Heartbeat templates are for local/VPS/Docker only; `/schedule` has its own mechanism. |
| 4 | Docker deployment should use docker-compose.yml with Dockerfile | **CONFIRMED** | Well-established pattern. Official Anthropic devcontainer reference exists. Docker sandboxes documented for safe autonomous operation. `--dangerously-skip-permissions` for unattended operation inside containers. Key security: `security_opt: no-new-privileges:true`, never mount Docker socket, mount only specific project folders. | docker-compose.yml template should add `security_opt: [no-new-privileges:true]`. Dockerfile approach is correct. Add Docker socket warning to README. |
**WARNING: Plan has 4 unverified assumptions -- review before executing.**
**All 4 assumptions verified. 1 was wrong (session IDs), 1 was partial (billing API), 2 confirmed.**
Sources: [CLI Reference](https://code.claude.com/docs/en/cli-reference), [Scheduled Tasks](https://code.claude.com/docs/en/web-scheduled-tasks), [Usage & Cost API](https://platform.claude.com/docs/en/build-with-claude/usage-cost-api), [Docker Blog](https://www.docker.com/blog/docker-sandboxes-run-claude-code-and-other-coding-agents-unsupervised-but-safely/)
## Verification