| 1 | # Casebook |
| 2 | |
| 3 | What happened behind the rules, for anyone curious. Nothing here is needed to |
| 4 | follow the skill. Projects: **the Knife**, Clover's fork of T3 Code with its |
| 5 | own updater and background holder processes (October 2026); **Snowbound**, a |
| 6 | OneNote remake one thread maintained for ten days. Quotes are Clover's. |
| 7 | |
| 8 | ## The role |
| 9 | |
| 10 | - **Seams.** On the Knife, the orchestrator saw that the Tools patches touched |
| 11 | the adapters hot-update relies on, which became a test scenario; found that |
| 12 | the update dialog said "interrupted" because orchestrator turns are never |
| 13 | handed off; and caught a banner showing two contradictory delivery lines. |
| 14 | - **Say when your call was wrong.** The orchestrator recommended dropping a |
| 15 | compatibility shim without checking live data, and her Devices page went |
| 16 | empty. |
| 17 | |
| 18 | ## Modes |
| 19 | |
| 20 | - Clover, on scope: "i dont want orchestrate to activate in [a work repo] and |
| 21 | then the agent starts messing with issue tracker and worktrees and stuff." |
| 22 | The core stays shared because "the core theory of locking parts of the code |
| 23 | and routing to different models is the meat of the skill." |
| 24 | |
| 25 | ## Ownership |
| 26 | |
| 27 | - **Keep the code claimed.** Clover: "the top level needs to ensure that as much |
| 28 | of the codebase is locked as possible, re-checking the queue for tasks that |
| 29 | slot into the gaps." |
| 30 | - **One rewriter.** Knife agents rewriting one jj store from several workspaces |
| 31 | made divergent changes. A shared `mkdir` lock fixed it; Clover preferred the |
| 32 | orchestrator knowing who works on what. |
| 33 | - **Own workspace per editor.** Snowbound's one shared working copy broke builds |
| 34 | for hours and swept half-edits into commits. |
| 35 | - **Confirm reachability before forgetting.** Snowbound nearly lost a finished |
| 36 | change by forgetting its workspace. |
| 37 | |
| 38 | ## Routing |
| 39 | |
| 40 | - **Reading is the cost.** On 2026-10-21, on Clover Home Claude, Opus subagents |
| 41 | used 84% of the day's usage and the orchestrator 14%; Sonnet came to 1%, and |
| 42 | 230 Haiku test sessions to under 1%. Nearly all of it was cache reads by long |
| 43 | agents rereading large contexts. |
| 44 | - **Limits mid-task.** Clover Home Claude hit 12% with hours to go. Clover Work |
| 45 | Codex hit its limit mid-rebase; the agent failed with nothing changed. |
| 46 | - **Live instance ids.** Re-sharing an account renamed `codex-personal` to |
| 47 | `codex-yf324204uu`, and the old entry stayed listed as "not authenticated". |
| 48 | |
| 49 | ## Briefs |
| 50 | |
| 51 | - **The exact tree.** A Knife release gate ran its updater end-to-end matrix on |
| 52 | one commit while the release tip had added the Tools patches, so the gate |
| 53 | proved nothing about what shipped. |
| 54 | - **Foreground only.** Two Knife agents stalled waiting for a background |
| 55 | notification that never came. |
| 56 | - **Steering.** "No Host rewriting, real host header" landed mid-build as a |
| 57 | steer. |
| 58 | - **Safety in AGENTS.md.** v1 pasted a 13-line safety block into every brief. |
| 59 | Clover: "you shouldn't be wasting your tokens re-emitting this block." |
| 60 | |
| 61 | ## Deciding and asking |
| 62 | |
| 63 | - **Obvious calls.** Clover: "i am glad i dont have to go 'yeah obviously we |
| 64 | should use the better approach' … i will ALWAYS appreciate a stronger and more |
| 65 | resilient implementation. expanding scope is the scarier one." |
| 66 | - **Trust model.** Knife: "computer to computer, trust the main port, permission |
| 67 | for other ports in the browser." It answered two agent questions without |
| 68 | asking her. |
| 69 | - **Declining scope behind a gate.** A stderr channel for one fix would have |
| 70 | changed the holder protocol and reopened the full matrix plus a review; |
| 71 | structured errors detected the same failure. |
| 72 | - **Do the simpler thing.** It decided the Claude usage endpoint: match |
| 73 | upstream. |
| 74 | - **Security escalation.** A Knife review blocked on four P1s, including proxy |
| 75 | egress reaching the LAN and a lease renewing without fresh approval. |
| 76 | |
| 77 | ## Gates and releases |
| 78 | |
| 79 | - **Stop rule up front.** The Knife updater took 12 fix rounds because the |
| 80 | reviewer kept finding the next ring: protocol-1 notices, then advice copy, |
| 81 | then damaged-record copy. |
| 82 | - **Prove shipped state.** Dropping a scope shim broke decoding of her shipped |
| 83 | auth rows and emptied Devices; a consolidation renumbered migrations her |
| 84 | database had already recorded. |
| 85 | - **Exit status.** A filtered "clean" once hid a check that never ran. |
| 86 | - **Reproduce on the base.** Thirteen server failures in unchanged tests |
| 87 | reproduced on the original source: the environment. |
| 88 | - **Waivers.** She chose "Publish it now" over a third review round, and was |
| 89 | told not to use keyed Tools servers with Codex until the next update. |
| 90 | - **Ship often.** Knife wave 1 (fixes) went out while wave 2 (UI) was still |
| 91 | folding. |
| 92 | |
| 93 | ## Safety |
| 94 | |
| 95 | - An agent ran read-only `git config` in a jj repo. |
| 96 | - Two updater harness runs shared one home, port and bundle id, and killed each |
| 97 | other. |
| 98 | - A bare `jj squash --into` opened an editor and hung the agent. |
| 99 | - An inherited `TMPDIR` and `CLAUDE_CONFIG_DIR` leaked a scratch server into the |
| 100 | agent's real profile, and 315 MB of build temp into her real home. |
| 101 | - Scratch servers without their own home wrote test identities into her real |
| 102 | `~/.knife`. |
| 103 | - An agent copied a scratch Claude credential into a fixture, then disclosed and |
| 104 | removed it. |
| 105 | - Closed literal unions (the icon colors) break old decoders when extended. |
| 106 | - **Machine load.** On Snowbound, stale waiter loops piled up (18 belonged to |
| 107 | finished agents; later "50 running bg tasks"). Unthrottled builds plus VMs |
| 108 | froze her Mac: "i literally couldnt even move the mouse." Deleting the macOS |
| 109 | 10.6 SDK cost a platform two days of releases. |
| 110 | |
| 111 | ## jj stack |
| 112 | |
| 113 | - **A deep fold.** Squashing a commit into a patch far below it cascaded |
| 114 | conflicts through 26 commits, because it depended on later patches. |
| 115 | - **Frozen snapshot.** Adding a workspace at an obsolete commit unhid its |
| 116 | ancestors and made the stack divergent. |
| 117 | |
| 118 | ## Trouble |
| 119 | |
| 120 | - **"Still" broken.** Her laptop sat on an old build; "it was just the updater". |
| 121 | - **A release broke her machine.** Applying a Knife update hung her app and |
| 122 | cancelled every delegated task. The hotfix reverted the offending patch on the |
| 123 | tested tree and released that. |
| 124 | - **A long suite.** The Knife's server tests run serially and outlast a |
| 125 | 10-minute tool call, so they run as file-list chunks. |
| 126 | |
| 127 | ## Talking to Clover |
| 128 | |
| 129 | - **Screenshots.** Spot-checking them caught the banner copy and a test thread |
| 130 | showing an auth failure. Clover: "screenshots and videos are always awesome to |
| 131 | see i just love seeing them." |
| 132 | - **Confidence.** "it should not be confident if it doesn't know." |