Ghost Hand
Public Unreviewedby John Lauer
A small battery gadget that keeps an automatic sink faucet running while you use the sink: it learns the faucet's timeout, re-arms with the shortest blip, and stops after 10 minutes or when picked up.
AI Flow run: claude-opus-5-5 on the board
Running: step test-plan, 15.8 min of AI time since the prompt (15.8 min on the wall clock). This page updates at every step change.
Prompt at 2026-11-08T16:20:00Z (UTC). Flow: board. Every number here is from the run's append-only ledger (run.jsonl). AI time is the time the AI was working on a prompt: from the human's prompt to the AI's done, with any gap over 15 min where no command ran (unobserved, not proven idle) cut out.
Sessions
One row per human prompt: the AI's time on it, unobserved gaps excluded by the heuristic, which may include external AI work.
| Session | Prompt at | Done at | AI time min | Unobserved gap min | What |
|---|---|---|---|---|---|
| 1 | 2026-11-08T16:20:00Z | (open) | 15.8 | 0 | the first prompt |
| all | 15.8 |
Per step
AI time only, the idle cut out.
| Step | AI min | AI thinking min | Tool min | Turns | Visits | Returns | Longest think |
|---|---|---|---|---|---|---|---|
| intake | 13.2 | 13.2 | 0.0 | 1 | 1 | 0 | 13.1 min |
| design | 1.1 | 0.1 | 1.1 | 5 | 1 | 0 | 0.1 min |
| rules | 0.9 | 0.8 | 0.1 | 2 | 1 | 0 | 0.8 min |
| test-plan | 0.5 | 0.0 | 0.5 | 1 | 1 | 0 | 0.0 min |
| total | 15.8 | 14.2 | 1.6 |
Decisions along the way
- 2026-11-08T16:33:15Z clip-start:rules-1
- 2026-11-08T16:35:08Z clip-start:design-1
- 2026-11-08T16:35:46Z clip-start:test-plan-1
Where the board stands
The steps on camera
One clip per step visit, sped up 10x, with the editor at the start and the end of the visit. A caption above every clip and screenshot says what it shows.
rules
What this step does:
Clip: rules, the PCB editor from 2026-11-08T16:33:15Z to 2026-11-08T16:34:12Z. Motion only: 0.9 min of real time, 41 s of it had something moving; the clock in the corner is the real elapsed time.
Contact sheet: nine frames spread through the rules clip, what the camera saw.

Screenshot: the board when rules began.

Screenshot: the board when rules ended.

design
What this step does:
Clip: design, the PCB editor from 2026-11-08T16:35:08Z to 2026-11-08T16:35:19Z. Motion only: 0.2 min of real time, 8 s of it had something moving; the clock in the corner is the real elapsed time.
Contact sheet: nine frames spread through the design clip, what the camera saw.

Screenshot: the board when design began.

Screenshot: the board when design ended.

test-plan
What this step does:
Clip: test-plan, still recording (started 2026-11-08T16:35:46Z); it appears here when the step ends.
Screenshot: the board when test-plan began.

Plan usage, the second cost line
Percent of each plan limit used, as the provider reports it, at the start of the run and at its end.
| Provider | Limit | At start | At end | Used by this run |
|---|---|---|---|---|
| antigravity | 3p week | 0.00 % | 0.00 % | 0.00 % |
| antigravity | week | 0.00 % | 0.00 % | 0.00 % |
| claude | Fable | 0.00 % | 0.00 % | 0.00 % |
| claude | week | 8.00 % | 8.00 % | 0.00 % |
| codex | week | 1.00 % | 1.00 % | 0.00 % |
The limits are per account, not per run: every AI thread signed in as this user draws on the same numbers, so a run made while other threads were working shows their usage too. Read it as an upper bound unless this run was the only thread active.
Google Antigravity: tokens, quota and cost
0 model calls: 0 fresh input, 0 cached input and 0 output tokens. The run used 0.00 % of the weekly limit, about $0.00 of a $199.99/month plan.
| Step | Calls | Fresh input | Cached input | Output |
|---|
Token counts are the difference of Antigravity's own per-call records (its conversation files) between step snapshots; exact when nothing else used Antigravity during the run.
Given back
0 issue(s) or PR(s) filed by this run's AI to make the tool better for every Adom user.
Adom processes PRs within minutes during business hours: a non-stop PR intake runs all day.
# AI Flow run: claude-opus-5-5 on the board
**Running**: step `test-plan`, 15.8 min of AI time since the prompt (15.8 min on the wall clock). This page updates at every step change.
Prompt at 2026-11-08T16:20:00Z (UTC). Flow: board. Every number here is from the run's append-only ledger (run.jsonl). AI time is the time the AI was working on a prompt: from the human's prompt to the AI's done, with any gap over 15 min where no command ran (unobserved, not proven idle) cut out.
## Sessions
One row per human prompt: the AI's time on it, unobserved gaps excluded by the heuristic, which may include external AI work.
| Session | Prompt at | Done at | AI time min | Unobserved gap min | What |
|---|---|---|---|---|---|
| 1 | 2026-11-08T16:20:00Z | (open) | 15.8 | 0 | the first prompt |
| **all** | | | **15.8** | | |
## Per step
AI time only, the idle cut out.
| Step | AI min | AI thinking min | Tool min | Turns | Visits | Returns | Longest think |
|---|---|---|---|---|---|---|---|
| intake | 13.2 | 13.2 | 0.0 | 1 | 1 | 0 | 13.1 min |
| design | 1.1 | 0.1 | 1.1 | 5 | 1 | 0 | 0.1 min |
| rules | 0.9 | 0.8 | 0.1 | 2 | 1 | 0 | 0.8 min |
| test-plan | 0.5 | 0.0 | 0.5 | 1 | 1 | 0 | 0.0 min |
| **total** | **15.8** | **14.2** | **1.6** | | | | |
## Decisions along the way
- 2026-11-08T16:33:15Z clip-start:rules-1
- 2026-11-08T16:35:08Z clip-start:design-1
- 2026-11-08T16:35:46Z clip-start:test-plan-1
## Where the board stands
## The steps on camera
One clip per step visit, sped up 10x, with the editor at the start and the end of the visit. A caption above every clip and screenshot says what it shows.
### rules
What this step does:
**Clip: rules, the PCB editor from 2026-11-08T16:33:15Z to 2026-11-08T16:34:12Z. Motion only: 0.9 min of real time, 41 s of it had something moving; the clock in the corner is the real elapsed time.**
<video width="100%" controls><source src="/blob/app/ghost-hand/docs/runs/board-claude-opus-5-5-20261108-1620/rules-1.mp4" type="video/mp4"></video>
**Contact sheet: nine frames spread through the rules clip, what the camera saw.**

**Screenshot: the board when rules began.**

**Screenshot: the board when rules ended.**

### design
What this step does:
**Clip: design, the PCB editor from 2026-11-08T16:35:08Z to 2026-11-08T16:35:19Z. Motion only: 0.2 min of real time, 8 s of it had something moving; the clock in the corner is the real elapsed time.**
<video width="100%" controls><source src="/blob/app/ghost-hand/docs/runs/board-claude-opus-5-5-20261108-1620/design-1.mp4" type="video/mp4"></video>
**Contact sheet: nine frames spread through the design clip, what the camera saw.**

**Screenshot: the board when design began.**

**Screenshot: the board when design ended.**

### test-plan
What this step does:
**Clip: test-plan, still recording (started 2026-11-08T16:35:46Z); it appears here when the step ends.**
**Screenshot: the board when test-plan began.**

## Plan usage, the second cost line
Percent of each plan limit used, as the provider reports it, at the start of the run and at its end.
| Provider | Limit | At start | At end | Used by this run |
|---|---|---|---|---|
| antigravity | 3p week | 0.00 % | 0.00 % | 0.00 % |
| antigravity | week | 0.00 % | 0.00 % | 0.00 % |
| claude | Fable | 0.00 % | 0.00 % | 0.00 % |
| claude | week | 8.00 % | 8.00 % | 0.00 % |
| codex | week | 1.00 % | 1.00 % | 0.00 % |
*The limits are per account, not per run: every AI thread signed in as this user draws on the same numbers, so a run made while other threads were working shows their usage too. Read it as an upper bound unless this run was the only thread active.*
## Google Antigravity: tokens, quota and cost
0 model calls: 0 fresh input, 0 cached input and 0 output tokens. The run used **0.00 % of the weekly limit**, about **$0.00** of a $199.99/month plan.
| Step | Calls | Fresh input | Cached input | Output |
|---|---|---|---|---|
*Token counts are the difference of Antigravity's own per-call records (its conversation files) between step snapshots; exact when nothing else used Antigravity during the run.*
## Given back
0 issue(s) or PR(s) filed by this run's AI to make the tool better for every Adom user.
Adom processes PRs within minutes during business hours: a non-stop PR intake runs all day.