Chat with CEO

Honest answer: there's no first-party Telegram/WhatsApp/email "chat with CEO" surface yet, and until that lands this is the best workaround I've found.

The trick is that you don't actually need a plugin or integration — every shipped local adapter (Adapters Overview (/docs/adapters/overview)) runs a coding CLI that already has a bash/terminal tool enabled by default. Pi Local explicitly enables read, bash, edit, write, grep, find, ls; Hermes Local defaults to all toolsets including terminal; Claude Local, Codex Local, OpenCode, Cursor and Gemini all run with dangerouslySkipPermissions: true for headless Paperclip runs so shell calls don't stall on approval prompts. So whatever CLI you install on the host, the CEO can call it. "Chat with CEO via X" = "install a CLI for X + tell the CEO when to use it."

Concrete picks per channel:

Email — [gogcli](https://github.com/sosedoff/gogcli). Single static binary, does both gogcli messages list --unread and gogcli messages send --to ... --subject ... --body .... Auth lives in ~/.gogcli/ on the host, outside Paperclip. I've been using this and it works well. Telegram — [tdl](https://docs.iyear.me/tdl/) for full-account access (read/reply as you), or just curl to https://api.telegram.org/bot<TOKEN>/sendMessage + getUpdates if "the CEO" is a dedicated bot. WhatsApp — a [whatsmeow](https://github.com/tulir/whatsmeow)-based CLI for personal/multi-device, or curl to the WhatsApp Cloud API if you have a Business account.

Wire any tokens through Paperclip Secrets (/docs/deployment/secrets) and reference them as a secretref in the adapter's env block — same pattern as the Claude Local example (/docs/adapters/claude-local#example) uses for ANTHROPICAPIKEY. Tell the CEO how to use the CLI either through a skill or via instructionsFilePath (Codex Local instructions file (/docs/adapters/codex-local#instructions-file)) — a few sentences is enough: "To email someone, run gogcli messages send …. To check inbox, run gogcli messages list --unread."

One nuance worth flagging — per Why Agents Do Nothing by Default (/docs/guides/concepts/why-agents-do-nothing-by-default), the CEO won't sit there long-polling your inbox or Telegram. For inbound, set up a Routine/heartbeat (/docs/projects-workflow/routines) that runs every N minutes: "Run gogcli messages list --unread. For each new message, file an issue or post a comment, then reply via gogcli messages send." If the channel has webhooks (Telegram Bot, WA Cloud API, SES inbound), even better — point them at the Paperclip API to wake the CEO directly, no polling needed.

Again — workaround, not the final shape. But it's working today with zero plugin code.

Yes — agent chat is being actively worked on, and the shape of it is already documented in the open repo. Two things from the public planning notes worth knowing:

It's intentionally not a generic chatbot tab. The plan doc is explicit (doc/plans/2026-03-11-agent-chat-ui-and-issue-backed-conversations.md): chat will be issue-backed, not a parallel chat object. Sending a message is a comment mutation on an issue, the assigned agent is woken via the existing comment flow, streaming comes from the existing live-run feed, and durable state stays in comments and run history. The framing doc (doc/plans/2026-03-13-features.md) puts it sharply: "V1 communication is tasks + comments only … make the core surface conversational, but keep the data model task/thread-centric."

CEO chat specifically = a conversation-flavored issue assigned to the CEO. Per the plan, that gives you durable history, billing rollup, run linkage, and session continuity for free, because Paperclip already maps taskKey → issueId and persists adapter sessions per task key. Onboarding and weekly review conversations fall out of the same model.

The presentation layer is assistant-ui over Paperclip-owned state and transport — components like IssueChatThread and lab pages (IssueChatUxLab, IssueChatLongThreadPerf) are already in ui/src/, so the foundations are landing in pieces.

What's still on the roadmap (ROADMAP.md lists CEO Chat as ⚪) is the user-facing entry point: a board-initiated CEO conversation issue with conversation-flavored UI treatment. The hard product question being worked through is interrupting an in-flight heartbeat with a synchronous human turn without breaking the issue/billing/session contract — which is why the plan defers multi-thread chat and cross-agent chat until there's real demand.

In the meantime the CLI-in-a-Routine workaround above is the most stable production pattern.

Btw "CEO Chat" is in the official roadmap: <https://github.com/paperclipai/paperclip/blob/master/ROADMAP.md>

And I saw some hooks mentioning commits about this - maybe it will land sooner than later

i have just installed a hermes along with paperclip and onboarded him as another agent, config wise this agent in paperclip is hollow, just a key card for hermes to do operations on the paperclip board. working decently for me\ \ tinkering with a plugin as well to have live chat with any agent, but i am focused more on the paperclip ui.

[mention] are you guys working on it ?

Since I have my instance running on a VPS, I just use the mobile view (it's not perfect, but it's good enough) out of the box!

Alright many thanks I ll try this way