Skip to content

Core concepts ​

TermMeaningExample
AgentA task executor with a model, instructions and toolsSupport assistant
ProfileNamed model and authentication settingsdefault, deep-analysis
WorkflowMattermost routing settings and agent instructionsAssistant for a support channel
SessionConversation context and working environmentHandling one ticket
RunOne assignment within a sessionPrepare the initial reply
ClarificationNew information for a running agentAdditional error details
SandboxEnvironment containing files and toolsCodex in AgentBox
TemplatePrepared sandbox softwareCodex, Python and a helpdesk CLI
HookPreparation or finalization scriptPublish a reply file
NamespaceIntegration or process labelhelpdesk
OrpheusService that creates sessions and executes runsOrpheus API and worker
SpaceSeparate service and web interface for recurring tasksMorning reports
Space schedulePrompt, repeat rule and agent settingsReport at 10:00 on weekdays
OccurrenceA due schedule instance with dispatch and run informationMonday’s report

A session allows one run by default. For conversations, set allow_multiple_runs: true at creation so subsequent runs retain context. Runs execute sequentially, and clarifications during execution work in either mode. Configuration is captured when a session is created. Editing a profile does not reconfigure an existing conversation.

Reusable sandbox context remains available until the paused sandbox is deleted after its retention period. Session history remains readable after deletion.

Lifecycle and states · Continue a task