claude-code - 💡(How to fix) Fix [FEATURE] Limit batch work to only use subscription tokens, and not extra tokens [2 comments, 2 participants]

TL;DR

Implement a feature to limit batch work to only use subscription tokens, configurable both globally and per batch job.

Guidance

• Introduce a new setting in the user settings to control the token usage for batch work, allowing users to set a percentage of subscription tokens that can be used.
• Add a command-line flag for batch jobs to override the global setting and specify the token usage for a specific job.
• Consider implementing a token allocation system to ensure that batch work and interactive work use separate token pools.
• Review the existing token management system to ensure it can handle the new feature without affecting the overall system performance.

Example

No code example is provided as the issue lacks specific technical details about the current implementation.

Notes

The proposed solution requires changes to the existing system, and its implementation may depend on the specific architecture and technology stack used. The feature's priority is marked as high, indicating its significant impact on productivity.

Recommendation

Apply a workaround by implementing a temporary solution, such as a script or a manual process, to limit token usage for batch work until the feature is fully implemented. This will allow users to better manage their token usage while the development team works on the permanent solution.