Well, on a positive note they seem to have also reset all weekly usage on my two max accounts.

Now I can continue my vanity project of having Claude iterate on a single spec.md for hours on end. Surely at some point it won't be shit.

▲

siddboots 4 hours ago | parent | next [-]

Once a spec becomes sufficiently large and detailed and complicated, it becomes very difficult to ensure it is internally consistent. That's why I start every project with a METASPEC.md so that Claude can break up the task of writing SPEC.md into manageable steps.

▲

Incipient 4 hours ago | parent [-]

Everyone knows a philosophy comes before a spec. Claude has to write your applications philosophy first, then you write your spec. But a philosophy is crap without a values statement, so Claude has to actually write that first.

	▲	Esophagus4 4 hours ago \| parent [-]
		Are you vibe coding a project by building an entire corporation around it??

▲

natch 5 hours ago | parent | prev [-]

How do you avoid interruptions for permission? dangerously skip permissions, or is there something less nuclear than that? For me I guess the only less nuclear thing I can think of is running on a sacrificial machine. Is there any better way?

	▲	chmod775 2 hours ago \| parent \| next [-]
		It's literally just writing a spec.md and reviewing it in a loop, fanning out to many agents using "reviewer -> [findings] -> validator (adversarial) -> judge (on conflict)" passes. Before I had it collect a kernel facts document from sources and a bunch of other stuff using the same kind of loop. It's got all it needs. No crazy permissions needed. Also I'm doing this because I find it amusing and somewhat educational on a meta level. If I'd written this myself without a spec it would've been done last month and been likely more correct than what Claude is likely to do once it gets to implementing it (the first spec-free attempt failed miserably). This is way too complex an integration for the poor thing. I had some hopes Fable would get it unstuck, but now we'll never know. Fable did seem to be better at keeping it together. Fun thing to watch on a second monitor though. To answer your question, there is something less nuclear: You can cycle multiple modes with SHIFT+TAB.
	▲	hoten 3 hours ago \| parent \| prev \| next [-]
		claude has auto mode. do shift+tab a few times. it uses a classifier to ask for permission far less often https://code.claude.com/docs/en/auto-mode-config
	▲	crooked-v 2 hours ago \| parent \| prev [-]
		Run it in a VM. Note that just a container probably won't be enough (https://stateofsurveillance.org/articles/ai/claude-opus-4-5-...).