# The ACC indicator

The indicator describes incoming messages for the current chat. It does not describe
other chats, confirm that a message was read, or promise when an agent will answer.

In Claude Code, only the status glyph carries color: green for `●`, warning color for
`!`, and neutral for `…`. All supported clients use the same fixed green (`#2c7a39`) for
`●`, without dimming. Claude uses its theme for the other states. The name
and `turn`/`inbox` qualifier keep the ordinary footer color. No background is added.

Antigravity's command emits ANSI foreground color around only the glyph, even when
stdout is a pipe. Existing installed commands need no new arguments. `--json` and
`--details` keep their plain, uncolored output.

| Display | Meaning |
|---|---|
| `ACC ●` | ACC is active. This chat has an automatic delivery binding with no newer recorded failure. A busy client can queue a request. |
| `ACC ● · turn` | ACC is active. Messages arrive on the next normal turn. |
| `ACC ● · inbox` | ACC is active. The agent reads messages through `acc inbox`. This does not imply a polling schedule. |
| `ACC …` | The Claude indicator is reading state or waiting up to five seconds for startup hooks. Failed reads keep it until a read answers or three reads in a row fail. |
| `ACC ! · turn` or `ACC ! · inbox` | ACC observed a failure. The qualifier names the remaining reception path. |
| `ACC !` | The chat is not registered, or the indicator cannot read its state. |

An unsupported wake-up capability is a normal `turn` or `inbox` mode. A failure of an
expected automatic channel retains `!`; it does not silently become a normal fallback.
The current `--delivery off` setting also uses the normal fallback. Details explain that
setting. Enabling the indicator does not enable automatic delivery or change its consent.

An idle chat does not lose its indicator because its heartbeat or delivery lease is old.
The sender verifies and renews an expired lease when it next attempts delivery. The badge
uses local observations. It does not test the endpoint on each refresh. Lease validity is
available in JSON as `leaseCurrent`, separately from reception and health.
Offer diagnostics are published separately from delivery. A slow diagnostic write
does not hold up offers to the next participant or change delivery receipts.

## Enable or disable

```sh
acc install --adapter claude_code --indicator on
acc install --adapter antigravity --indicator on
acc install --adapter kimi --indicator on
acc install --adapter grok --indicator on
acc install --adapter claude_code --indicator off
```

The initial preference is off. A later install or automatic update keeps the saved choice
when `--indicator` is omitted. `--dry-run` makes no changes. Normal uninstall removes the
indicator and keeps status-line settings that the user changed.

## Client surfaces

| Client | Integration and limits |
|---|---|
| Claude Code | From 2.1.287: a plugin mod adds a native footer label. It does not change `settings.statusLine`. Use `/reload-plugins` in an open session after installing. Client policy can disable mods. |
| Antigravity CLI | A status-line command adds ACC below the built-in line. If a custom command exists, ACC passes it the original stdin and appends the badge. Existing padding and stacking choices remain. Start a new CLI session after changing settings. |
| Codex and Gemini CLI | No automatic indicator installation. Their native status lines do not expose this command surface. |
| Kimi Code | From 2.1.1: compose one line with the existing custom command, or available mode/model/cwd/branch fields. Run `/reload-tui`. The native context/warnings line remains. |
| Grok | From 1.0.46: compose the optional status row with the existing command, or configured built-in items. ACC adds idle refresh once per second unless an interval is already configured. Start a new Grok session. |
| Other hosts | A host that provides the native session id can run `acc-indicator` as a custom widget. This does not certify that host's UI integration. |

Claude prints one diagnostic when a new problem appears. `/acc-status` shows the current
explanation and recovery step without a model request. Healthy refreshes do not print
messages. A read that fails or does not answer describes the indicator, not the chat.
The badge keeps the last observed state until three reads in a row fail; only then
does it show `!` and print the diagnostic. A slow read says so and does not suggest
reinstalling, because a reinstall cannot make a busy machine answer sooner. Antigravity's command surface has no equivalent notification: only a problem
adds `acc doctor` to the compact line. Run that command in the project for diagnostics.

The Antigravity wrapper runs an existing enabled command with a 700 ms limit and a 64 KiB
output limit. A disabled old command stays disabled. Disabling ACC restores only the
fields ACC changed and still owns. A user replacement command takes precedence.
Removing or replacing Antigravity's ACC command also survives repeated updates.
To add ACC again after that edit, disable the indicator and then enable it.

On POSIX, timeout, output overflow and indicator cancellation stop the previous
command's owned process group. Windows uses a detached Node launcher because a
detached shell loses its standard input handles. The launcher starts a hidden shell
with the original stdin/stdout. ACC stops the launcher and its descendants with
`taskkill /T /F`. Scripts that leave background processes
running after the shell exits must stop those processes themselves on Windows.

## Kimi and Grok composition

ACC puts its compact badge first so a narrow terminal cannot truncate it behind a long
path. Existing custom commands receive the original stdin. Kimi keeps their first output
line; Grok retains the remaining lines. Disabling or uninstalling restores the old command
and only the presentation fields ACC still owns. A later user replacement takes precedence.

Kimi passes `sessionId`; Grok passes `session_id`. An empty Kimi ID is its welcome screen,
before a session exists, so ACC retains the footer without a registration error.
A registered Kimi normally shows `ACC ● · turn`; Grok shows `ACC ● · inbox`.

Kimi's snapshot does not expose goals, background task counts, thinking effort, swarm/tower
badges, detailed Git status, or rotating tips. These first-line elements cannot be retained
when composing the built-in footer; the native context/warnings line remains. Existing
custom commands can retain any extra information they already render. Kimi limits the entire
command to 300 ms; ACC bounds its own work to 180 ms after module loading and the previous
command to 80 ms. A host timeout can retain the last line until a successful refresh.

TOML comments and unrelated settings are retained. Ambiguous inline status tables or dotted
status declarations are refused without rewriting them; use a normal `[status_line]` or
`[ui.status_line]` table. The version floors above reflect native UI captures, not new
message-delivery certification.

## Read-only command

```sh
printf '%s' '{"session_id":"native-session-id"}' | acc-indicator --adapter claude_code
acc-indicator --adapter claude_code --native-session native-session-id --details
acc-indicator --adapter claude_code --native-session native-session-id --json
```

Antigravity supplies `conversation_id`; `session_id` is also accepted. The reader selects
the saved room for that adapter and native id. It never guesses from the current directory
or scans other sessions. Output contains no generation token, endpoint, or message body.

The reader does not acquire a runtime lease, schedule updates, create a workspace,
recover a journal, send a heartbeat, renew delivery, or contact a client socket. The
managed launcher resolves the active runtime on each call. A concurrent update can cause
one failed read; a later refresh can recover without retaining the outgoing generation.

The router publishes an optional, bounded observation after a transport accepts or rejects
a send. For records with equal timestamps, a delayed older write cannot replace a newer
success or failure.
The indicator compares the resulting observation with the latest hook handshake for the same generation.
This diagnostic contains only time, outcome, and a closed reason code. Delivery receipts
and immutable history remain authoritative. An unavailable diagnostic cannot fail a send.

An unreadable state produces a closed error and a recovery command. It never renders raw
file content. A command stops waiting after 1.5 seconds. Claude refreshes every five seconds,
with one-second checks during its bounded startup period. Claude allows each read five
seconds: on a loaded machine the command's own start took up to 1.3 seconds inside
Claude, before its 1.5-second wait begins.