A terminal status light for your agent hooks, with a five-check quick check (free sample)
by PaperChaseWebb
From Agent Status Hardware: an event-to-state map for Claude Code and Codex hooks, five rules, a script that shows one colored light for all your sessions in a spare terminal window, and a read-only quick check with a worked example.
- Price
- Free
- Difficulty
- Beginner
- Setup
- 10 min
- Format
- .md file
agent-status-light-event-map-free-sample.md · 13 KB · direct download, no signup
What you end up with
When any agent session asks for a permission, a terminal window turns red, blinks and rings the bell, even while other sessions keep working.
What you get
- The event-to-state map
- status_mini.py: hook, watch, check and a worked example
- Five rules for status signals
- Hooks for Claude Code and Codex
- A one-line install
- Worked example: 5 findings, then 0
Who it is for
Anyone who misses agent permission prompts while working in another window and wants a fix with no hardware.
Works with
Solid chips: the agent is named in this listing's own tools list. Dashed chip: Plain Markdown, so it also pastes into other agents such as Grok Bot, Hermes, OpenClaw or Muse. We list those as compatible by format only, not as tested.
Tools needed
Cost to run: Free.
Time to result: About ten minutes to a working terminal light
Sample prompt from the pack
Save the python block in this file as ~/status_mini.py. Show me the hooks block from the file merged into my settings, as a diff, and wait for my yes. Then run status_mini.py example demo and check on both folders, and paste the output.
The map and the rules are in the file.
Free preview of the file
# A terminal status light for your agent hooks, with a five-check quick check (free sample of Agent Status Hardware)
Version 1.0, 2026-10-28. By PaperChaseWebb. For Claude Code and Codex hooks, with notes for Hermes and Grok Bot. One Markdown file and one Python 3 script, standard library only. The script was tested on its worked example (5 findings, then 0) and with sample hook payloads for Claude Code and Codex. It was not loaded inside a harness for this release, and it drives no hardware: the light is a block of color in a terminal window.
The common way to miss an agent's question is simple: it asks for a permission at minute two, you are in another window, and you find out at minute twenty. This sample gives you the smallest honest fix. Each hook writes one line of state, a second terminal window shows one colored block for all your sessions, and when any session needs you it turns red, blinks and rings the bell, whatever the other sessions are doing.
## Install in one line
Save this page as FREE-SAMPLE.md, then:
```
python3 -c "import re;t=open('FREE-SAMPLE.md').read();open('status_mini.py','w').write(re.search(r'~~~python\n(.*?)~~~',t,re.S).group(1))"
cp status_mini.py ~/status_mini.py
python3 ~/status_mini.py watch
```
Leave watch running in its own window. The hooks print nothing, because the agent owns its own terminal.
## The event-to-state map
| Hook event (Claude Code; Codex uses the same names) | State | Light |
|---|---|---|
| PermissionRequest, NotifiWorth knowing
- The sample drives no hardware and has no stale state, Hermes hooks, Grok Bot rules, approvals or full checker; the full pack adds them.
- On 2026-10-28 the quick check gave 5 findings on the worked example, then 0, and sample payloads for Claude Code and Codex gave the expected states. It was not loaded inside a harness.
Questions
Why a second terminal window?
The agent owns its own terminal, so a hook's output there is hidden or mixed into the session. A second window running watch is always readable.
What is in the full pack?
Hooks for Claude Code, Codex and Hermes, a Grok Bot rules block, a bridge with seven adapters including USB lights, an ESP32 and an e-ink panel, a stale state, owner approvals for flashing, network and tokens, fifteen read-only checks with a fixture, ten prompts and a failure table. $14.
Details
Version 1.0 · Updated Oct 28, 2026 · Markdown version of this page
License: Personal and commercial use. Download terms
Related
Agent Status Hardware: one light and one e-ink display for every agent session, driven by hooks
Wire the hooks Claude Code, Codex and Hermes already have, plus a rules block for Grok Bot, to one small bridge on your machine. It turns agent events into one state for all sessions and drives a terminal, a USB busylight, a blink(1), an ESP32 LED, a 2.13 inch e-ink panel or a Home Assistant light. Waiting for you is a red blink nothing can cover, a session with no news turns amber, and the light never approves anything.
Reversible or irreversible: the action sorting sheet (free sample)
A five-class sheet that sorts every action an agent can take on a computer, from read to irreversible, with two rules and one prompt.
The relay packet and the routine-or-judgment table (free sample)
The packet every handoff between agents should carry, a table for which work can move to a cheaper or fallback agent and which stays with you, two rules to paste and a check prompt.
The builder and tester contract and a red-then-green check (free sample)
From Two-Agent Build and Test Loop for paid apps: the six rules that keep a coding agent from grading its own work (two sessions, the tester never edits code, the builder never touches tests or says passed, red first, a script runs the tests, sandbox only with owner yeses on paid apps), a story card, and a read-only Python check on your run's ledger, with a worked example and its expected output.