Memory #104 CURRENT
Conductor Claude Code Integration Three-phase plan — CLI sub-agents, MCP bidirectional bridge, UI — with reminders for Option C (subagents) and Option D (Managed Agents API) Conductor integration with Claude Code approved 2026-04-12. Three deliverables: 1. **integrations/claude_live.py** — CLI `-p` mode sub-agent executor (Option A) 2. **MCP bidirectional bridge** — `conductor_request_agent` tool in existing MCP server (Option B) 3. **UI for the Conductor** — user interface (design TBD) **Why:** Conductor needs an execution layer for sub-agent tasks. Claude Code is the natural fit given existing MCP infrastructure. **How to apply:** Every Claude Code sub-agent gets ephemeral prime, authority C₂², 4-tick TTL. Results attested by clock before acceptance. **Reminders for future sessions:** - After A+B are working: suggest **Option C** — `.claude/subagents/` definitions for domain-specific delegates (health, finance, etc.) - After wallet integration lands (Phase 1): suggest **Option D** — Managed Agents API for cloud-scale async orchestration - UI decision needed: web-based (Flask/FastAPI + HTMX?) vs Electron vs terminal TUI — [project_conductor_claude_integration.md]
| Composite | 10C972FF464251F1DF |
| Project prime | 13 |
| Domain prime | 59 |
| Type prime | 67 |
| Importance | 0.343295 (ACTIVE) |
| Decay epoch | 0 |
| Created | 2026-05-04 15:46:49 |
| Valid from | (unset) |
| Valid to | NULL — still believed true |
Outgoing Edges
No outgoing edges.