u/Fine_Cup2674

Hi everyone, I’m building Manyfold and looking for a few people to test it. Recently, one of features I created is for "channels".

Manyfold lets you use the same coding agent from apps like Slack, Telegram, Discord, GitHub, Linear and more... You can start a task in one place and continue it somewhere else, while keeping the same session, files, permissions and history. 3 steps for connecting it.

I’m especially looking for people already using Claude Code, Codex, Gemini CLI or Hermes, especially if you want to run tasks while away from your laptop.

The test should take around 15 minutes:

1. Connect one agent to two channels
2. Start a small task in the first channel
3. Continue it from the second channel
4. Try a group mention or approval step

I’d love honest feedback on:

• Is this useful for you?
• Was the setup easy to understand?
• Did the session and context carry over correctly?
• Were permissions and approvals clear?
• Would you use this for a real project?
• What felt confusing or missing?

Try it here: Manyfold

Hey all,

I am building Manyfold and want to have some beta users. I keep seeing people use Claude Code, Codex, Gemini CLI and other coding Agents in the terminal, then connect separate bots to Slack, Telegram or Discord. It works at first, but once you use an Agent seriously, the hard part is not connecting another app. The hard part is keeping the Agent’s state consistent.

Here are a few things I keep coming back to.

1. The Agent should be separate from the channel. Slack, Telegram, GitHub and Linear should be different ways to reach the same Agent, not completely separate bots with separate memory.
2. Each conversation should have its own session. A Slack thread about a bug should not get mixed with a Telegram conversation about research. Chats, groups and threads need their own scope.
3. The Agent should keep the shared context. History, files, skills, permissions, model settings and usage should belong to the Agent. If I upload a screenshot in Slack, I should still be able to use it when I continue the task from Telegram or the workspace.
4. Group chats should be mention based. The Agent probably should not receive every message in a busy team channel. It should join when someone mentions it. That keeps the context cleaner and avoids wasting tokens.
5. Usage and permissions matter as much as the model. I want to know how many tokens a session used, how long it ran and what it cost. I also want a clear difference between reading a message, preparing a change and actually sending or executing something.
6. The real test is switching surfaces. If I start a task in Slack, check it from my phone and later open it from GitHub or Linear, the Agent should still know what happened without making me explain everything again.

This is the model I’m building with Manyfold. One Agent can connect to Slack, Telegram, Discord, WhatsApp, Lark, GitHub and Linear, while keeping the sessions, history, files and usage connected to the Agent.

I’m curious how other people are handling this. Do you think this is useful? LMK!

One agent can plan. Another can research. A third can turn the result into something a team can use. The interesting part of a multi-agent workflow is not simply adding more agents. It is giving each one a clear role and keeping the work connected from start to finish. Manyfold brings agents, models, tools, and context into one workspace so they can work together instead of becoming another set of isolated chats.

How would you split work across your first agent team?

One workspace. Every framework.