architect
Ask when consequential design choices must be settled before or during implementation — investigates context, compares…
Sprout uses a provider registry and native provider adapters. The runtime resolves model tiers or exact model references before creating LLM requests.
How it fires
How this agent gets triggered: by you, by Claude, or both.
Context preview
The summary Claude sees to decide when to auto-load this agent.
Sprout uses a provider registry and native provider adapters. The runtime resolves model tiers or exact model references before creating LLM requests.
Sprout uses a provider registry and native provider adapters. The runtime resolves model tiers or exact model references before creating LLM requests.
Settings define enabled providers, provider kinds, secrets, defaults, and memory model assignments. Env vars can override runtime model selection without persisting changes to settings.
Source of truth:
Agent `model` can be a tier or exact provider/model. Memory system models use separate purposes: extraction, summary, relationship, consolidation, entityGc, and subcortical. An exact memory model wins when configured; otherwise the purpose falls back to its configured global tier.
Source of truth:
Anthropic, OpenAI, and Gemini use native APIs rather than one flattened schema. Adapters convert Sprout `Request` and `Message` structures into provider calls and convert responses back into Sprout messages, tool calls, finish reasons, and usage accounting.
Source of truth:
Streaming emits normalized events for text deltas, tool call starts/ends, final usage, and finish reason. Agent code can throttle chunks before sending them to the UI.
Source of truth:
Plan requests include provider-specific prompt-cache options when session id and agent name are known. Anthropic uses cache control markers, OpenAI uses prompt cache keys, and Gemini creates explicit cached-content resources for stable system/tool payloads. Cache creation failures are not silently ignored.
Source of truth:
The client can be wrapped with logging middleware. Runtime logs are separate from session event logs and are intended for diagnostics, not replay.
Source of truth:
A self-improving, multi-agent AI system that decomposes tasks and delegates to specialist agents. Sprout is an autonomous coding assistant built on a recursive agent architecture — where every action is a goal-directed delegation to a subagent.
Ask when consequential design choices must be settled before or during implementation — investigates context, compares…
Memory investigation, synthesis, and authorized curation when surfaced memories are insufficient
Systematically diagnose and fix bugs: find root cause before attempting any fix
Observe Sprout's live session behavior and send concise guidance when it is drifting, stuck, or missing an important instruction
Explore and understand unfamiliar codebases, map architecture, and synthesize structural insights
Ask when you need to know what Sprout agents, tools, or MCP servers are available, need a reusable capability plan, or need a new…