-
Notifications
You must be signed in to change notification settings - Fork 2
Statusline Integration
Ivan Seredkin edited this page May 23, 2026
·
2 revisions
Stub. Tracked as a "still to write" page on the Home hub.
A wiki-level companion to the in-repo docs/statusline-contract.md. The in-repo doc owns the schema; this page will own the integration story across surfaces:
-
The shared JSON shape —
GET /analytics/statuslineandbudi statusline --format json, consumed by the CLI statusline, the Cursor / VS Code extension, and the cloud dashboard -
Slot vocabulary —
1d/7d/30d/session/message/branch/project/provider. Why1d/7d/30dare rolling (not calendar) windows. Legacytoday/week/monthaliases at load time -
Provider-scoping — strict filtering on
provider=claude_codeetc.; never blended unless requested -
Install paths —
budi initwires Claude Code'sstatusLineautomatically;budi integrations install --with claude-code-statusline/--with cursor-extension; idempotent merge with existing settings -
Doctor checks — what
budi doctorflags as a missing-statusline WARN and why - Host- vs. provider-scoped surfaces — when a multi-provider host (VS Code with Copilot Chat + Cursor) needs the aggregated path
-
docs/statusline-contract.md— schema SOUL.md— Statusline contract section-
STATUSLINE_SLOTSincrates/budi-core/src/config.rs
budi · Issues · Releases · app.getbudi.dev · getbudi.dev
Start here
ADRs — Data & privacy
ADRs — Ingestion
ADRs — Pricing
- Model Pricing – Embedded Baseline and Runtime Refresh
- Custom Team Pricing and Effective Cost
- Codex Cost Model – Marginal-Token Counting
ADRs — Provider contracts
Operational references
- Daemon Lifecycle and Autostart
- Provider Plugin Contract
- Cloud Sync Mechanics
- Statusline Integration
- Operations and Observability
- Release and Versioning
Ecosystem