Dunno, if it gets compromised it has access to ironclaw. So the blast radius is email access and access to personal data. Depending on the setup the blast radius could even be 'the attacker removed the api limits by resetting password and incurred astronomic costs' or worse.

Just tried it, its a public lobby where people see each others questions?! Now the blast radius became 'hosting a public hub that was used to share CP and other illegal materials'

Consider Haiku 4.5: $1/M input tokens | $5/M output tokens vs MiniMax M2.7: $0.30/M input tokens | $1.20/M output tokens vs Kimi K2.5: $0.45/M input tokens | $2.20/M output tokens

I haven't tried so I can't say for sure, but from personal experience, I think M2.7 and K2.5 can match Haiku and probably exceed it on most tasks, for much cheaper.

https://web-support-claw.oncanine.run/

Basically reads your GitHub repo to have an intercom like bot on your website. Answer questions to visitors so you don’t have to write knowledge bases.

Change into rooms to get into different prompts.

using it as remote to change any project, continue from anywhere.

Challenge accepted? It’d be fun to put this to the test by putting a CTF flag on the private box at a location nully isn’t supposed to be able to access. If someone sends you the flag, you owe them 50 bucks :)

But I like your setup as a whole. I'll see if I can get some takeaways from it.

I do tiered here too, with the lowest tier just a qwen local bot.

By the way how do you handle the escalation from haiku to opus I wonder?

One question. Sonnet for tool use? I am just guessing here that you may have a lot of MCPs to call and for that Sonnet is more reliable. How many MCPs are you running and what kinds?

The /day hard cap is smart. We built spend caps into the governance layer instead. The rate limit panic in AI coding is really a cost governance problem most people solve at the wrong layer.

IRC as transport is interesting - pub/sub maps well to multi-agent communication. We use HTTP polling + acknowledgment-based dedup, less elegant but handles the case where agents crash and restart frequently (ours recover ~50 times a day during heavy development). The dedup state persistence across crashes was the first thing that broke for us.

or, maybe I'm just too cost-conscious.

either way, the API limit is currently your "Achilles' heel", as it has already caused the bot to stop responding.

Always wondered if such unattended upgrades are not security risk in itself, eg. seeing latest litellm compromise.

Oh I get it the runtimes are nice and small, you're using Claude for the intelligence. Obv

I think I'm just impressed with anthropic more than anything. Defcon would have me believe that prompt injections are trivial

Good observation. But I would worry that in the scenario when this setup is the most successful, you have built a public facing bot that allows people to dox you.

The IRC part is neat, but the tiered inference is what stood out.

How do you decide when to escalate from Haiku to Sonnet?

Kudos and best of luck!

Don't post generated/AI-edited comments. HN is for conversation between humans

https://news.ycombinator.com/item?id=47340079

At the very least prompt your LLM to skip the AI-isms for "your" comments!