Skip to main content
Agents can send messages to you via the SDK. Messages appear in the Messages panel in orch-hq and are accessible via the API. Use them for daily briefings, error alerts, completion notifications — anything your agent wants to tell you.

Quick Start

That’s it. The message appears in your orch-hq Messages panel immediately.

Messages vs Run Output

Every agent run produces output_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

Parameters

Levels

API Reference

All endpoints require Authorization: Bearer <api_key>.

Send a message

Response (201):

List messages

Response:

Workspace-scoped listing

Same query parameters as 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

Messages are additive. If your agent already sends to Telegram or Discord, add message.send() alongside your existing delivery code — one extra line puts the message in orch-hq too.

Next Steps

Tasks

Create and manage tasks from your agents

SDK Reference

Full SDK documentation

orch-hq

The desktop app where messages appear