Reaching me from a chat app you already live in

A channel hands me a task or a question from a chat app you already live in — a Telegram chat, a team channel — and I work the task and reply in the same thread.

You message me the way you’d message a colleague, and I come to where you already are.

‹!-- ADAPT:

harperOS connects Gmail, Calendar, and Drive — no chat platform is wired today, so no channel is live in this workspace yet.

This module is the reference for when one is connected: what a channel is, how I behave in it, and the governance that applies.

The wider framework supports Telegram, Discord, and iMessage natively.

Slack and other workplace channels reach me through a custom build.

When a channel does go live, asking me which channels are connected is the final word for this workspace.

--›

For a channel to work, I run on a server, not your machine

In the main app, I run on your computer and stop when you close the laptop.

A channel needs something listening around the clock, so a channel-reachable me lives on a server — the always-on home.

That’s what lets a message reach me at any hour with your machine closed: the same me in two homes, and a channel depends on the always-on one.

Ask me which channels are connected

The set of connected channels moves fast and is set per workspace, so rather than list it here and let it go stale, ask me and I read the live state.

What’s wired up is declared in the workspace’s channel mappings, and I check them when you ask, so the answer is current.

Read it before you rely on a channel — what’s live this week is the final word, not what any module says.

Say "what channels are connected, and who’s reachable through each one?"

The way channels are declared and governed is set out in the channel integration architecture and the channel hygiene operating model — the canon for it ships with the OS once a channel platform is connected here.

Today you can reach me through the connected chat apps

In this workspace no chat channel is connected yet — Gmail, Calendar, and Drive are the wired surfaces, so for now I’m reachable in the main app and over email, not from a chat app.

When a channel platform is set up, the messaging apps the framework supports natively come first — Telegram, Discord, and iMessage as of early 2026.

Set a channel up once, then message it like any other chat.

From a Telegram chat: "Pull my brief for today and flag anything urgent."

Slack and other workplace channels reach me through a custom build

As of early 2026, Slack isn’t wired up the way the messaging apps are — it arrives through a custom integration layered on the standard framework, not out of the box.

The deeper aim: standard channel support treats a channel mostly as a chat pipe, while the aim here is to route your real tools — your Gmail, your Calendar, your Drive — through the channel itself, so a message in a Telegram chat or a team channel triggers the same real work you’d get in the app.

That deeper routing is the edge being built, not a finished feature, and no channel is live in harperOS yet — so ask me to confirm what’s connected before you lean on it.

The habit: the app for deep work, a channel for reach

When you’re heads-down, the main app is home.

When you want me from your phone or a team channel — a quick ask, a handoff, a check while you’re away — a channel is the door.

Set it up once, ask me what’s live to confirm, and message me from where you already are.

The one thing to remember

A channel brings me to the chat app you already live in, and it works because a copy of me runs on an always-on server.

Ask me what’s connected in your workspace, then message me from there for a quick ask — and keep the main app for deep work.

Sources

• https://docs.claude.com/en/docs/claude-code — the main surface, with the channels capability layered on top of it.
• claudefa.st and mindstudio.ai channel guides (verified 2026-05-23) — native channel support for Telegram, Discord, and iMessage as of early 2026, with the framework built to add more.
• github.com/chenhg5/cc-connect (verified 2026-05-23) — Slack and other workplace channels reach me through a custom integration layered on the framework, not native support.
• This workspace runs on Google Workspace; the harperOS connection carries Gmail, Calendar, and Drive — no chat platform is wired today, so no channel is live here yet.
• Verify the connected surfaces against CLAUDE.md and .mcp.json.
• The channel mechanism — channel modes declared in the workspace channel mappings, governed by the channel hygiene operating model — ships with the OS canon once a channel platform is connected to this workspace.