Problem
codeburn antigravity-hook can leave Antigravity configured with an absolute statusLine.command path that later becomes stale. When that target no longer exists, Antigravity repeatedly fails the statusLine command, then auto-disables it after consecutive failures. From that point, CodeBurn reports Antigravity usage as €0 / 0 calls even though agy was used.
This is related to, but distinct from #381. That issue covers missed usage after the CLI exits. This issue is about the live capture hook itself becoming broken because the configured command points at a removed/moved CodeBurn build artifact.
Evidence
Local Antigravity settings contained a command like:
{
"statusLine": {
"type": "command",
"command": "'/path/to/node' '~/codeburn-agy-statusline/dist/cli.js' agy-statusline-hook"
}
}
Recent Antigravity CLI logs then showed:
statusline: command failed: exit status 1
Error: Cannot find module '~/codeburn-agy-statusline/dist/cli.js'
...
statusline: auto-disabled after 30 consecutive failures
After that, CodeBurn showed Antigravity for the day as:
cost: 0
calls: 0
sessions: 0
while Claude and Codex continued to report normally.
Expected
The Antigravity hook should not depend on a fragile absolute path to a temporary/local CodeBurn checkout or build output.
Possible fixes:
- install the hook using the persistent
codeburn binary path, similar to the menubar persistent path handling;
- make
codeburn antigravity-hook install detect and repair stale CodeBurn-owned statusLine commands;
- warn clearly when the installed Antigravity statusLine command points to a missing target;
- avoid Antigravity silently staying in a broken capture state until the user manually runs
codeburn antigravity-hook install --force.
Workaround
Running this repairs future capture:
codeburn antigravity-hook install --force
but historical usage during the broken/auto-disabled window remains missing.
Environment
- CodeBurn:
0.9.11
- Platform: macOS
- Provider affected:
antigravity
Problem
codeburn antigravity-hookcan leave Antigravity configured with an absolutestatusLine.commandpath that later becomes stale. When that target no longer exists, Antigravity repeatedly fails the statusLine command, then auto-disables it after consecutive failures. From that point, CodeBurn reports Antigravity usage as€0/0 callseven thoughagywas used.This is related to, but distinct from #381. That issue covers missed usage after the CLI exits. This issue is about the live capture hook itself becoming broken because the configured command points at a removed/moved CodeBurn build artifact.
Evidence
Local Antigravity settings contained a command like:
{ "statusLine": { "type": "command", "command": "'/path/to/node' '~/codeburn-agy-statusline/dist/cli.js' agy-statusline-hook" } }Recent Antigravity CLI logs then showed:
After that, CodeBurn showed Antigravity for the day as:
while Claude and Codex continued to report normally.
Expected
The Antigravity hook should not depend on a fragile absolute path to a temporary/local CodeBurn checkout or build output.
Possible fixes:
codeburnbinary path, similar to the menubar persistent path handling;codeburn antigravity-hook installdetect and repair stale CodeBurn-owned statusLine commands;codeburn antigravity-hook install --force.Workaround
Running this repairs future capture:
but historical usage during the broken/auto-disabled window remains missing.
Environment
0.9.11antigravity