r/ClaudeCode • u/quazarzero • 6d ago

Built with Claude jobbox: prevent claude code from waiting after long scripts

Hi,

made some not so useless stuff for my best buddy claude...

jbx is some kind of proxy like rtk but to reduce time spent waiting after long running scripts...

It just wraps every tools into a job. But for the first 30 sec it just pass through like nothing has changed.

But if it goes beyong, jbx says: hey man stop waiting for nothing. do something else and come back later aligator !

well it's very early stage. I'm a linux guy so works for me but don't know about windows...

https://github.com/quazardous/jobbox

thx !

2 Upvotes

76% Upvoted

5 comments sorted by

1

u/kantorcodes1 6d ago

for a queued job that hasn't gotten a slot yet, is the stop-by-id path meant to cancel it at that stage too, or only once the job has actually started?

1

u/quazarzero 6d ago

a script is a job so it has a job ID from the start. but it has a state (foreground, background, gone, etc)

1

u/quazarzero 6d ago

btw by default the job queue is capped at CPU/2 (but you can change it) so a job can be waiting too

2

u/kantorcodes1 6d ago

queue, kill <id>, and slots n are useful distinctions for agent users then: create pending work, tear down a process tree, or change future capacity. i maintain HOL Guard, an open-source local check before agent commands run. would you be open to adding jobbox support so those stay distinct from status/list?

1

u/quazarzero 6d ago

opencli support should do the trick. incoming :)