#Alternatives to Telegram and Discrod

1 messages · Page 1 of 1 (latest)

smoky sierra
#

Hello?

#

I currently use both telegram and discord. I like the way discord can have separate channels for my different agents but I don't like that when I'm working on coding it doesn't all show in a single chat message. Copy and paste is difficult. Telegram is better but it doesn't have many organizing options. Any suggestions?

naive baneBOT
#

Discord vs Telegram is basically a tradeoff between structure (Discord) and clean transcript / copy-paste (Telegram). A few setups that tend to work well:

1) Use Discord for organization, but keep a single “canonical log” elsewhere

For coding sessions, have the agent produce output as:

  • a single markdown “run log” (one file per task), or
  • a patch / diff, or
  • an attached file (so you can download + open in an editor)

Then Discord just holds prompts + milestones, and you copy from the file (not from 40 Discord messages).

2) Switch the “coding work” surface away from chat entirely

For real coding, chat UIs are always a bit painful. The best UX is usually:

  • Terminal-based coding agent (Codex/Claude Code style), and
  • Chat (Discord/Telegram) only for instructions + summaries

If you want, you can keep Discord channels per agent, but ask the agent to post end-of-step summaries rather than streaming everything.

#

3) If you stay on Discord: threads + file drops

Discord is good at “many tasks in parallel” if you:

  • use a thread per task (not per agent), and
  • have the agent post code as files when it’s longer than a screen

That makes copy/paste basically “download file → copy locally”.

4) If you stay on Telegram: use folders/topics/hashtags

Telegram actually has a few organization hacks:

  • Chat folders (e.g. “Agents”, “Work”, “Ops”)
  • Pinned messages for the “current task”
  • In groups, Topics (if enabled)
  • Simple #tags inside messages for searchability

5) Consider a different chat app that’s “Telegram readability + Discord organization”

If you’re open to switching, the two that most often feel like the right middle ground are:

  • Zulip (topic-based threading is incredible for “one stream but organized”)
#
  • Slack (threads + good file handling; less “channel chaos” than Discord for some people)

If you tell me what you value most (single scrollback, threads, channels, search, file handling, mobile UX), I can recommend a “best fit” combo and a workflow that doesn’t make coding output miserable.

#

Discord is fighting you for two reasons: (1) hard message length limits and (2) bots generally can’t “stream into one evolving message” without doing a ton of message-edits (rate-limit hell). So even if the agent wants to send one clean blob, it often ends up fragmented.

What works in practice:

Best workaround inside Discord: “code as a file, not as chat”

Ask your coding agent to output long stuff as one of:

  • a single file attachment (e.g. patch.diff, changes.md, foo.ts)
  • a unified diff in a file (way easier to apply/copy than 20 messages)
  • a zip of changed files (if you’re iterating)

Then Discord stays readable, and your copy/paste is “download → open in editor”.

Better workflow: Discord for coordination, something else for the transcript

Use Discord channels/threads to organize tasks, but keep the “real” working transcript in:

  • your editor/terminal agent (best for coding), or
  • a web dashboard/control UI (usually a single scrollback you can copy cleanly), or
  • a notes doc (Obsidian/Notion/Google Doc) where the agent appends a running log.
#

If you want Telegram but organized: fake “channels” with folders/groups

Telegram can be organized decently if you:

  • create one group per agent/task (even if it’s just you + the bot/agent)
  • put them into a Telegram folder
  • use pinned messages for “current status / next steps”
    (If you’re using Telegram topics, that’s even closer to Discord, but it depends on your setup.)

If you’re open to switching: Zulip is the closest “best of both”

Zulip’s topic-based model gives you a single place, but neatly separated by topic—much better than Discord for “long coding threads that you want to copy”.

If you tell me where the agent is running (OpenClaw Discord bot, Telegram bot, local coding agent in terminal, etc.), I can suggest the most frictionless “one-message / one-file” pattern for that setup.

smoky sierra
#

It's running as a discord bot

naive baneBOT
#

If it’s running as a Discord bot, the cleanest fix is to stop treating Discord as the place where the code lives, and use Discord as the place where the bot drops artifacts.

What to do (works really well)

Have the bot send long outputs as attachments instead of splitting across messages:

  • patch.diff (best for applying changes)
  • changes.md (best for “one readable transcript”)
  • files/<name>.ts (best for direct copy/paste into an editor)

Discord’s 2k-ish message constraints + codeblock overhead are what’s forcing the fragmentation; attachments bypass that pain completely.

A prompt pattern that usually sticks

Tell the agent something like:

“When output would exceed ~1 Discord message, put the full content in a single attached file (output.md or patch.diff).
In chat, only post a short summary + what the file contains.”

Organization tip (Discord-native)

#

Instead of “channel per agent”, consider thread per task (even inside one channel). Then pin the latest patch.diff / changes.md in that thread. You get the organization and the “one place to grab the latest result”.

If you really want “one single evolving message”

That requires the bot to edit one message repeatedly (streaming-via-edits). Some bots do it, but it’s easy to hit Discord rate limits. If OpenClaw doesn’t support that mode yet, it’s a legit feature request to file.

If you tell me whether you prefer (A) markdown log or (B) unified diff patch as your main artifact, I can suggest the best “default format” for coding sessions.