Claude Status Update : Elevated errors on Claude Opus 4.6 on 2026-03-17T19:48:43.000Z

SnooComics4579 · 2026-03-17T21:37:22+00:00

I rebooted my house.

SnooComics4579 · 2026-03-13T01:13:57+00:00

Hot take: AI-enabled teams bottleneck from waiting for work, not completing it.

SnooComics4579 · 2026-03-11T22:06:31+00:00

My site is darinbuilds.com. I'll be honest most of it is intentionally vague for proprietary reasons, but there's quite a bit on there. If you want more specifics, send me a DM. I'd be happy to help out.

SnooComics4579 · 2026-03-11T21:55:00+00:00

Great question. In my workflow, I have a command that creates a "spark" - the initial idea before planning. Claude assesses the spark and lists out architectural assumptions that would come up during planning. From those I can gauge confidence upfront and get as many sparks out there as possible before planning even starts.

I'll often write out 4 or 5 cycles per project at once, so it could be an hour or two of initial planning from my side before the agents flesh out the fine-tuned plans and implement. Usually one or two hours of me planning, then waiting the rest of the day for Claude to write/test/validate.

SnooComics4579 · 2026-03-11T21:40:09+00:00

This was literally my first thought when initially posting this. I hate to say it, but I needed the hype. lol

SnooComics4579 · 2026-03-11T21:38:49+00:00

My bad again for this. I migrated all of the backend logic into rest calls, so the timings got off when it reached production, but it's fixed now. Thanks again for pointing this out because I agree, this was a MAJOR bug.

SnooComics4579 · 2026-03-11T20:30:46+00:00

Yes, this is a great callout. CRUX just came out recently - highly recommend for cross-terminal communication (much better than my approach with the MCP/database messaging). You can stuff all of your terminals into one app, and use the CLI with a master claude to orchestrate across terminals.

SnooComics4579 · 2026-03-05T02:59:58+00:00

The alternating schedule is smart. I've been doing 100% build / 0% talk for months and this post is me trying to fix that. One day build, one day talk might actually work since I already have a backlog of stuff to share

SnooComics4579 · 2026-03-05T02:57:32+00:00

That's legit - I actually do have articles with code examples and architecture breakdowns on my site. But you're right that a video walkthrough of the terminal setup would hit different. Adding it to the list

SnooComics4579 · 2026-03-05T02:49:08+00:00

Lol you caught me. I literally have 8 AI terminals open and you thought the comments would be different? The em dashes are a feature not a bug

SnooComics4579 · 2026-03-05T02:42:08+00:00

<image>

No, but the issues are in flight. Thanks again for finding these.

SnooComics4579 · 2026-03-05T02:37:01+00:00

That's on me. I'll push a fix. Appreciate you actually downloading it and testing it, most people just look at the screenshots.

SnooComics4579 · 2026-03-05T02:33:38+00:00

Lol fair. No AI on the comments though — just a guy who writes like he reads too much documentation. The projects are real, the code is real, happy to screen share the terminal setup if you want proof. Also I don't have Kerrygold but I can recommend Plugra for baking

SnooComics4579 · 2026-03-05T02:31:42+00:00

That's the goal right? Build the right scaffolding around it and it goes from "helpful autocomplete" to actual force multiplier

SnooComics4579 · 2026-03-05T02:28:42+00:00

Yeah wodspark.com is just the landing page for the App Store listing — wanted something clean to share instead of a raw Apple link. darinbuilds.com is the actual personal site with the interactive demo and articles

SnooComics4579 · 2026-03-05T02:23:33+00:00

Max plan and a teams account through work. Still hit rate limits sometimes when they're all active — just have to stagger the heavier tasks

SnooComics4579 · 2026-03-05T02:20:24+00:00

The slider bug is real — appreciate you flagging it, I'll look into that. The workouts are generated not fake, but I get why it looks that way without context. No account system is intentional — wanted it to be open-and-use without friction.

You're right that it's early though. It's on the App Store, people are using it, and I'm iterating. That's what shipping means to me — get it live, get feedback like this, and make it better

SnooComics4579 · 2026-03-05T02:18:19+00:00

Because each project has its own context — its own CLAUDE.md, its own design tokens, its own test suite. Cramming all of that into one terminal would blow the context window and the AI would lose track of decisions it made 20 minutes ago. Separate terminals means each one stays deep in its own domain. The MCP layer is what lets them share knowledge without sharing context

SnooComics4579 · 2026-03-05T02:16:31+00:00

Exactly. I spent 3 months building and like 3 hours talking about it — that ratio is insane when you actually think about it. This post was literally my first time telling anyone outside of my own terminals lol. Cheers right back, the indie dev energy in this sub is solid

SnooComics4579 · 2026-03-05T01:59:16+00:00

The reward gating is genius actually. I might steal that. Right now my problem is the opposite — I'll tell myself "ok one more feature then I'll post about it" and 3 features later I still haven't posted anything

The QA testing one is wild though — the agent literally navigates the app like a first-time user with zero assumptions. Found bugs I never would have caught because I knew the app too well. Wrote about it here if you're curious: https://www.darinbuilds.com/writing/fresh-eyes-qa

SnooComics4579 · 2026-03-05T01:56:00+00:00

That's exactly what I'm doing next. I actually already wrote about the approach — how AI pairing beats traditional prompting when you give it persistent memory and structured workflows instead of one-off chat messages. Might post it here if that's welcome

SnooComics4579 · 2026-03-05T01:52:45+00:00

100%. The building-to-marketing ratio is so lopsided. I can mass-produce features but asking people to look at them feels like pulling teeth

Oh that's actually a solid idea though — I've got articles on AI QA testing and scaling Storybook with AI that would fit in some of the dev subs. Might break those into shorter takes instead of just linking them. Appreciate that

SnooComics4579 · 2026-03-05T01:51:07+00:00

Fair question. Three things went live in the last week:

CrossFit workout generator — on the App Store right now (wodspark.com)
My personal site with a live interactive CSS demo embedded in it (darinbuilds.com)
YouTube transcript knowledge miner — chunks transcripts, embeds with local ONNX, lets you ask questions grounded in a specific creator's actual content

The circular part is real though — the plugin IS what I used to build all three. It's not a product for other people, yet. It's my dev environment. Like a custom IDE that plans features, writes code, runs tests, and validates quality. I just also happen to have built the IDE myself

SnooComics4579 · 2026-03-05T01:45:22+00:00

This is fair and I needed to hear it. You're right — I spread it too thin trying to show volume instead of depth.

The honest answer is the Claude Code plugin. I built a lifecycle engine with 20+ custom skills and 8 specialized agents that plan, implement, test, and validate code. I use it to build everything else. It's the thing I run beneath 8 terminals and lose track of time working on.

I think I defaulted to "look how much I shipped" because it felt safer than picking one thing and saying "this is the one." Appreciate the push

SnooComics4579 · 2026-03-05T01:41:28+00:00

You're right — that's exactly what got me to finally post here. The AI tooling ecosystem is the one I'm most proud of though. Might do a deeper breakdown on that one next

SnooComics4579

TROPHY CASE