[FEATURE] Limit batch jobs to for example 25% of subscription tokens and using to extra tokens

Resolved 💬 4 comments Opened Apr 12, 2026 by AndersEdin Closed Apr 12, 2026

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

I want to always have tokens to work interactively, but also want to schedule large independent tasks as batch work.
It is easy that the batch work consumes all the tokens.

I also want to limit batch work to only use subscription tokens, so I can easily use up all of them. It would be ok then
to get extra tokens for the interactive work if I find this important.

Proposed Solution

  • Allow limiting a batch job to using only a percentage of the subscription tokens
  • Allow limiting batch jobs to only use subscriptions tokens (and never extra tokens)

This would allow me to schedule 2-3 batch jobs in parallel, and still have tokens over for interactive work.
If I then find the interactive work important, I can purchase extra tokens without risking that the batch work
eats up all of them.

Alternative Solutions

_No response_

Priority

High - Significant impact on productivity

Feature Category

CLI commands and flags

Use Case Example

  1. I am working on a geometry package
  2. I have created a project plan with multiple work items that are relatively independent
  3. I also have work items that needs to be explored interactively before including in project plan (a pre-study)
  4. I want to start 2-3 batch jobs using at most 25% of the subscriptions tokens
  5. I use remaining 25% or 50% for interactive work
  6. If the interactive work needs more tokens, then I can purchase these knowing that the batch work will not use them

Additional Context

_No response_

View original on GitHub ↗

This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗