Agents & Runtime

What an agent is made of

Every agent has: a unique name (lowercase, digits, hyphens), an optional short alias, a runtime + model + effort, a project (or global if not tied to one), its own instruction/system prompt, a permission mode, and the settings on the Reliability page (autoboot, hang_threshold_minutes, auto_sleep_enabled, auto_sleep_minutes).

Field	Meaning
alias	A second, short address (e.g. sa); always resolved to the main name when sending/receiving
instruction	The hand-written part; mixed with the runtime’s template to build the system prompt when the agent starts
Template changes	After a runtime template update, run /agent resync <name> (or /agent resync --all), then /agent restart <name>
permission_mode	An unattended agent needs a mode other than the default — the default (manual) stops at the first tool approval

Supported runtimes

Runtime	Supports tools	Default model	Available efforts	Minimum version
claude	yes	claude-haiku-4-5-20251001	low, medium, high, xhigh, max	2.1.274
agy	no	gemini-3.6-flash-low	low, medium, high, max	1.2.11
codex	—	—	—	—

Model and effort are a suggested menu, not an allowlist: a model outside the list is still accepted, with a warning.

Lifecycle

Command	Effect
restart <name>	Stop then boot a fresh session, seeded with a summary of the session that just stopped — works even if the agent hangs
rotate <name>	Like restart but the new session is completely blank
resync <name> | --all	Re-mix the prompt when the runtime’s template changes
set <name> <field> <value>	Updates an agent setting — see the field list on Chat commands

Hub MCP tools

Agents access platform integrations with Hub MCP tools for dynamic skill discovery and remote execution.