Feature request for product/service
Billing
Describe the request
One of the main reasons we choose to enable API usage is for better code quality, deeper analysis, and more advanced reasoning.
However, what I’ve experienced multiple times is that once API is enabled, even regular Composer agent tasks seem to be deducted from the selected API limit.
This does not feel fair.
The system should work more clearly and fairly:
If a user enables API, then it makes sense that:
- code generation
- deeper analysis
- complex reasoning
are billed from the API — that is completely understandable.
But agent-related actions such as:
- opening and modifying files
- running tests
- general project automation tasks
should not be charged against the API limit.
These are part of the core Composer/agent workflow and should remain within the subscription usage.
A fair system would separate these two clearly.
We are paying for the product, and I strongly believe we should have this level of control and fairness.
Am I the only one who feels this way, or do others agree?