Codelight

codelight - coding-agent status & remote control

Live status, usage, conversation following, and remote-control prompts for
supported coding agents. Watch grouped working/waiting/idle state on a desk
screen, phone, GNOME and KDE Plasma panels, or in VSCode — and, when you're
away from the keyboard, approve permission prompts and answer agent
questions from supported clients. Pick and choose whatever suits your needs:

Currently supported agents

1. Copilot usage is the organization's pooled monthly AI-credit meter — needs agents.copilot.github_org and a token.
2. Copilot answers questions only where the IDE hook path exposes them.
3. Cursor shows a monthly included-usage meter read from the local Cursor auth token (no setup); it hides if you are not signed in to the IDE.
4. Cursor remote-allow bypasses the prompt in the IDE; the cursor-agent CLI is deny-only (its own command allowlist still prompts).
5. Cursor exposes no agent-asks-the-user hook to intercept.
6. No Grok usage meter: the CLI runs on the SuperGrok subscription, whose weekly rate limit is not machine-readable (cookie-gated web page, and the CLI's OAuth token is rejected by the rate-limit API). xAI's separate developer-API credit pool *is* readable (opt-in via a billing management key) but the subscription-based CLI never draws on it, so it would always read ~0%. See companion/AGENTS.md for the two-wallets detail.
7. Grok's single blocking hook cannot approve remotely, and it has no agent-asks-the-user hook.
8. OpenCode has no hooks; codelight follows its local HTTP server's event stream (run opencode serve --port 4096, or set agents.opencode.server_url).
9. OpenCode is BYOK (no provider quota), so the meter is an opt-in monthly $-budget you set (agents.opencode.monthly_budget_usd) against spend read from…