aidown in your terminal

When Claude Code or Codex fails with an error, aidown sends one small anonymous report. All reports together show an outage within minutes, before the official status page changes.

curl -fsSL https://aidown.dev/install | sh

The installer shows what it changes and asks first. It backs up every file it edits. Source: /install and /aidown.sh (plain shell, read it before you run it).

Exactly what is sent

`tool`	claude-code or codex
`event`	rate_limit, overloaded, server_error, auth, billing, invalid_request, unknown, or turns (an hourly count of finished turns)
`model`	for example claude-opus-5-5
`ver`	tool version, for example 2.1.304
`n`	number of turns (only for the hourly count)
`id`	a random install id made on your machine

Never sent: prompts, answers, code, file paths, project names, session ids, email, account ids, API keys or tokens. The server rejects any other field.

How it works

Claude Code: hooks on StopFailure (the error type), SessionStart and PostModelSwitch (the model, kept on your machine), and Stop (counts turns locally).
Codex: hooks on Stop and SessionEnd. The script reads only the task_complete lines of your local session file to find the error type. Run /hooks in Codex once to trust it.
Every hook runs in the background and always exits with 0. It cannot slow down or break your tool.

On the server

We store the fields above, a hash of your install id, and a hash of your IP address with a salt that changes every day. We never store the IP address or the raw install id. Raw rows are deleted after 30 days; hourly totals stay.

Control

`aidown status`	live status of AI tools in your terminal
`aidown pause`	stop sending (aidown resume to start again)
`aidown forget`	delete all reports from your install on the server
`aidown uninstall`	remove the hooks, delete your server data and ~/.aidown