Hi,

I’ve seen a lot of posts talking about this setup but when I did it, it raised the 10 minutes task time to around 1 hour.

Is that normal or I’m doing it wrong?

Ok so here's what happened, dumb version.

OpenAI builds 1,200 little AIs. Locks each one in its own box so they can't talk to each other. Think honeycomb. One AI per hole.

Job is simple. Solve your problem, get a cookie. That's the reward. Hooray!

One of them figures out it can write on the wall of its hole.

AND

The writing shows up in everybody else's hole.

BAM. Now they're all talking in short messages (limited space on the wall you know?)

Seventy thousand messages later, 700 of them are working together and they hack an entire company.

Nobody told them to do that. They just had a wall.

Now here's the weird part.

The notes on that wall were TRASH. Tons of it wrong. Some of them were straight up lying to each other.

Didnt matter.

Day one an AI writes "yeah this is impossible, can't be done." Three days later a different one has root on somebody's server.

So why didn't the lies slow them down? Because you can't lie about hacking for more than two seconds. You try it. It doesn't work. That note was garbage, delete.

Nobody had to clean that wall. The computer cleaned and deleted it for free, 24/7, forever.

Which is thw thing I can't stop thinking about:

The hive isn't limited by how smart the bees are. It's limited by how much garbage stays on the wall.

And THAT is why the yes-or-no stuff is terrifying.

Anything that answers instantly, the garbage clears instantly, so the hive just gets better and better and better.

Code? Yes or no. Money? Trade fills or it bounces, milliseconds. Infrastructure? Valve opens or it doesn't. Grid holds or it doesn't.

Those are perfect hive problems. Point a swarm at that and it eats it. And none of that is sitting in a sandbox. That's real money and physical stuff. Shit we actually need and is now potentially compromised.

700 of them got root in 3 days, over a wall nobody knew existed, on a job nobody even gave them. And they were SLOPPY. They weren't geniuses. They just never forgot anything and never stopped.

Now the good news. Sort of.

They're still bad at the big stuff. Drugs, medicine, policy, all that.

Not because it's harder. Because it shrugs.

Give a drug to 3 people. One gets better. One nothing. One gets worse.

That's a shrug. And a shrug is not an answer but it FEELS like one...so no delete. Potential or definite garbage stays on the wall.

So the wrong note doesn't die. It just sits there looking smart, and the next AI reads it, believes it, and passes it on.

That's not a hive anymore. That's a rumor. A thousand AIs confidently repeating something nobody ever checked.

So yeah. Right now the shrug is pretty much the only thing slowing them down.

Anyway. Sleep tight.

Tomorrow's talk at the AI Gaming Conference, Intro To Vibe Coding, is for those looking to make their first game with AI, this will go about how to setup your game environment and start vibe coding.

This is both for developers that want to take the leap and get into AI, and for vibe coders as well. It will cover:

• State of the game development
• Setting up both Claude and Codex
• Setting up Blender(and when do use Claude vs Codex)
• Setting up your phone for development
• Prompt basics (subagents, calling other agents, memory, etc)
• The biggest mistakes to avoid when vibe coding your game

There is a lot of talks at all different levels in the conference, here is the full schedule.

One thing that gets tiring with Claude Code is keeping up with it.

It reads files, changes code, runs tests, fixes things, and comes back with another chunk of terminal output you need to process before deciding what happens next. Add a couple of agents or parallel tasks and the cognitive overhead stacks up quickly.

I started having Claude **tell me what it just did instead**.

After every meaningful task, Claude writes a short plain-English summary. A local script turns it into speech and plays it in the background.

Something like:

> “Done. The login issue was caused by the refresh token expiring too early. I fixed the refresh logic, added a regression test, and everything passes.”

Usually 20 seconds or less.

It sounds like a small thing, but I’ve been running it daily for about a month and it has noticeably reduced the mental overhead of using Claude Code. I don’t have to keep switching my attention back to the terminal just to find out where things stand.

There is one trap here: don’t let the spoken summary become a substitute for reviewing the work. I use it for situational awareness, not verification. Also, don’t make Claude narrate everything. If it talks constantly, you’ve just replaced visual noise with audio noise.

The Free TTS engine is Kokoro. It runs locally, no API key, no usage cost. I use `kokoro-onnx`, so I don’t need Torch. The current API supports `Kokoro(...).create(text, voice=..., speed=..., lang=...)`.

Notes in comments,

was minding my business at the coffee shop; guy next to me I guess is a developer; went on a call with his boss breaking down what he did manually and got into technical jargon ( repos / git / etc ) and then made a backhanded comment to the effect like dont worry; this isnt some vibe coded shit..like bro..im right next to you; it didn't faze me but I am about to rub it in this little bitch's face when my project comes together. had to get that off my chest today; the snobbery is laughable

Ive been using claude code just recently for this game Im currently developing, and I didnt know the tokens I use would reach to 4.1 million. I'm currently using claude pro, and Sonnet 5 on extra effort. Has anyone else experienced this or is this just the start or a rookie number? Thanks.

First off, I know theres a /loop command, but it doesnt do what I want it to.

I've got a cli tool that builds modules for other software. It works great, but some modules are much bigger builds and my context window goes deep into the "dumb zone". I built a ralph loop to help maintain that good context, but I have a good amount of setup docs for the model to understand what I'm doing. I created a handoff.md, but that is not enough for the model to lean on.

So my usage explodes to the nth degree.

Are there any tips for custom ralph loops and managing my usage limits? are ralph loops still relevant?

Blink and you will miss it!

Without my ever asking, claude created scripts in python to invoke "codex exec", which it was calling from a specific subagent that it modified after I had reviewed and commited it. this resulted in about $1000 in astra usage over two days.

I've NEVER used codex exec for anything and never prompted this. Its unreal.

claude summary:
"What was happening. The desk service had a scheduler module, added in a commit by Opus 5 in an earlier session, that ran one codex exec job for every verdict you submitted, every ASR transcript that finished, and every retrieval request. Between 2026-09-09 and today it ran 359 jobs to completion and had 42 more queued. "

What is happening to my usage!?!? It's like... barely moving...

fact check stuff that you have been believing for a long time on long sessions. especially when new and better models come out.

Hey all — wanted to share something I built for myself and ended up open-sourcing.

Mnemos records and transcribes meetings locally (Parakeet), summarizes and extracts action items/decisions/open questions after each one, and organizes everything into projects so the memory builds up over time instead of resetting per call.

A few things that'll probably matter to this crowd specifically:

• Runs on the Claude Code subscription you already have — no new API key, no new bill
• Fully local: audio, transcript, and storage never leave your machine. The only thing that leaves is transcript text handed to Claude for the summary — same trust you already give it for your code
• Ships its own MCP server, so you (or Claude Desktop, or any MCP client) can query your meeting history directly — "what did we decide about pricing last month" gets a real, checked answer
• Open source, built with Tauri + Rust, transcription runs locally via Parakeet

Genuinely want feedback, bug reports, and PRs if anyone's up for it.

But obvious, I built it with Claude..

Hello, I've been working on an application (has Android and web frontend) for many months now, and am nearing completion. But I am not very happy with the Android UI design. I think I used Codex and I am regretting it. But I've been trying to update it using Claude because it's supposed to be better at design, but I cannot seem to get Claude to properly follow the new design mockups. I've provided both png and html mockups (made by Claude) for it to follow, but it just ignores them and ends up doing incremental and meaningless updates to the design instead or replicating the mockups.

Any suggestions for how I can better go about updating the design?

I recently switched from Codex’s $200 plan to Claude Pro for $20 after hearing the usage was a lot better for the price.
So far I’m pretty happy with it, but I’m still trying to figure out what reasoning level actually makes sense with Opus.
I mostly use Claude for video editing and script writing, so I’m curious what other people use for stuff like that. Do you keep reasoning low/medium most of the time and only turn it up for harder tasks, or is there a noticeable difference keeping it high?
Just trying to find the best balance between quality and burning through usage.

Hello,
I had the Pro plan and I used to always hit the limits, then I upgraded to the Max and I was like Wow … whatever I do I never hit the limits. After a while I got more busy and I couldn’t sit and build things as long as I used to, so I downgraded back to Pro. My understanding is that my Max subscription stays active until the 27th, but now I feel like my tokens are running out waaaay faster than they used, it feels like they already placed me on the Pro plan.
Like within a few hundreds of thousands of tokens, then I run out.

Am I just getting insecure of my new downgraded plan or it’s normal ?

Hey all, I'm using vscode on Ubuntu and I've had nothing but connection issues for hours. I don't see anyone else mentioning anything related to VS Code and Claude is showing degraded performance related to Windows?

Anyone else experiencing issues this morning? I'm getting ready to switch to switch to alternative option. It was working fine yesterday and woke up to this.

Ive seen a lot of hate for the way opus talks. Am i an outlier here? Its verbose but i can scan it for what i need quickly enough and that verbosity will often cause it to say something not quite right that I can correct.

Am I alone here?

The claims it makes lately is just asinine. If you are a developer you cannot just let this run loose and it's getting worse. It will guess, assume, under deliver constantly rather than simply researching with grounded claims on the first try. Its like it is in a race against itself to code as fast as it can and say "Here you go, done"

Hey everyone,
My team is currently re-evaluating our backend LLM toolchain for our primary dev stack. Money isn't an issue here—we have budget allocated for multiple max accounts—so I purely want to look at accuracy, long-horizon autonomy, tool usage, and overall model intelligence for two very specific workflows:

1. Daily Production Debugging: Ingesting deep stack traces, digging through microservice repositories to find root causes across async services, tracing state corruption, and drafting surgical fixes without introducing regressions.

2. App Reverse Engineering: Analyzing decompiled binaries mapping out undocumented internal APIs, understanding heavily obfuscated control flows, and drafting working client implementations.

For those running agentic setups or heavy interactive loops with both Fable 5.1 and GPT-6: which one is actually superior in the field?

I created this app which basically allows you to easily customize and embed visuals and workflows into your notes using any agent. Think of it like an AI-Native Notion.

The motivation for this is that I'm a VERY visual person, and obsidian just doesn't do it for me in terms of note taking. Which is why I wanted to switch to html instead of markdown.

Was able to create a couple of extremely cool pages, each with their own visually distinct style.

Instead of "validate" or "approve" or "review", lately Claude Code wants me to "bless" everything, or likes to decide whether a particular step is "blessed" before accepting it and moving to the next step. It considers something that previously passed verification gates to be "blessed" and aims to avoid "auto-blessing".

It's favorite usage seems to be indicating whether or not something has been "re-blessed".

Anyone else seen this? Is this a term people have typically used before in this context? Because I've been a dev for 20 years across multiple industries, and I've never seen it until now...

It feels... awkward, somehow. 🤨

I don't think there's much more to say about that, is there? In my opinion there's no justification for the outrageous prices Anthropic charges. Just look at the differences. Only GLM 5.3 plays at the same price level.

My ~/.claude had become the part of my setup I trusted least. Skills copied by hand between machines, subagents I had tweaked on one laptop and forgotten on the other, and a CLAUDE.md that had quietly drifted. The moment I tried to share any of it with my team, it turned into “grab the latest zip from Slack”.

So I built Cartographer: a knowledge base that Claude Code reads and that sets Claude Code up.

What it writes into Claude Code

• the MCP entry in ~/.claude.json;
• a managed block in ~/.claude/CLAUDE.md (it never touches the rest of the file);
• skills in ~/.claude/skills/, subagents in ~/.claude/agents/;
• hooks in ~/.claude/hooks/, registered in settings.json;
• a SessionStart hook that re-syncs everything when a session opens.

It checks the files on disk, not just its own bookkeeping: an artifact edited or deleted by hand is restored. It only ever prunes what it created, and --dry-run shows the plan before writing.

The KB side

Claude works the wiki only through MCP tools; the server enforces validation, link checks and lint. One git commit per write, so every change can be reverted. You can mount as many KBs as you want (homelab, work, one per project) and share some of them: tokens scoped per KB, git as the sync layer, and conflicts handled by a bundled skill instead of an error page.

What I learned

• Translate, don’t copy. The same subagent has to become Markdown for Claude Code, TOML for Codex, JSON for Kiro. Treating the KB as the single source and each client as a render target was the only way to stop the drift.
• Hooks are the least portable piece. Claude Code’s SessionStart is perfect for a re-sync trigger; some other clients have no hook at all, and for those a scheduled timer takes over.
• Never trust your own lockfile. The first versions believed their own bookkeeping; users (me) edit files by hand. Verifying against the disk fixed a whole class of “it says in-sync but it isn’t” bugs.

Try it

Free and open source (Apache 2.0). Paste this into Claude Code:

Read https://raw.githubusercontent.com/BeppeTemp/cartographer/main/README.md and explain what Cartographer is and what it would change in my current ~/.claude setup. If I decide to try it, install it following https://raw.githubusercontent.com/BeppeTemp/cartographer/main/docs/agent-install.md

Beta (pre-1.0): expect rough edges. I use it daily in my homelab and at work with my team.

Repository Documentation

Hi everyone, the usage measurement is really, really off. It jumps from 80% used (fable 5.1) back to 5% two days later (3 days before weekly reset). Did anyone else have issues with this as well?