Watch the queue before opening another thread.

The Life OS Watchtower reads local Codex, Claude Code, Kimi, and Grok session metadata, compares it with the previous baseline, and turns the queue into deltas, alerts, next actions, and a safe cockpit import.

Simple layer. The Watchtower is a local traffic light for your agent sessions. It does not solve the queue for you. It tells you what changed and which three decisions to make next.

The generator runs the local agent-session refresh, reads the sanitized refresh JSON, compares counts and newest sessions against the previous watchtower file, then writes Markdown, JSON, and an import file. It strips private source fields and does not call any external service.

Run the watchtower

node work/life-os-watchtower.mjs
# or
node work/life-os.mjs watch

# then open:
outputs/life-os-command-center/life-os-watchtower.md

Read five signals

TotalHow large the session queue is right now.

DeltaWhat changed since the previous watchtower file.

AlertsMissing sources, validation needs, or oversized queue.

QueueThe short list to decide before more context switching.

ActionOne timeboxed move with a proof gate.

Manual-only guardrails

The Watchtower is not a daemon, not an auto-archiver, and not an app controller. It prepares decisions. You manually choose continue, validate, extract task, or archive.

Import into the cockpit

outputs/life-os-command-center/life-os-watchtower-import.json

Proof from this run: the Watchtower writes local session counts, per-agent deltas, alerts, at least 3 next actions, a short queue, and a cockpit import with no private source fields.