Summary
When using BYOK in autopilot mode, the CLI still says it is "continuing autonomously" and reports that it charged one premium request.
Problem
In BYOK mode, the messaging appears to imply platform-managed premium usage even though the session is using the user's own key.
Current behavior
- Autopilot mode says it is continuing autonomously
- The UI/message says that one premium request was charged
Expected behavior
When BYOK is active, autopilot messaging and usage reporting should reflect that accurately and should not claim that a premium request was charged if that is not actually what happened.
Notes
This looks especially confusing in autopilot mode because the autonomy wording and premium-request wording together suggest hosted premium consumption rather than BYOK execution.
Summary
When using BYOK in autopilot mode, the CLI still says it is "continuing autonomously" and reports that it charged one premium request.
Problem
In BYOK mode, the messaging appears to imply platform-managed premium usage even though the session is using the user's own key.
Current behavior
Expected behavior
When BYOK is active, autopilot messaging and usage reporting should reflect that accurately and should not claim that a premium request was charged if that is not actually what happened.
Notes
This looks especially confusing in autopilot mode because the autonomy wording and premium-request wording together suggest hosted premium consumption rather than BYOK execution.