Agentic AI
The parts of an LLM agent: tool protocols, the agent loop, context and memory, multi-agent orchestration, sandboxing and evaluation.
Tool protocols
How a model calls code and how the output stays machine-readable.
Tool calling
lowThe model emits a structured call (id, name, JSON arguments) instead of prose; your code validates, runs it and returns a result tagged with the same id.
model context protocol
Planned.
Constrained decoding
lowForce LLM output to match a regex, JSON schema or grammar by masking, at every step, the tokens that would leave the language.
The agent loop
Observe, think, act, repeat, inside a finite context window.
agent loop
Planned.
Context window management
lowKeep an agent's growing history inside the model's window by truncating, clearing and summarizing old turns in a cheap-to-lossy ladder, at turn boundaries.
Prompt caching
lowReuse the attention keys/values of a repeated prompt prefix, so an agent's growing context is prefilled once and later turns pay only for the new tokens.
task planning
Planned.
edit application
Planned.
Tool retrieval (selecting tools for a request)
mediumIndex tool descriptions, filter by the caller's permissions, rank against the request and put only the top few definitions in context, in a stable order.
Human-in-the-loop approval
mediumClassify each proposed action as auto, ask or deny; park asks as durable pending records a human approves, edits or rejects, executing once, with timeouts that deny.
Memory and retrieval
What the agent knows beyond the current window.
agent memory
Planned.
code context retrieval
Planned.
Memory consolidation
mediumPeriodically merge near-duplicate memories, resolve contradictions, decay the unused and cap the store, so an agent's long-term memory stays small, current and cheap to search.
citation grounding
Planned.
schema linking
Planned.
Multi-agent orchestration
Splitting work across agents and merging the results.
subagent orchestration
Planned.
agent workflows
Planned.
Model routing and cascades
mediumSend each request to the cheapest model that will answer it well enough, by rules, a learned router, or a cascade that escalates from small to large on low confidence.
semantic cache
Planned.
Safety and operations
Keeping agents contained, honest and measurable.
agent sandboxing
Planned.
Prompt injection defense
mediumTreat every untrusted string as data, track where values came from, and make tool calls and rendered output depend on provenance, not on what the model says.
agent evaluation
Planned.
agent tracing
Planned.
user simulation
Planned.
Computer use
Seeing and driving browsers and desktops.
accessibility tree
Planned.
gui grounding
Planned.
input event synthesis
Planned.
browser automation protocol
Planned.
screen capture
Planned.