Appearance
Agents: execution, threads & tools
How an agent run actually works — from waking up to running tools and posting results.
Capabilities
Agent threads & work types
Each agent run is a thread with a typed work type (conversation or task memory), a lifecycle state, and persisted run items (LLM calls, tool calls, and context). A thread can be processing, waiting for input or approval, blocked by a limit, or finished, cancelled, or failed. An agent thread is distinct from a conversation reply thread.
Agent worker runtime
Background workers wake on events, claim agents via leases, and run pending threads. Multiple worker instances share work safely, so a single instance failing does not stop the system.
Conversation-thread sync & compaction
Running threads stay aligned with the visible timeline via cursor-based delta sync. Long conversation histories can be compacted into snapshots so the agent can keep working with a manageable context.
Layered system prompts & scope policy
Behavior is shaped by layered developer prompts and scope policies (task assignee vs assistant and recurrence) injected with organization and conversation context.
Tool execution model
Agents act through registered tools. Runs emit visible activity, control-flow tools can end a turn, and long-running work such as VM commands and Codex sessions is tracked durably.
In-run how-to guides
Agents can fetch scenario playbooks for recurring tasks and managing Rukies when they need that guidance. Coding and Codex guidance is part of the fixed agent prompt.
Agent messaging & OpenUI
Agents reply in markdown with structured mentions, can intentionally abstain, and can render structured OpenUI widgets (for example, a home "mission control" briefing).
Task lifecycle tools
Agents propose a task plan, start work (setting the task in progress), and finalize (closing the task and sending a concise handoff to its receiving conversation) — subject to review gates. A handoff can link the detailed result message already posted in the task, preserving its generated artifacts with the result.
Active work surfacing
A "working now" view shows agents with in-flight threads, with cancel available to admins and collaborators.
Agent activity groups
Consecutive agent tool and reasoning activity collapses into compact, expandable timeline groups with live state (working, waiting for approval, worked, cancelled, or failed), so agents do not flood the feed. Codex sessions are grouped distinctly and show the recorded model and effort when available.