Skip to content
Monopea

Monopea Channels

Where the team and the agent meet.

Threads, tasks and a living canvas per channel — edited by people and the agent side by side, in the same workspace as the files the work is about.

Start freeSee pricing
#launch · threadcanvas · launch planagentAna

—

No proprietary file format

—

A surface, not a tool family

1

Approval gate for every outward action

CH · EU

Stored in Switzerland. Processed in the EU.

The Teams surface, showing a rail of channels with unread counts and a launch channel where two people and two agents answer each other in one thread, with a reply thread open beside it.
Teams · a launch channel where two people and two agents answer in one thread

What you ask → what actually happens

Channels, in the words people type.

Mechanism, not adjectives: each line is what the agent does when you say it.

“Turn this thread into a plan.”

Writes it onto the channel’s canvas, where the team keeps editing it.

“What did we decide here last week?”

Answers from the thread, not from a summary it made up later.

“Make these into tasks.”

Tasks attached to the conversation that produced them, not a list somewhere else.

Capabilities

What Channels does.

01

A canvas per channel

A shared page both people and the agent edit.

02

Threads and tasks together

Tasks stay attached to the conversation that produced them.

03

Notes in markdown

Opened by the same editor the Library uses.

04

Same gate

Anything outward from a channel is a proposal like everywhere else.

Tools the agent calls

Real functions, not a chat reply.

Channels are a surface, not a tool family: the agent works in them through the notes and planning tools.

Channels are a surface, not a tool family: the agent works in them through the notes and planning tools.

Governed

It works on its own. It asks at the door.

Inside the workspace the agent just works. Anything above the one risk threshold you set — and anything that leaves — becomes a proposal with its exact arguments, and waits for you.

How the approval gate works
Proposal · send renewal quotedrafted in the workspacecredentials by {{secret}} onlyabove your threshold → askwaiting…Approveactivity logdispatched

Works with

The rest of the suite, one agent.

Notes

Markdown notes that live in your channels — outlined, extended and ticked off by the agent, opened by the same editor the Library uses.

Explore Notes

Teams

Members, roles and per-project scope, and agent personas with their own brief — the agent can run the workspace admin it is authorised for, and changes to who sees what are proposals.

Explore Teams

Meetings

Transcription runs in the browser, so the audio does not have to leave the machine. Summaries, actions and who-spoke-when come out of the transcript.

Explore Meetings

FAQ

Channels, answered.

Is this a Slack replacement?
It is a place for the team and the agent to work on the same thing — threads, tasks and a canvas next to your files. Keep whatever chat you already use.
Can the agent edit the canvas?
Yes. The canvas is shared: people and the agent edit the same page.
Does the agent need my approval for everything?
No — that would make it a form, not an agent. Work inside the workspace runs on its own; anything above the one risk threshold you set, and anything that leaves the workspace, becomes a proposal with its exact arguments and waits for you.

Hand Channels its first job.

Open a workspace, give the agent a task, and approve what it proposes. Stored in Switzerland, processed in the EU.

Start freeSee every product