It can. Go to the code tab, choose your repo, and have it write an image file to disk. If you tell it to read it, it should show in the chat. It works on the web version so hopefully it works on ios.

Claude Code for the web would be able to do that

I feel like this is absolutely not the case. Our corporate infosec guys are freaking out, as developers and general users alike are finding all new ways to poke holes in literally everything.

We're finding out quickly that enterprise endpoints are not locked down anywhere near enough, and the stuff that users are creating on the local endpoints is quickly outpacing the rate at which SOC teams can investigate what's going on.

If you're using Claude via Anthropic's SaaS service it's near impossible to collect logs of what actually happened in a user's session. We happen to proxy Claude Code usage through Amazon Bedrock and the Bedrock logs have already proven to be instrumental in figuring out what led a user to having repeated attempts to install software that they wouldn't have otherwise attempted to install - all because they turned their brains off and started accepting every Claude Code prompt to install random stuff.

Sandboxing works to an extent, but it's a really difficult balance to strike between locking it down so much that you neuter the tool and having a reasonable security policy.

The auth mess is part of why I don't use the AWS MCP

Also because the aws cli works better, just add an instruction like this to your agents file:

> When performing aws cli commands in terminal always use the `--no-cli-pager` flag to avoid interactive pagination.

the truth?

It isn't a fallacy and nothing should ever be above criticism.

its a description of the opportunity, i think.

webhooks have been very powerful, and you can start feeding the same stuff into claude as the orchestrator

What do you call it when someone takes offense to calling a spade a spade?

Dang it, I wrote the wrong link. https://github.com/corpollc/qntm

I wrote it originally because I wanted my openclaw install to talk to my assistant's openclaw, and my openclaws that were local at different houses.

It's morphed a lot since then, and is close to being super useful -- it allows group chat, and is close to having a realistic API call on threshold vote gateway system built in.

That stuff is built to support Corpo's main business model which is providing real world asset and governance access to agents.

So, for example, I think agents might like to vote on sending a wire transfer by approving a specific mercury bank API call.

I could go on. You can also use it to remotely chat to an agent across firewalls - it's pull / poll only.

And if anyone is interested, I made an HN Group chat: https://chat.corpo.llc/?invite=p2F2AWR0eXBlZmRpcmVjdGVzdWl0Z...

I'm using `pi` as my agent and build my entire agent orchestration on like 4 skills to start / stop / capture / await a set of tmux-bash & tmux-pi sessions.

This is the first time in a few months I might actually try `claude` cli again to try out this channels scheme.

I tried various solutions around this. CloudCLI (ex claudecodeui) looked promising, but very buggy (disconnects, UI overlapping text, etc). Tried Claude Remote Control as well, but also very buggy, websocket disconnecting, UI broken.

I ended up just running Claude code in a dtach+ttyd session. Still not the best, as xterm.js has tons of issues with long scrollbacks, but it's at least somewhat _usable_.

Back in the day, when I used to play pokemon go, there was a small local community and we would struggle to decide where to meet up for the daily raids because people would basically not respond (so as t not commit), or not know which gym each other meant exactly, nor give live updates when people moved around, etc. etc.

Then I joined a group from a bigger city where I commuted for work. They had a telegram group chat with two "channels", one for talking, one for bot posts. The telegram bot could be sent a single screenshot of a raid, and it would use OCR to automatically generate an interactive UI for that raid for everyone to see, with all the relevant info, and it would also clear itself up when the raid is no longer relevant. You could press buttons to say you were going, that you MAYBE were going, if you were late, and if you already started/done it, all in single clicks. Tons of options, tons of information, all live updated.

I was bedazzled. That feature singlehandedly removed all attrition from urban social gaming. And it was entirely grassroots. It made me try out making my own telegram bots, and yeah, you basically have the power to make a little app in chat form, even some that feel like CLI commands.

It's been OVER HALF A DECADE and I have yet to see a single other chat application have that degree of freedom where it comes to applications and bots. Some like discord even did whole ass 100% reworks of their bot AP to support the likes of slash commands, and still fall short. And there's none worse than Teams. Teams hates you. Teams spent the prior 2 years before this one basically pointing a gun to our heads telling us they were removing webhooks and pushing back on it whenever they repeatedly get told that's the most insane and dogshit idea ever. And they still did it. There's just no spark in Teams UX. No self-respect. It's a soulless product made entirely as a dumping place of "synergy" with other M$ products. It's reciprocal, I hate it too.

Oh and my local group never go into telegram because they didn't want a new app. It died, but I still kept playing after work without problem. It makes me wonder how fast Teams would die if it wasn't proped up by 365 and Azure subscriptions.

I’ve been using Telegram for about 10 years, and it’s one of the few products that has consistently felt great the entire time. It’s fast everywhere: backend, mobile app, desktop app, all of it. Everything just works. Its sync is out of this world—fluid, fast, and seamless across devices. You can use it on your phone, then move to your PC or laptop and continue instantly without friction. Unlimited message history and file storage are fantastic, and the bot platform is absurdly powerful. It’s boring in the best way, which is exactly what you want from a channel for interacting with your agents everywhere.

Odious is one of the most reserved words you could use to describe Telegram, which is primarily a host for scams that the influencers and other bottom feeders aren't allowed to monetize on the big social networks.

My employer keeps Slack so locked down it is not really possible to use anything useful with it anyway…

I feel the opposite. I'm on Teams all day at work and have reluctantly opened Telegram recently to try a Claw despite having an account for years.

I've been surprised how little support there has been for Teams in the whole AI ecosystem. It seems all developers assume that the whole world is at startups working on Slack when most businesses are on Microsoft 365.

Can't say I have had literally anyone ever message me on telegram. And I have been a daily user for years.

You're telling me that Anthropic, one of the hottest companies on the planet right now couldn't field four teams of developers to integrate with Discord, Slack, Telegram, and Teams? AI being such a productivity multiplier, seems like they could just choose to do it all. I mean, mythical man month and all that, but do it three times and have a retrospective and use Claude to refactor the pain points and centralize the learnings.

no they definitely did not have fewer users than Perplexity xD

Interesting. I set up a bunch of slack webhooks for server events that's been working decently well but maybe I'll look at telegram.

This is so true. I don’t like Telegram for a host of reasons, but the bot architecture is second to none. Try creating a bot in Slack. You’ll pull your hair out for hours. Same goes for Discord. Utter nightmare. Telegram? You send a DM and it is basically done.

Unfortunately, Telegram is also a no-go from a security/data privacy perspective for many use cases.

WhatsApp is actually more popular than Slack, isn’t it? In my country, almost everyone uses Slack, and I’ve hardly ever heard of any companies using WhatsApp, so that was surprising to me.

south america and africa are both heavily invested in whatsapp in the business space.

XMPP is working pretty well for me

Twitter put all normal fun bots out of business with their API changes, that's about it.

Heartbeat should be set to be a cheaper model.

All *Claw implementations should use a local model for heartbeat, it doesn't need to do anything complex, pretty much just read a text file and do a true/false decision if there's something in there to do when it wakes up.

If so, it can either just shove the full heartbeat file to a smarter model or try to intelligently spread the tasks to the correct models.

Maybe it's less risk for them to offer the individual features. That way if people get inadvertent results, it's easier to blame the user, not the tool/company

Anthropic previously shared that they make ~60% margin on API access. So they're losing money on plan whales.

It doesn't matter if they are unprofitable at full usage, as long as there are enough users (like me!) who barely ever max out but still pay the $100/month. The people who love Claude Code enough to max out the 20x plan every day, that's probably the best influencer marketing campaign you could ever buy anyways.

Can you give an example of why this is better than the iOS Claude app?

Anything to do with Code. Not on Mac or iOS, and not with local sessions or cloud sessions. Normal Claude chats send notifications fine.

They appear to get turned on but then just never work on iOS for me. Hooks work fine, I use it to get a beep.

I’ve tried everything. Regular Claude chats notify me fine, but nothing from Code - neither a cloud session or remote control.

Not for me

Quote:

"i enabled github connector can you see it?"

Answer: "I don't see a GitHub connector in the available integrations. The search only returned a Microsoft Learn connector (not connected). It's possible the connector hasn't fully activated yet, or it may not be available in your current setup. Could you double-check in Settings → Integrations that it shows as connected?"

Multiple such checks and re-setups do nothing.

I'm using the web UI and its container.

For bots?

Well, it's one conversation per bot. I set it up, connected the channel. DM'd it (only way to converse with it - wish I could have a Discord channel per project, different CWDs etc...) and asked what happens when I start 2 claude sessions connected to the channel and it said it'll just work with one.

Suppose you could have multiple bots, but it looks like it only supports one bot token anyway.