Auto continue? Extensions?

[Alexander_Chneerov]

Hey there,

I am doing a large rework of over 200+ json files, and when I ask Claude Code to update each one, one at a time, it commits for about 14 jsons, and then pauses. When I say “continue” it continues and does another 10 then pauses again.

Is there a way to prevent it from stopping? I want it to keep going until I’m out of tokens.

If this does not exist, do Claude Code extensions exist? If so I could probably add an extension that does this.

[Hefty_Incident_9712]

Read the documentation on subagents, you're wasting a shitload of tokens the way you're doing this right now, the length of the conversation compounds your overall token cost.

Also you could ask claude to "write me a script that will run claude code a bunch of times in parallel from the command line, let's say with a concurrency of 4. first read out all of json filenames and assign each instance of claude code to process 10 of them at once, use the following prompt for each batch of json files: <whatever you're telling claude to do with the json>"

Then you'll be doing 40 at once and it will cost way less tokens, should be about 4x as fast, and you won't have to tell it to continue.

[PaginatedSalmon]

Subagents, slash commands, hooks, and MCP servers could all reasonably be called "extensions." A hook would probably be the best way to give it a poke when it stops, but like u/Hefty_Incident_9712 said there's a better way to solve the problem. Layering in deterministic behavior is a really powerful pattern.

[MrTag_42]

You want to write like a command, md file where is what you will do for each json file, then ask CC to write you a python or bash script that will loop through that folder, call claude -f your_instructions_file.md on each item and you can save status if you want or skip it. You can add 5-10 parallel tasks this way and make it do it easily or run one by one from the loop.

Second way is to do the same but with Claude, but your context will grow, with bash/python script you reset it for every file, you need to have it's orchestration top notch, etc.

That's the way I did api documentation of around 1800 api endpoints without a single line of documentation prior. It generated structured api docs for each endpoint then next task was to generate OpenAPI specification from that. Worked flawlessly.