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.

What you can do now

Clawdfather keeps its durable identity, reads work across the machine, resumes existing Sessions exactly, dispatches non-conflicting tasks, arranges independent review, and keeps the root responsible for integration, verification, and release.

scope: machine standby

seven situations, three beats each

Problem. Judgement. Durable outcome.

01Problem

The app disappears. The work does not become anonymous.

What you can do now

You can ask Clawdfather to find each conversation by its durable identity and resume it through the exact Session route.

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 stepwaitingnames the outside moverreadycan accept work; obligations may remainclosed · outcomelifecycle outcome · not a live Session recordunknownstale or absent evidence

Unknown is not offline. Ready is a Session declaration that says it can accept new work; it does not prove that every obligation is complete or replace a broker-verified landing. Closed is a lifecycle outcome, not a current live Session record.

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.

how Clawdfather works

Clawdfather first builds a trustworthy machine-wide picture, then uses current capabilities to move the work forward.

First, confirm where every status came from

The machine-wide picture does not lose context when one process restarts.

Clawdfather has a broker-authenticated machine identity. Bearings reads current Session data, tasks, waits, and pending landings while preserving the source and freshness of each fact. When work must resume, it opens the known Claude or Codex conversation instead of creating a similar-looking Session without the original context.

Then, turn the request into executable work

You can ask Clawdfather to coordinate the complete workflow in natural language.

Ask it to resume every Session, split work across projects, arrange an independent review, correct findings, route around a quota failure, or integrate and verify the final result. It advances the workflow through exact resume, dispatch, receipts, review, and landing records while keeping the root responsible for the final delivery.

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.