Channels & continuity
An agent is only useful if a human can reach it, follow what it's doing, and step in. The usual failures: the agent lives where nobody is (a separate web app instead of Slack or the ticket queue), there's no real thread to follow (only a transcript the framework owns), and anyone who can type can drive it. OAP reaches agents where teams already work, with durable threads and approvals that live in-channel.
How it works
A channel is a pluggable transport: Slack, a browser tab, a terminal, a webhook. The same agent is reachable through any of them, and the conversation is a real, durable thread — it continues across turns, and everyone in it sees the same plan, the same status, and the same approvals. In Slack you can even @-mention the bot into a thread that's already going, bringing the prior discussion and the people in it into the session. Crucially, the approval cards a human acts on render in the channel, next to the work, rather than in some separate console — and who is allowed to drive or approve is an authorization question, not "whoever can type."
Go deeper
- Slack — the richest surface: the app-provisioning wizard, threads, in-channel interactions, and the App Home hub. (Most of the Authorization guides are shown through Slack.)
- Browser web chat — the built-in
/sessionschat served by the web daemon. - Local terminal — a full-screen TUI (
oap agent chat) with zero external setup. - Continuity & interactions — how threads persist and how approvals, notices, and status render across kinds.