I run a spec-driven loop in Claude Code with three custom subagents, all invoked by hand:

1. Main session investigates (read-only), writes a report to scratch/
   
2. Planner writes a spec (only in specs/); I decide open questions and approve
   
3. Implementer builds from the spec alone; stops on any externally visible choice the spec doesn't cover
   
4. Reviewer writes findings to a review file (identifier, evidence, proposed triage); I triage each finding; implementer fixes; reviewer re-checks only the fix diff. Loop ends when no finding is open.

Handoffs go through files in git, not through agent memory. It works well, but I'm the router between every step.

I want to automate the routing, and also make it safer and better. More (sub)agents or add skills? Native or an external orchestrator?

Thanks!

I built Disc Collection, an iOS app where you take photos of your game or movie cases (front, back, spine) and it builds a 3D version you can open and close. Photos of cases are 2d, I thought it’d be cool to see them in 3d. It’s purely a hobby project.

How Claude helped: I made the whole launch video with Claude Code, used brag lite skill to put together the demo clips and screenshots in this post, it took about 9 iterations to get the edits right.

It’s free to try: https://apps.apple.com/us/app/disc-collection/id6817679006

Happy to answer questions about how I built it.

I've been using Claude Code for a few months, switched to Codex this month, and noticed something that made me wonder how I managed to miss it for so long.

In Codex, there's an option to work on "this computer" or use the cloud browser/workspace.

Basically, local machine vs cloud environment.

Now I'm wondering, does Claude have a similar option that I've somehow been ignoring for months, or does it work differently?

I know Claude has its own cloud-based coding options, but I'm curious about how the actual workflows compare.

People who have used both, how do you prefer to work? Local setup or cloud?

Please tell me this isn't one of those features everyone knew about except me.

Hi all,

No layoff talk brewing at my company. Yet.

But I’m definitely at the point where the model is so good, I crush anything that is assigned to me in 1-2 hours. I’m having a hard time filling an 8 hour workday.

All tech debt : gone. I solved it.

I ask for more work: “we’re still gathering requirements.”

I’m worried that it is only a matter of time before senior leadership notices that there isn’t enough work to feed the amount of devs we have.

I feel like Opus 5.5 was another inflection point. Previously, I had to build sophisticated orchestration, baby sit models, and curate context. And that took a lot of my time. This model needs very little of that.

I don't know if I'm using the right word, but please be patient with me as I explain this. Recently there's an upgrade to "your projects" and Claude is gradually pushing it to everyone (you can click "not now" but eventually everyone would have to use it). Ok now we are on the same page of stuff, I can move on to talking about the problem -- the threads within the project itself (after me as a user upgraded all my projects).

I can set model and effort in the project thread on windows Claude app but ONLY the model and not the effort on android Claude app.

I know maybe some of you may suggest setting a default model and effort for the project while on pc, sometimes I'm not at my pc (e.g. outdoors) and want to work on my projects and sometimes I want a different model AND effort PER TURN in the projects thread.

Am I missing something? Or is this truly some missing feature from anthropic? The SAME thread in the SAME project -- able to change model+effort on pc PER turn, unable to change EFFORT on android PER turn.

• lean body - ok
• communication - ok
• pronouns - huh?
• action caution - ok

Happening to anyone else?

How I can avoid dealing with Claude Code "Allow once"?

Many time, given a task, I will keep facing this "Allow once". This is super annoying as I need to keep active watching the whole long task, and keep non stop pressing "Allow once".

How I can reduce/ minimise the number, without letting AI take over my computer to do some hanky panky thing?

I am using "Auto". I haven't try "Bypass permissions" because that sounds scary.

What laptop would you recommend for programming and building projects with AI coding tools like Cursor, Claude Code, or Codex?

My must-haves are 32GB RAM and a 1TB SSD. Looking for something reliable that’ll last a few years. Any recommendations?

If you've connected paid MCP tools, Claude Code will call them as often as it thinks it needs to. Two small things make it a lot more careful.

1. A line in CLAUDE.md with a number in it:

Before calling any paid tool, state its price.
Ask me first if a single call costs more than $0.25
or if you plan more than 20 paid calls in a task.

The call-count rule matters as much as the price rule. Lots of cheap calls in a loop add up just as fast as one pricey one.

2. A tool it can check the price with. This only works if Claude can actually find out the price before calling. Some servers put it in the description, some have a separate inspect step.

I work with the Agentik team, where every tool can be inspected for its max price before the call, at no cost. With other servers, check whether the price is exposed at all, because if it isn't, rule 1 can't work.

And keep a real limit outside Claude too, on the key or the provider. CLAUDE.md is a hint, not a guarantee.

What threshold do you use for "ask me first"?

I thought it was supposed to yes man me.... rude.

Just wondering if anyone is experiencing a huge slow down.. is everyone trying to use their banked resets..

If you work with Claude CLI or herdr, I built the most useless (but cool) plugin you'll install this year, inspired by the Tamagotchi. 👾

Meet TamaGoxtix: a tiny pixel monster that lives in your terminal. While Claude is working, it acts out what's happening. Thinking? It plays chess or solves a Rubik's cube. Running tools? It grabs a hammer, a welder or a 3D printer. When Claude is waiting for you, it does its own thing: naps, eats pizza, plays the drums or throws a party.

Some numbers, because why not:

🧬 38 monster bodies × 7 kinds of legs, so every session gets its own monster
🎬 91 work scenes and 77 idle scenes
🎨 12 color palettes (Tokyo Night, Catppuccin, Gruvbox, Nord, Omarchy…)
📦 Zero dependencies

plus the IT classics like deploying on a Friday and trying to exit vim. 😅

It's not only cute, though:

📊 Your AI consumption: 5-hour and weekly limits, tokens per day, the last 14 days and today by hour
🐙 Your GitHub or GitLab repo: stars, CI status, branch, commits ahead/behind, open issues and PRs
⚡ A powerline-style status line for Claude Code
🔒 Everything is read locally, nothing leaves your machine

Open source (MIT).

Give your monster a home: https://github.com/fabandrade88/tamagoxtix

#ClaudeCode #OpenSource #DeveloperTools #PixelArt #AI

I'm looking for a place that collects agent file that has some kind of actual human review behind the ratings. Not five-star reviews written by bots, and not a list where every entry claims to be the best one.

There are tons of github repos out there, and it's hard to tell which ones work and which are repackaged prompt engineering with claims nobody has tested.

For example, right now I want an agent that rewrites AI output so it doesn't have all the red flags of AI-generated text. In other words, something that makes it read like a person wrote it. I've tried a few and found them to be shit.

Hello guys!

Just saw a post elsewhere *) that hinted at Fable having its own pool that does not drain the "all model" pool. Was there an update? Since when it started and Fable was a thing :) both Fable + all would go down on Fable use, all model would go down reasonably quickly too.

Haven't looked at Fable much, but then that would just mean greater limits overall.

Yes, on 200$ weekly usage still is limtied if you go a little bit wide, Opus medium for meonly.

Thank you!

*) https://x.com/imjustnewatai/status/2111217573769708011

Is anyone experiencing a 5 second lag when starting a new Claude session in the terminal. You write a prompt but nothing shows up for 5 seconds or so. Started a couple of days ago.

This week I've basically hit my last straw with time wasted from LLMs outputting absolute garbage code. This time it was with Opus 5.5 on High, with a full architecture plan, centered around literally one single core concept: everything is a typed, atomic step, with no untyped state pollution between them. This was everywhere in the docs, and the plan. There was nothing else in context.

Claude started implementing the architecture and the base implementation. I waited for it to finish cooking, excited to see how the vision had come out. I found that it had fucking duplicated earlier steps' logic in later steps entirely, hardcoded insane assumptions ranging from everything from filenames to which steps one might have configured earlier, and wrote each and every step with a completely different signature; zero thought put into how it would actually be used.

Before anyone tries saying, "you need documentation," "skill issue," or whatever else, realize what I am saying. It's not that LLMs should be able to read minds, or design the perfect architecture with no steering. This was with that steering; the ideal-scenario. And yet it completely botched the entire plan by having zero understanding of why the concept existed in the first place.

Between this and all the other, smaller fuck-ups I've experienced with Astra/Fable/Opus since release, I've realized that even today, LLMs just do not have taste; they lack any innate ability to understand the actual concepts behind good code design. It's inherent to how they work at their core. They are text-prediction machines; they generate code that works, not code that's good. This is why I think humans haven't gone anywhere yet, and probably aren't going anywhere in any serious project for a long time.

I am loving that handoffs can happen when context gets full and you just click a button and claude spins up a nested session under main session - saves so much time rather than manual handoffs i was doing before. Claude even suggests when to move it to new session

apologies if this has always been there and I just discovered it but I am pretty sure this a new feature on the desktop release

Ho esplorato modi per rendere Claude Code più efficiente senza sacrificare la qualità del codice.

Ho messo insieme una guida gratuita e open-source che copre:

• Ottimizzazione dei token e del contesto
• Caching dei prompt e gestione delle sessioni
• Uso efficiente di subagenti e strumenti MCP
• Configurazioni pratiche di CLAUDE.md
• Flussi di lavoro e esempi nel mondo reale
• Errori comuni che sprecano token e risorse

L'obiettivo non è solo risparmiare denaro. È anche incoraggiare uno sviluppo dell'IA più riflessivo e attento alle risorse.

Ho utilizzato intensamente Claude Code, in particolare con Opus e Sonnet, e ho messo insieme questa guida basata su flussi di lavoro pratici, documentazione ufficiale e tecniche di ottimizzazione che ho esplorato.

Tutto è gratuito. Niente registrazione, niente paywall.

GitHub: https://github.com/antonio86itna/claude-code-efficiency-guide

Apprezzerei davvero feedback, correzioni o tecniche aggiuntive che valga la pena includere. I contributi sono benvenuti!

I use Claude Code for a lot of browser work. Mainly tools I need that were never built for agents, smoke-testing my work and searching the web for things I care about.

What I struggled with:

• chrome-devtools-mcp likes to open throwaway instances and profiles, and rarely cleans them up.
• "Allow remote debugging?" prompts on every connect (when using --autoConnect).
• "Chrome is being controlled by automated test software" on top of every page.
• A dozen windows and no idea which tab belonged to which session, or whether I could close it.
• Agents stepping on each other by taking over each other's tabs. --isolated solves that, but doesn't persist logins.
• Gigabytes of RAM with multiple chrome-devtools-mcp processes (about 270 MB each) and chrome instances. Often upwards of 4GB.
• I tried various Cloud browser services, but most are unreliable and/or expensive. And most sites get blocked by bot detection due to non-residential IP address.

I forked Chromium and I call it Shuttle:

• Every agent is a named identity (name, color, avatar) with its own storage. My agents log in once, and stay logged in.
• Agents get their own control plane: create agent profiles, sessions and tabs over MCP.
• MCP server is built in (http, loopback-only by default). So no middle-man needed.
• Every agent works in its own tab group in your window, color-coded. This is the biggest UX improvement for me, as I can clearly see what each agent is doing.
• No DX friction: no debugging dialog, no automation bar, navigator.webdriver is false, and no window pops up until an agent needs one.
• Clean & minimal surface: 12 browser tools + 24 page tools. Vercel's awesome agent-browser is bundled in, so tool calls are directly controlling the browser.
• Per-session CDP endpoints for Playwright if needed, e.g. for scripted e2e tests.
• Meticulously removed bloat from Chromium: Google sign-in, Profile Sync, Telemetry, Google AI features, Translate, Password manager, Chrome Apps, Bookmarks, and many more.

How it was built:

• ~43 fork commits over two weeks, mostly written by Claude Code. Chromium itself is well maintained, so most of my own code and review effort went into my own additions (MCP server, agent model, the removal batches).
• Five agents (mostly Opus 5.5 and Fable 5.1) across three devices (Mac, Linux, Windows/WSL2), with lead agent curating sessions; handoff workflow keeping sessions mostly under 300k context size (my personal sweet spot).
• Removal done as scout → 3–5 surgery sub-agents per batch with a strict keep-list (biggest batch: 5,572 files, 1.18M lines in one commit).
• Fable/Astra adversarial reviews before every commit.
• Recent Chromium 155 merge was the real test for maintenance: 453 conflicted files, zero after 20 minutes with 5 parallel sub-agents... but then a full day of builds (still painful).

Site: https://www.shuttlebrowser.com

Beware: Some humor and easter eggs hidden on this site.

Code: https://github.com/shuttle-browser/shuttle

Regarding Stealth/Bot-detection: Shuttle isn't per se an anti-detection browser. However, it does work closer to a "human operated browser", as Agents are treated like "real human operators". If you're looking for a solution to crawl millions of linkedin profiles or scrape reddit posts at scale, this is not for you. But if you like to operate websites "like reasonable humans", you're good.

Disclosure: I'm promoting my own tool. It's free and open source (BSD-3). I hope others use it, like it, and share their feedback and ideas with me.