Feature request
When a technical user runs an agent, the token usage generated by that agent should be attributed to the user account that created the agent, rather than the technical/runtime user that executed it.
Problem
For agents created and owned by a specific user, usage accounting can become misleading if token consumption is charged to the technical user account that happens to run the agent. This makes it harder to understand the real cost of each creator's agents and can cause token usage to appear under the wrong account.
Expected behavior
- Token usage generated by an agent should be counted against the agent creator's user account.
- The technical/runtime user should still be available for execution and auditing purposes, but should not be the billing/usage owner for those tokens.
- Usage reports should make it clear which creator account is responsible for the agent's token consumption.
Why this matters
This would make usage tracking, quota management, and cost attribution more accurate for creator-owned agents, especially when agents are executed through shared technical users or system-level runtime accounts.
Feature request
When a technical user runs an agent, the token usage generated by that agent should be attributed to the user account that created the agent, rather than the technical/runtime user that executed it.
Problem
For agents created and owned by a specific user, usage accounting can become misleading if token consumption is charged to the technical user account that happens to run the agent. This makes it harder to understand the real cost of each creator's agents and can cause token usage to appear under the wrong account.
Expected behavior
Why this matters
This would make usage tracking, quota management, and cost attribution more accurate for creator-owned agents, especially when agents are executed through shared technical users or system-level runtime accounts.