OpenClaw Agent Home: Thread per Project + File Baton

One developer's three rebuilds of their OpenClaw agent home land on a clear pattern: channel per area, thread per project, and a file-baton workaround for long content that dodges platform message limits entirely.

The Setup That Stuck

This is a Discord-centric layout, but the principle — organization by project, not by workflow — applies anywhere. The author tried Discord (single channel), then Telegram (four workflow channels: dictations, research, writing, general), and hit clutter both times. The problem with workflow channels: agents mid-turn get redirected to whichever channel is handy, scattering project context across unrelated channels.

The winning setup was Discord with channel per area, thread per project. A project lives in one thread for its whole life, and switching between projects never loses context. The missing unit was the project, not the workflow.

The Message Length Gap and the File-Baton

Here's the hard limit that forced the workaround: Discord caps messages at 2,000 characters (4,000 with Nitro), and Telegram's 4,096-character limit auto-splits long pastes. But dictations routinely pass 4,000 characters. The author's first long dictation on Discord died mid-sentence at 2,000 characters — Nitro wouldn't have saved it.

The fix: when content is longer than a message, make it a file. Write the long content to a file, drop it into the project thread, and let the agent pick it up from there. Nothing truncates, nothing splits — it works on any platform with no Nitro and no waiting on Discord or Telegram to raise limits that aren't coming.

Practical Pattern: Telegram as Sidecar

The author still keeps Telegram installed purely as a long-capture sidecar — a fast way to dump text. Discord is home, Telegram is the loading dock. They also flag Telegram's trust baggage (App Store removal, founder legal fights) as context, not the argument.