Skip to content
C.W.K.
Stream
Lesson 05 of 05 · published

The Proposal Runs in the Kit Worker

~13 min · pippa, proposal, worker, siblingkit, brain-control, ssh

Level 0Spark
0 XP0/48 lessons0/12 achievements
0/100 XP to next level100 XP to go0% complete

Same Rule, New Address

The last lesson's rule has not moved an inch: a proposal inserts only against a frozen snapshot and never with a newline (a multi-line one can be read and copied, not inserted), and nothing picks silently. What moved on 2026-09-23 is where the thinking happens. Until then, ⌘K proposals, Option+Tab completions and Ask were requests to Pippa's own server, and the proposal and completion routes refused any caller that was not on the office Mac's loopback — so on every other Mac those two features simply did not work. Now all three run Pippa's command-proposal service, unchanged, inside a utility worker that ships in the app bundle. The worker comes from Sibling Kit; Smolder consumes it like every other family app that needs a tool-less model call.

Office Runs It; Every Other Mac Reaches Office

On the office Mac the app runs the worker from its own installed bundle. On every other Mac the app reaches the office Mac's installed copy of the same bundle over SSH, pinned to a known host key that ships beside the worker, with strict host-key checking and no interactive prompt. A Mac without a fleet label never runs it locally; the missing label is not allowed to mean "this must be office". The build script refuses to produce a bundle without the worker and its pinned key, because a bundle that cannot propose on a peer is a bundle that will fail in front of Dad on the MacBook.

Why office? The worker does not hold a model credential either. Per call it asks the family owner on the office Mac for provider state, and it runs whichever brain the slot names. Smolder holds no provider key, the session daemon still calls no model, and the app is the only caller. When the owner or the office Mac is unreachable, there is simply no proposal — the terminal stays whole, and nothing falls back to a different endpoint.

Who Chooses the Brain

Each request carries the brain, model and effort resolved from two named slots in the family's brain control: one for commands and questions, one for completions. The slots are read before each call, so a change made in the family settings applies to the next ⌘K. Ask is a respond-mode call with tools and shell execution switched off. And because the work runs on office and is reached over SSH from elsewhere, both slots declare themselves remote-executed: a brain that signs in through a desktop keychain cannot sign in across that hop, so the family authority refuses to assign one to these slots.

Loopback Is a Claim About Your Machine

The Pippa server Smolder talks to for slots and the Sidekick also stopped assuming loopback in October. A fleet-label helper from the kit now decides by machine: the office Mac uses its own loopback; every other Mac defaults to the office Mac's HTTPS address on the family tailnet, and Settings refuses a typed loopback address off office. The bug that forced it was quiet: on the MacBook abroad, "loopback Pippa" reached a different local service that happened to listen on the same port. Anvil's preparation plan follows the same rule. Smolder's own daemon, door and gateway stay local by design.

Where a proposal is computed can move; what it may do cannot. The worker runs on office, the brain comes from the family's slots, the terminal holds no credential — and a proposal still only inserts, against a frozen snapshot, without a newline; an Ask answer is only ever shown.

Code

A ⌘K proposal, from keystroke to insertion·text
Cmd-K in a pane (or Option+Tab, or Ask)
  1. app freezes the snapshot: pane, generation, pid, cwd, prompt state
  2. app resolves the slot from the family's brain control
       command + questions slot  |  completion slot
       -> brain, model, effort   (read before every call)
  3. app runs the Kit utility worker
       on office      -> the worker inside this app's own bundle
       anywhere else  -> office's installed bundle over pinned SSH
                         (known host key ships with the worker; strict checking)
       no fleet label -> never "local"
  4. worker asks office's family owner for provider state, calls the brain
       Ask: respond mode, tools off, shell off
  5. one proposal (Cmd-K), an answer (Ask), or up to five candidates (Option+Tab)
  6. proposal / candidate: insert only if the snapshot still matches; never a newline
       multi-line, risky or delegate-recommended proposal: Copy only
     Ask answer: shown, Copy only, never inserted

unreachable owner or office -> no proposal; the terminal is unaffected
session daemon -> still calls no model

External links

Exercise

Draw the path of one ⌘K proposal from a laptop that is not the office Mac: which process freezes the snapshot, which reads the brain choice, where the model call runs, which machine holds the provider credential, and where the answer is inserted. Mark the one step that may never send a newline, and the one failure that must leave the terminal untouched.
Hint
Four machines' worth of roles fit on two Macs. If your drawing has the terminal holding a key, or the daemon calling a model, a box is in the wrong place.

Progress

Progress is local-only — sign in to sync across devices.
Spotted a bug or have feedback on this page?Report an Issue

Comments 0

🔔 Reply notifications (sign in)
Sign in — Please sign in to comment.

No comments yet — be the first.