Skip to content
Supen Docs

Use Supen Through Channels

Channels let you reach the same Supen runtime from the places where your team already talks. They are best for lightweight interaction, quick approvals, and keeping work visible without turning chat into the main control surface.

For developers extending Codex-style work to mobile and channel surfaces, Supen treats channels as another presentation layer over the same task/thread runtime. The web UI, CLI, and channel replies should point at the same task history, tool activity, usage data, and approval state instead of creating a separate bot-only workflow.

What channels are good for

Section titled “What channels are good for”
  • checking progress without opening the platform
  • approving or continuing work from chat
  • keeping long-running sessions visible to the rest of the team
  • following up on tasks that already exist in Supen
  • bringing Codex task updates to mobile-first chat clients

Developer extension boundaries

Section titled “Developer extension boundaries”
  • Use channels for task updates, short replies, approvals, and follow-up prompts.
  • Keep configuration, environment setup, template publishing, and detailed debugging in the web UI or CLI.
  • Preserve opaque channel thread identifiers when routing messages through the gateway; do not reinterpret them as local task ids.
  • Render replies from the same stored task/thread events that power the web UI, including tool activity, final answers, and usage summaries.
  • Require an explicit human review step before publishing generated release notes or other public-facing content.

Pair a channel to Supen

Section titled “Pair a channel to Supen”

The CLI exposes the pairing flow:

Terminal window
supen pairing list
supen pairing pair

If you already have a pairing code, you can approve it directly:

Terminal window
supen pairing approve <code>

There is also a shortcut form:

Terminal window
supen pair <code>

Once paired, the channel can route lightweight interactions to the right agent and session context.

Remove a stale channel binding

Section titled “Remove a stale channel binding”

If a chat identity should no longer be connected:

Terminal window
supen pairing unbind <chat_jid>

What still belongs in the platform or CLI

Section titled “What still belongs in the platform or CLI”

Do not treat channels as the main place to configure Supen. Use the platform or CLI when you need to:

  • launch or switch spaces
  • inspect runtime health
  • manage detailed capabilities
  • edit automations carefully

Channels work best when they extend an existing Supen workflow instead of replacing it.