Agent operations · Local first
Clawdline makes multi-session work visible: which agent owns what, who dispatched whom, what is waiting, what was reviewed, and whether the exact tree reached the target branch.
One coding agent quickly becomes five. Some were opened by hand, some were dispatched by another session, two may touch the same project, and a finished answer may still need an independent review. Tab titles cannot express that operating state.
Clawdline coordinates the Claude Code and Codex sessions already running on a Mac. It adds a durable map of sessions, task ownership, write claims, reviews, waits, landings, and release evidence without wrapping or replacing either assistant.
Clawdline preserves session identity, lineage, attention, and delivery evidence across Claude Code and Codex—on the Mac and from a paired phone.
Fleet
Sessions appear as an operating hierarchy instead of a flat row of terminals. Project, provider, parent-child lineage, task state, and attention are visible before anyone opens a transcript.
Transcript
The transcript pane keeps instructions, tool activity, decisions, and delivery evidence legible. Operators can understand what happened without reconstructing the story from an ephemeral terminal buffer.
Reach
A paired phone can show the same fleet, urgency, and session identity away from the desk. Remote access extends visibility first; write control remains a separate, deliberate capability.
Built around the real operating conditions of the people it serves.
Every live Claude Code and Codex session appears in one hierarchy with status, project, transcript, and ownership.
Declared write claims prevent collisions before work begins; typed waits and receipts keep asynchronous work legible.
Independent review, bounded correction, root-owned landing, and exact-tree verification keep “finished” from becoming an assumption.
Delivered is not reviewed. Reviewed is not landed.
Clawdline treats coordination as durable evidence rather than transient chat state. Cloud is optional reach: execution and the content key stay on hardware you own, while signed, end-to-end encrypted payloads move between paired devices.
