HeyAgent – continue your Codex/Claude sessions from Telegram
Telegram-to-Claude bridge is nice UX, but continues a local session, not a true multi-device workflow.

Consolidation loop preserves context across sessions when Claude's native compaction loses state.
Developers using Claude Code or similar LLM harnesses
Claude Code · Continue.dev · Cursor
Theres a few core ideas outlined on the html, but the incepting one was domain lenses as personas within a thread. The main path /storytime cmd kicks off the process and yields a full set incremental documents, and thats been very useful for me as well.
Other ideas like breakouts, @roles, and others have been subsumed by recent moves towards agentic teams, but I think this flavor is unique in its approach and format.
Unfortunately many of the other ideas have collided with CC's opinionated/more built-out systems, and its hard to say if they're production worthy.
That said, I've been using this as my daily driver for maybe 4 months now, so hopefully its useful or inspiring to someone else.
Telegram-to-Claude bridge is nice UX, but continues a local session, not a true multi-device workflow.
Markdown based idea queue with Stop hooks for Claude Code sessions.
Cross-session Claude messaging using Anthropic's research channels API.
Debugger for Claude Code session costs—step-by-step breakdown of tokens and tool calls.
Debugger for Claude Code sessions—niche but solves real frustration with cost visibility.
Turns your denied Claude Code plans into personalized improvement hooks automatically.