Glossary
This glossary defines common AgentOS terms in user-facing language. It is not a runtime design document.
Agent
A named AgentOS identity with defaults such as model, workspace, name, and
description. The built-in main agent is always available.
Read: Durable Agents
Artifact
A file or media output produced by a run, such as an HTML page, report, image, spreadsheet, PDF, or slide deck.
Read: Artifacts and Media
Approval
A human decision required before a sensitive tool action can continue. Approval behavior depends on the surface, permission profile, and tool policy.
Read: Approvals and Permissions
Channel
A messaging integration such as Telegram, Slack, Discord, terminal, or websocket-style clients.
Read: Channels
Compaction
The process of reducing old context in a long session so the agent can continue within the model's context budget.
Read: Compaction and Cache Continuity
Diagnostics
Runtime logging controls used to understand routing, provider behavior, compaction, tool compression, cache behavior, and delivery failures.
Read: Diagnostics and Replay
Gateway
The local server behind the Web UI, channels, sessions, approvals, diagnostics, usage, and RPC clients.
Read: Gateway
Memory
Durable user or project context that can be searched and recalled later without stuffing every old transcript into the active prompt.
Read: Memory
Permission Profile
The chosen tool-access posture for a run, such as restricted, on, bypass,
or full.
Read: Approvals and Permissions
Provider
An LLM backend configured for AgentOS, such as OpenRouter, OpenAI, Anthropic, Gemini, DeepSeek, DashScope, or Ollama.
Read: Providers and Models
Replay
A read-only view of a recorded turn from the decision log. Replay does not re-run tools.
Read: Diagnostics and Replay
Scheduler
The agentos cron feature for recurring and one-time AgentOS runs.
Read: Scheduling
Session
A durable conversation or task history. Sessions can be listed, resumed, exported, aborted, or deleted.
Read: Sessions and History
Skill
A reusable package of task-specific guidance, scripts, or workflow instructions that AgentOS can load when needed.
Read: Skills
Pilot Router
AgentOS's local routing layer for choosing an appropriate model tier per
turn. Every routing strategy — the default pilot-v1 local ML model and the
LLM judge — runs inside it.
Read: Pilot Router
pilot-v1
The default Pilot Router strategy: an AgentOS-native, English-optimized local ML model (MiniLM embeddings + ONNX) that picks the tier on-device with no LLM call.
Read: Pilot Router
Tool Compression
A context-saving feature that keeps large tool results useful while sending a smaller preview to the model.
Read: Tool Compression
Workspace
The local directory a task is allowed or expected to work in. Workspace flags help contain file and shell work.