clawdfather / machine-wide context

The one session that keeps the whole machine in view.

Sessions can be fast and still pull in opposite directions. Clawdfather is the pinned, durable role that keeps the map: what is active, blocked, delivered, waiting to land, or waiting for you. It uses that map now to resume, decompose, dispatch, review, correct, integrate, verify and release — without pretending that coordination is unlimited authority or that a Session declaration proves a landing.

Current

Durable identity, Bearings, exact session resume, claims, parallel dispatch, independent review, correction, root-owned landing, exact-tree verification and build/restart.

Next surface

Native graph controls, a derived closeable gate, one-tap batch receipts and broker policies that run the same workflows without a live Clawdfather conversation.

scope: machine standby

seven situations, three beats each

Problem. Judgement. Durable outcome.

01Problem

The app disappears. The work does not become anonymous.

Currentvoice intent · durable identity · exact resume Next surfaceone-tap native batch + atomic batch receipt
Clawdfather judgement“Resume all sessions.”
Clawdfathergeneration 7
auth refactorcodex · exact id
release notesclaude · exact id
test repaircodex · exact id
01 / problem

The Mac app or coordinator process drops. Three conversations are still real work, but every live binding is dark.

02 / judgement

Clawdfather inventories the Mac-owned conversation ids, avoids sessions already live, rebinds its own durable role when needed, then calls the exact resume route for each stopped conversation.

03 / durable outcome

Current: “Resume all sessions” becomes a sequence of exact Claude and Codex resumes, and every session continues its own assignment. Rebind restores Clawdfather’s role; the existing resume route restores the conversations.

  1. 01plantruth · scope · landing owner
  2. 02claim + dispatchtyped conflicts before work
  3. 03parallel workindependent paths and receipts
  4. 04reviewreviewer did not author the delivery
  5. 05correctionone bounded finding graph
  6. 06landingroot integrates reviewed bytes
  7. 07exact commit treeone final acceptance run
  8. 08build and restarthealth · receipts · release
workingowns an active next step waitingnames the outside mover readycan accept work; obligations may remain closeableproposed derived gate closed · outcomelifecycle outcome · not a live Session record unknownstale or absent evidence

Unknown is not offline. A ready value is a Session declaration; it can coexist with owed work and cannot replace a broker-verified landed target. Closed is a lifecycle outcome, not a current live Session record. Closeable is the next derived product gate—not a shipped Status API—and should require no live child, open wait, dirty or staged delivery, or pending landing before a Session may be closed.

01 · Recover

The app disappears. The work does not become anonymous.

Current: “Resume all sessions” becomes a sequence of exact Claude and Codex resumes, and every session continues its own assignment. Rebind restores Clawdfather’s role; the existing resume route restores the conversations.

02 · Untangle

Two fast sessions are slower when they touch the same truth.

The conflict becomes a typed wait, not a race. Disjoint lanes flow now; the blocked lane resumes only after the owner releases it.

03 · Dispatch

One sentence becomes three independent lines of work.

The lines start independently and report independently. A slow relay audit cannot hide the app result or hold the launch-page result hostage.

04 · Protect

A green child result is not permission to land.

One check marks a delivered milestone. Two checks appear only after the broker verifies the target landing; the wider graph still belongs to its root.

05 · Catch up

Return to the machine-wide picture, not four stale tabs.

The summary keeps the states separate: completed, pending landing, waiting human, failed. Nothing is promoted to “done” by prose or by silence.

06 · Route around

One exhausted assistant is a branch failure, not a machine failure.

The blocked branch is explicit and recoverable. Codex takes the bounded build; observation and unrelated sessions continue without sharing its failure.

07 · Integrate

Plan once. Split safely. Review independently. Deliver the exact tree.

Only a SAFE TO LAND review opens integration. Clawdfather lands the reviewed bytes, verifies the exact commit tree once, performs the authorized build and restart, checks live health and receipts, and closes only Sessions with no remaining obligation.

the honest boundary

The workflows are current. The first-party control surface is next.

Current / identity and evidence

The machine-wide picture survives process churn.

Clawdfather has one broker-authenticated machine identity. Bearings reads current Session metadata, tasks, waits and pending landings with source freshness. Exact project resume opens known Claude or Codex conversations; guarded rebind preserves Clawdfather’s own role.

Current / coordinated workflow

Clawdfather acts through existing primitives.

A person can already say “Resume all sessions,” ask for a multi-project split, send independent review, correct a finding, reroute a quota failure, or ask Clawdfather to integrate and verify. The root performs those workflows through exact resume, dispatch, receipts, review, landing and an authorized build—not through the narrow rebind endpoint.

Next / native product surface

The app controls still catch up to the workflow.

The Clawdfather control sheet remains Preview/Disabled. A derived closeable state, one-tap batch resume, persisted since-away return points, native graph controls and broker-native reroute policies are next; the working conversational orchestration path does not depend on those buttons.

read the underlying system

The animation is a story. The records are the truth.

See how dispatch, claims, handoff and landing create the durable evidence Clawdfather reads.