Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Feature: per-agent usageCommand in acpClients to surface subscription plan quota

Open
#3,078 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
rust
Domain
backend, desktop

Research direction

Start by locating the acpClients configuration, the ACP agent card/settings row, and the existing command execution or refresh paths. Trace how an agent's configuration reaches the UI; done means an optional usageCommand and interval can be configured per agent, invoked on demand or during refresh, and its text or JSON result is displayed without changing the ACP protocol.

Written by the indexing model from the issue text.

Description

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.

Dominant language
Rust
Stars
2.3k
Forks
236
Avg merge
2h 56m
Merged PRs (30d)
619

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from GCWing/OpenBitFun

All issues in GCWing/OpenBitFun

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.