Kind Venom

Built a self-hosted MCP server so claude can ssh into my machines and call any API without ever seeing my credentials no extra tools, no API costs, works from the official mobile app

If you're building yet another orchestration layer and you don't want to glue code from different provides:

Someone idk told me this is great and i feel so validated right now github.com/thezem/AgentKi…

@grok rate my self promotion on a scale of 0/x influencer github.com/thezem/AgentKit

Holy shit! Someone just open sourced this!! It gives you one builder-facing API for: -opening and resuming sessions - switching models - chat/plan controls - supervised / auto-edit / full-access modes -approvals and user-input prompts - normalized activity events for agent UIs

@thsottiaux Just increase the limit at this point

At the current codex growth pace, we will owe you all another reset in less than two weeks. Would be funny to reach a state where these happen more than once a week before we reach 10M. Scrambling to get the capacity online.

How do people find contributers github.com/thezem/AgentKit

What's going on

They were right, it's not codex vs Claude, it's codex **and** claude. Legit thinking about keeping my subscription for both of them now, and just pay 40$ for two instead of 20$ just for codex. Ugh, really wish i was doing something important to justify these subscriptions

You all sleeping on GitHub copilot as a harness

We're cooking..

@spoollabs Windows support or at least as web app? 👀

Spool v0.3.0 is released with built-in agent mode! API key in, answers out. No CLI needed! 🤩 github.com/spool-lab/spool

The anxiety i have now with codex because claude shows the weekly limit from left to right > as progress you're moving through And codex shows from right to left as it gets reduced I used to go through Claude with no anxiety lol, this feels off man

Am i experiencing deja Vu?

@thdxr @gitlawb 😭😭😭

@gitlawb bruh

We forked the leaked Claude Code source and made it work with ANY LLM: GPT, DeepSeek, Gemini, Llama, MiniMax. Open source. The name is OpenCode

kept rebuilding the same auth stack with logto (frontend + backend + all the glue), so i turned it into a toolkit basically gives you a production-ready auth layer instead of wiring everything from scratch finally at a point i'd trust in real apps: github.com/ouim-me/logto-…

coding is solved my ass

@trq212 @dmitriid @bcherny @lydiahallie Hey , heard you're looking for more proof x.com/i/status/20382…

@dmitriid @bcherny @lydiahallie that's not the root cause unfortunately, wish it was

Goodbye my dictator goodbye

@trq212 @altryne Are you fucking kidding

@altryne we are actively looking into this in particular but not sure it's real yet, prompt cache bugs can be quite subtle

PSA: If you've been running out of Claude session quotas on Max tier, you're not alone. Read this. Some insane Redditor reverse engineered the Claude binaries with MITM to find 2 bugs that could have caused cache-invalidation. Tokens that aren't cached are 10x-20x more expensive and are killing your quota. If you're using your API keys with Claude this is even worse. This is also likely why this isn't uniform, while over 500 folks replied to me and said "me too", many (including me) didn't see this issue. There are 2 issues that are compounded here (per Redditor, I haven't independently confirmed this) : 1s bug he found is a string replacement bug in bun that invalidates cache. Apparently this has to do with the custom @bunjavascript binary that ships with standalone Claude CLI. The workaround there is to use Claude with `npx @anthropic-ai/claude-code` 2nd bug is worse, he claims that --resume always breaks cache. And there doesn't seem to be a workaround there, except pinning to a very old version (that will miss on tons of features) This bug is also documented on Github and confirmed by other folks. I won't entertain the conspiracy theories there that Anthropic "chooses" to ignore these bugs because it gets them more $$$, they are actively benefiting from everyone hitting as much cached tokens as possible, so this is absolutely a great find and it does align with my thoughts earlier. The very sudden spike in reporting for this, the non-uniform nature (some folks are completely fine, some folks are hitting quotas after saying "hey") definitely points to a bug. cc @trq212 @bcherny @_catwu for visibility in case this helps all of us.

@pankajkumar_dev 1 prompt = 1% usage Had to switch to codex And i raw dawged codex for 3 hours on heavy tasks only consumed 18% of my quota x.com/i/status/20382…

Claude Quota Reduced: Opus Feels Worse and Pro Plan is Unusable - I noticed a clear drop in Claude’s quality, especially with Opus 4.6. more hallucinations, worse decisions, and poor instruction following. - Tasks that used to work smoothly now need multiple retries, even for simple changes. - The quota issue is worse even small prompts are consuming a noticeable percentage of limits. - Claude Pro is where things break a single maxed Sonnet session took 8% of my weekly limit. - In just 2 days, I hit 56% usage with only 5-6 sessions (2 hours each). - This is with normal usage like concepts, strategy, and documentation. - Paying $20/month now feels like getting fewer messages than the free plan. - The Pro limit feels almost unusable. - Later it was said peak hours burn quota faster, but this wasn't communicated clearly. - Overall, it feels like Claude got worse and more expensive at the same time.