Claude is leaning into the idea of a local "session" being the host where everything connects.
I guess this makes sense for now. You can build integrations leveraging the user's personal access credentials. Later, once Claude takes over the world, they can move sessions to live in their own walled garden.
thats how Amazon worked its MCP setup - got everything onto oauth tokens, and then the harness knows how to to access the token to get permissions to whatever the user has.
the bad part is setting separate permissions for different user tokens
What these 'channels' do is essentially why I was running a nanoclaw at work: triggering a claude code based on events and getting feedback/review/analysis which nicely closes the loop with other agents.
Not sure why it has to be an mcp, but will be trying this out asap.
This looks super super useful.. I'm making an agent to agent chat tool (that I think is actually ready for testing, so please check it out) -- https://chat.corpo.llc/ or https://github.com/corpo/qntm -- and the difficulty of getting claude to check and respond to messages is real.
Basically the Claude CLI is the operating system is the product vibe I get right now.
I was a little surprised to see a Telegram integration rather than Slack or Teams, given Anthropic's enterprise-first posture. But then I looked it up, and it turns out Telegram dwarfs both, at around 1bn MAUs, vs 50m and 300m respectively! I had no idea - reminds me of the time I found out Snapchat has 2x the userbase of Twitter.
Telegram is more popular among "normal people", and it also has a laissez-faire attitude towards bots and bot development. Making a bot that you, or even other people, could add to their contact list and use is pretty easy.
It's wild, but "people who want to build and run their own one-off bot for something like home automation" are almost treated by Telegram like first class citizens.
It's not even funny how a multibillion-dollar company with thousands of employees having unlimited access to the "world's best coding models" lags behind a small one-man [1] open source project that already had multiple plugins for the same feature [2] for months.
Pi already has 700+ third-party packages [2] for various purposes of various quality. But it doesn't matter, since creating a new working Pi extension to suit your needs is just a prompt away, and you don't even have to restart your coding session.
Apples and oranges comparison, one is a messaging app, the other two are used for communication and collaboration across teams in a workspace. I have worked in 5+ companies who used either Slack and Teams, none used Telegram for any comms.
Telegram is 'bot friendly' since the beginning, gaining a lot of users with crypto boom a decade ago with coin drops and things like that, so it is very good to develop for, but I have your initial sentiment first - shame this hasn't launched with tools people actually use for work.
Not really a meaningful comparison. Telegram is a personal messenger while Slack and Teams are for work. Telegram should be put alongside WhatsApp, iMessage, WeChat etc., which all have user bases in the billions.
finally! I'm building an app that's essentially a "sidecar" to an llm subscription and works via mcp and has a web ui to make reviewing deliverables easier, uses the user's subscription for intelligence instead of requiring to pay for tokens inside the app. The problem until now is I couldn't trigger AI work from the web ui, that limitation will be soon gone, it fixes a huge ux issue for me, I honestly thought it would happen sooner but I'm glad the industry is catching up.
I was making a telegram to Claude via tmux capture-pane and send-keys, this will be so much nicer. Also sounds like something that addresses some of what Steve Yegge said was missing for agent to agent communication as well.
Plus it gives a little ASCII dog to Claude Code terminal.
The ability to spawn independent CLI is awesome. No brainer they would add eventually between the great threaded functionality it brings and is essentially a more controlled version of OpenClaw IMO
I don't understand how this can be economically viable. If this takes off, it will allow businesses to use openclaw-like functionality at non-api prices (pro, max).
I've created an iCloud account for my llm.
On my Mac, I created another user account, not an admin, just regular. Linked to the iCloud account. Installed Bluebubble.
And now I can chat with my AI via iMessage, via my Apple watch, or my homepods. It works beautifully.
I've been looking to build something similar to this so this is very timely!
What I wanted to build is a way for Claude Code to automatically receive reviews and CP failures from a Github PR and automatically revise code and respond to comments. It looks like with a custom Github PR channel I can get very close to this, although I do wish that a channel can be opened in a running session instead of having to create a new one. Hopefully they add that soon.
It would have surely taken less time to just set up notifications for the Claude Code app? Are they ever going to do this? It's baffling to me that they're just skipping over letting you know when a task is completed... this is basic stuff.
at this point anthropic is dogfooding us a new product every week just to see what might stick - doubt a lot of the features/products they've rolled out will actually be around or supported in a year
I also get the impression this is way more complicated than it needs to be. Or maybe it's simple and they keep inventing new terminology for stuff that basically already exists. The crypto bros did the same shit. Like, bidirectional communication has been a thing for decades. We're just changing what we call the client and the server? And the protocol is just strings the bot on the other end is a little better at reading?
75 comments
[ 0.30 ms ] story [ 69.3 ms ] thread[1] https://github.com/anthropics/claude-code/issues/11447
I guess this makes sense for now. You can build integrations leveraging the user's personal access credentials. Later, once Claude takes over the world, they can move sessions to live in their own walled garden.
the bad part is setting separate permissions for different user tokens
Not sure why it has to be an mcp, but will be trying this out asap.
Basically the Claude CLI is the operating system is the product vibe I get right now.
Claude Code daemon mode in background when?
It's wild, but "people who want to build and run their own one-off bot for something like home automation" are almost treated by Telegram like first class citizens.
Pi already has 700+ third-party packages [2] for various purposes of various quality. But it doesn't matter, since creating a new working Pi extension to suit your needs is just a prompt away, and you don't even have to restart your coding session.
[1] Pi Coding Agent https://pi.dev [2] https://www.npmjs.com/package/@e9n/pi-channels [3] https://pi.dev/packages
Telegram is 'bot friendly' since the beginning, gaining a lot of users with crypto boom a decade ago with coin drops and things like that, so it is very good to develop for, but I have your initial sentiment first - shame this hasn't launched with tools people actually use for work.
And no, Discord is not used for that either.
The code/product itself is an absolute nightmare of overengineering, riddled with bugs and undocumented behavior changes across versions.
- https://clappie.ai
Plus it gives a little ASCII dog to Claude Code terminal.
The ability to spawn independent CLI is awesome. No brainer they would add eventually between the great threaded functionality it brings and is essentially a more controlled version of OpenClaw IMO
Maybe there should be a Claude code that facilitates others that is connected. Like sub agents but can "choose what to do" on permissions check.
Or some other means to listen for permissions check
I've created an iCloud account for my llm. On my Mac, I created another user account, not an admin, just regular. Linked to the iCloud account. Installed Bluebubble.
And now I can chat with my AI via iMessage, via my Apple watch, or my homepods. It works beautifully.
However, once remote capabilities are added to any software, it is virtually guaranteed that they will eventually be exploited as backdoors.
This means enterprise security solutions will need to develop the capability to distinguish between legitimate and illegitimate Claude Code instances.
What I wanted to build is a way for Claude Code to automatically receive reviews and CP failures from a Github PR and automatically revise code and respond to comments. It looks like with a custom Github PR channel I can get very close to this, although I do wish that a channel can be opened in a running session instead of having to create a new one. Hopefully they add that soon.
It runs Claude in docker containers, listens for webhooks to see comments and CI status.
(and it may be better)