[FEATURE] Dispatch Channels.

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

When I pick up my phone I want to move my own projects forward, not fall into a feed. The current mobile surfaces don't let me. Dispatch is one thread that has to be briefed from scratch every time — by the time context is reloaded, the spare five minutes is gone.

Thirty minutes at a time get stolen by the dopamine slop machine — time I'd gladly spend on my own projects if the product made that the path of least resistance. It doesn't.

What I need: projects always primed. Walk up, tap in, continue. Zero briefing, zero waiting, zero cold-start. One tap into a channel that already knows the repo, the notes, the half-built thought from yesterday — and I'm doing useful work before my thumb lands on Instagram.

Proposed Solution

Per-project channels. Each one a persistent, warm conversation bound to one project, always primed with its full context: repo state, CLAUDE.md, recent session history, status files, notes, whatever the project has. No briefing step, ever.

Each channel is alive, not just reactive:

It has its own cron jobs, editable from the channel itself. The project owns its schedule.
Those jobs post into the channel — overnight status updates, build results, reminders, scheduled agent runs — so when I open the phone I walk into movement, not a blank prompt.
Those jobs update the project — they can write to status files, run tasks, commit changes. The channel isn't just a reader; it drives the project forward while I'm away.
My messages into the channel go straight to the project's live Claude, which has tools and file access. I type, it acts, the project moves.
Channels run in parallel. Ten projects, ten always-warm threads, ten independent contexts. Switching between them is a tap, not a reload.

The result: picking up my phone is a choice between the feed and my own life's work — with my own work now the easier, faster, more satisfying option.

Alternative Solutions

Dispatch — one thread per account, briefed each time. Cold-start every tap. Can't keep many projects warm in parallel. Wrong shape for this problem even if it were reliable.

Priority

High - Significant impact on productivity

Feature Category

Other

Use Case Example

Imagine a user with several active personal projects — a side-project codebase, a half-written essay, a home-admin thread chasing paperwork, a running reading log, a cooking journal. All live as folders on their always-on Mac. All have history, notes, half-finished tasks.

They leave the house. Forty minutes on the train, then twenty minutes waiting for a friend at a restaurant. An hour of phone time that today goes to Instagram.

With channels:

On the train they tap the home-admin channel. Its overnight cron already posted that a reply came in from their accountant. They type one sentence in response; the channel — which knows the paperwork, the filings, the deadlines — drafts and sends the follow-up.
They tap the side-project channel. Last activity yesterday, mid-implementation. The channel knows the repo and where they were. "Sketch the smallest change I can make to try X when I'm home." Answer is grounded in the actual code within seconds.
At the restaurant, they tap the cooking channel. "What was I planning to cook Thursday, do I have the ingredients?" The channel — which lives in the cooking notes — answers without being re-introduced.
An hour of phone time that would have gone to feeds, spent nudging five different projects forward. No briefing. No cold-start. No single-thread bottleneck. Each channel was already primed; each tap was already useful.

That's the shape.

Additional Context

I can do this in openclaw with discord channels, only feature left open from the openclaw days I can't do with clawd code. I can't work from anywhere in the same way.