Context
ACP has no concept of plan quota (limits, reset windows, burn-down). Subscription-backed CLIs — Claude Max, Codex (ChatGPT), Kimi coding plan, GLM coding plan — each expose their remaining usage through their own CLI commands or account endpoints, none of which is visible inside BitFun. When orchestrating a fleet of subscription CLIs as ACP agents, the orchestrator currently has no way to see which agent's plan is nearly exhausted before dispatching work.
Proposal
Add an optional field on each acpClients entry, for example:
{
"kimi": {
"command": "kimi",
"args": ["acp"],
"usageCommand": "kimi usage --json",
"usageIntervalMinutes": 30
}
}
usageCommand: a shell command whose (text or JSON) output represents that agent's remaining quota- BitFun runs it on demand (button on the agent card / ACP settings row) and/or on a refresh interval, parses, and displays the result next to the agent
This keeps quota semantics out of the ACP protocol (where they don't belong) while making them visible exactly where dispatch decisions are made.
Use case
Multi-agent orchestration over subscription CLIs: check remaining quota per agent before assigning a long-running task, and avoid routing work to an agent whose plan window is exhausted.
Context
ACP has no concept of plan quota (limits, reset windows, burn-down). Subscription-backed CLIs — Claude Max, Codex (ChatGPT), Kimi coding plan, GLM coding plan — each expose their remaining usage through their own CLI commands or account endpoints, none of which is visible inside BitFun. When orchestrating a fleet of subscription CLIs as ACP agents, the orchestrator currently has no way to see which agent's plan is nearly exhausted before dispatching work.
Proposal
Add an optional field on each
acpClientsentry, for example:{ "kimi": { "command": "kimi", "args": ["acp"], "usageCommand": "kimi usage --json", "usageIntervalMinutes": 30 } }usageCommand: a shell command whose (text or JSON) output represents that agent's remaining quotaThis keeps quota semantics out of the ACP protocol (where they don't belong) while making them visible exactly where dispatch decisions are made.
Use case
Multi-agent orchestration over subscription CLIs: check remaining quota per agent before assigning a long-running task, and avoid routing work to an agent whose plan window is exhausted.