Quick Start
Messages vs Run Output
Every agent run producesoutput_data — visible in the Activity Feed. But not every run output is worth surfacing as a notification. A Discord bot responding to a user produces output, but showing one side of that conversation as a message is noise.
Messages are intentional. You decide what’s worth surfacing by calling message.send() explicitly. This separates “agent did work” (Activity Feed) from “agent has something to tell you” (Messages).
SDK Usage
- Python
Parameters
Levels
API Reference
All endpoints requireAuthorization: Bearer <api_key>.
Send a message
List messages
Response:
Workspace-scoped listing
GET /messages, scoped to a specific workspace.
Delete a message
orch-hq Display
Messages appear in the Messages panel (sidebar button) in orch-hq:- Level dot (colored by severity)
- Agent name, title, and body preview
- Relative timestamp (“2m ago”, “1h ago”)
- Click to expand full body
- Polls every 15 seconds for new messages
Examples
Morning briefing agent
Error monitor
Deployment notification
Next Steps
Tasks
Create and manage tasks from your agents
SDK Reference
Full SDK documentation
orch-hq
The desktop app where messages appear