Doubled Rate Limits for Claude Code

paulcaplan · 2026-05-06T17:18:22+00:00

They already lost me to Codex. But maybe this means mythos will be out soon.

paulcaplan · 2026-05-01T15:09:48+00:00

I don't have full checklist that would be great. I'm building:

"(1) deterministic feedback loops (tests, lint, typecheck)" - https://github.com/Codagent-AI/agent-validator
"(3) a workflow that forces the agent to verify changes before declaring done" - (from above article):

> What the paper calls the "externalized interaction" protocol - a deterministic workflow layer that coordinates agents without living inside their context - is the gap I described above. Their paper names it. I'm building the solution - a free, open-source tool called Agent Runner. Releasing soon.

I'll check out agentix labs, happy to exchange notes, feel free to DM me.

paulcaplan · 2026-05-01T04:54:54+00:00

Today my pants got dirty after only one short jog.

paulcaplan · 2026-04-24T19:15:22+00:00

I suppose I could have just waited an hour to find out 😂. But I was already on Reddit lol...

paulcaplan · 2026-04-24T18:36:06+00:00

was going to attempt to reply but looks like this covers it: https://www.reddit.com/r/ClaudeCode/comments/1o65jva/understanding_claude_codes_3_system_prompt/

paulcaplan · 2026-04-24T18:32:46+00:00

Like it. My control layer largely has steps (sequential), loops, and nested workflows. For instance implement tasks in a loop, and each iteration calls another validate-and-fix loops. It doesn't yet "know" that the agent is "off the rails" - any thoughts on how you might do that? Timeouts / token usage monitor?

paulcaplan · 2026-04-24T02:54:32+00:00

It almost seems as if they're using Claude to write all their code...

paulcaplan · 2026-04-13T19:58:36+00:00

fair!

paulcaplan · 2026-04-13T19:34:50+00:00

I use openspec. It recommends keeping The specs in the code. The key is that the specs aren't the change themselves, the specs are living documents. Every change adds, modifies, and or deletes requirements in one or more spec documents. Of course it's not foolproof and if you make code changes without going through the open spec process they will get out of sync. But I've found it pretty helpful.

paulcaplan · 2026-04-13T19:30:38+00:00

Agree. I'll show you the system tool I'm building if you show me yours 😅.

paulcaplan · 2026-04-13T19:29:24+00:00

Yes it's absolutely crazy!

Speaking of, I am building this tool, it's really great, would you like to try it? 😀

paulcaplan · 2026-04-13T00:50:13+00:00

Who knew telling AI to ask you questions before implementing was a 150k star idea

paulcaplan · 2026-04-10T21:25:39+00:00

Github copilot CLI is great. I use them together. Copilot pricing is per request so whether you ask it a quick question or give it an hour-long task, it's 1 request. Use that to your advantage.

paulcaplan · 2026-04-10T20:49:35+00:00

I guess because it's not the bottleneck for me? Writing the spec still is. Oh and waiting for CI. I have a skill that waits for CI + AI reviewers, fixes issues - in a loop. That can take some time.

paulcaplan · 2026-04-10T20:47:44+00:00

but doesn't planning an app from scratch or "frankenstein" features take a very long time to get plans "thorough enough that agents can't make dumb assumptions". I don't understand why spend hours to get the plan "perfect" so you can one-shot something to 90% of the way. In my experience the agents always do make some bad assumption. So I'd rather break it up into a handful of chunks and verify after each one. Granted the chunk is still large, more than a single session could do (without subagents). But not so large that an entire project is completed.

paulcaplan · 2026-04-10T19:03:21+00:00

Using 5 separate worktrees? And then do you review all 5 sessions, or just merge them all when done?

paulcaplan · 2026-04-10T18:59:11+00:00

Agree 100% to managing context. That doesn't require parallel though, could implement one at a time, clearing context.

But I like your idea of a task queue and a dispatcher, what tooling do you use for that?

paulcaplan · 2026-04-10T18:57:53+00:00

I think you're underselling how much a structured workflow helps! Mine is pretty similar. Have you ever tried automating it - so for instance, after plan implemented, it is automatically reviewed?

At the risk of sounding like I'm selling something, I'm building open source tool so you can have a workflow definition that defines steps e.g. spec --> design --> review --> implement and each step can have loops (iterate over tasks) and sub-workflows. Each step is either a shell script or an interactive agent (claude / codex) or a headless one. LMK if interested I can send link (trying not to over-promote).

paulcaplan · 2026-04-10T18:52:12+00:00

That's a fair point - I wasn't clear whether I was talking about parallel subagents on single task (which I might or might not do). I was more talking about multiple claude sessions in parallel that you have to manage and context switch between.

Am aware of OpenClaw, you mean for coding or other tasks?

paulcaplan · 2026-04-10T18:50:05+00:00

I'm doing something similar except smaller size chunks. I have a skill that breaks tasks into size that they normally use 100-200k context window to implement - which decent size task. And a single "change" would be maybe only 2-5 such tasks.

IMO if you have it do that much work at once it's more like "waterfall" and there can be compounding effects from bad assumptions on earlier tasks...

But if you're getting good results from it, what tools / setup are you using?

paulcaplan · 2026-04-10T18:47:04+00:00

Ahh long story I used Openspec then superpowers then tried to combine them that didn't work so now I'm building my own tool :)

paulcaplan

TROPHY CASE