- • The AgentLoop is the central orchestrator — it mediates all component interactions
- • Each loop iteration: prompt LLM → parse tool_calls → execute → collect results → re-prompt
- • Activations make ownership duration visible across the timeline
- • Three LLM APIs (OpenAI / Anthropic / Gemini) are abstracted behind a single interface
- • Emphasis arrows mark the main request path; returns are quieter
- • The same loop pattern applies regardless of which LLM backend is selected
- • ToolShell provides file sandbox, code exec, and CLI tools without extra installs
- • Memory layer uses Qdrant semantic search + SQLite backup for persistent cross-session recall
- • Both augment the LLM context before the next API call
- • Conversation storage is non-blocking (dashed arrow)
- • It happens after the user-facing response completes
- • Separates observability from user latency