Local-first agent command
Watch parallel agent work, keep session intent visible, and steer implementation from a cockpit built around local operator workflows.
Operator boundarySynthetic static samples only: no analytics, no visitor tracking, and no hosted runtime calls. Outbound adapters wait for operator approval.
Signal relay
The operator problem
Terminal noise, session drift, and hidden risk collapse into lanes, checkpoints, and review states the operator can act on.
$ tail -f session.log
... 4200 lines of scrollback ...
who touched auth.ts?Session rows attach file-touch and tool status to a readable lane.
agent-1 ok agent-2 ?
agent-3 (stalled)
context lost on tab closeA mission roster keeps who is active, queued, or blocked in one picture.
diff: 41 files changed
no review checkpoint
no approval trailReview gates and approval events make risk visible before it ships.
Mission board
Inspect the active mission as a tactical board: roster on the rail, objective on the map, events on the clock, and approvals held at the gate.
Keep parallel coding agents visible, reviewable, and locally controlled.
Operator Human approval required for outbound adapters and destructive file operations.
Agent roster
Event stream
Session objective captured.
Component and style files inspected.
Mission board state layer patched.
Review checkpoint opened for changed surface states.
Outbound docs adapter held pending approval.
Replay scrub
Current tickMission board state layer patched.
Approval checkpoint
review-gate-2
Human approval required for outbound adapters and destructive file operations.
Guided preview data. Events represent the shape of local hook output and mission state.
Hook-to-cockpit flow
The flow starts on the operator machine, resolves into local mission state, and only leaves through an operator-approved adapter.
A CLI or editor-side hook records a compact lifecycle marker such as prompt started, tool requested, file touched, task updated, or validation completed.
In Agent workflow signalOut Structured local event
The event begins on the operator machine.
The local FactionOS server accepts the event, normalizes the contract, and prepares a small snapshot for the cockpit.
In Structured local eventOut REST snapshot
Ingest describes local product behavior.
A local browser cockpit can refresh mission lanes, status rings, and review checkpoints through a WebSocket stream when the runtime is installed and running locally.
In State changeOut Visible cockpit update
The cockpit stream belongs to the installed product runtime.
If an operator configures an adapter, a narrow notification can leave the machine under that adapter contract for destinations such as team chat or downstream automation.
In Operator-approved signalOut External notice if enabled
Adapters are optional and operator-approved.
Capability deck
Pick the job: observe the signal, coordinate the lanes, review the gate, contain the boundary, or export a narrow notice.
Observe
Hook lifecycle events become readable session rows instead of terminal scrollback.
Coordinate
Lanes, objectives, and progress states make handoffs recoverable after several agents move at once.
Review
Review checkpoints and approval gates hold sensitive actions until an operator decides.
Contain
Prompts, paths, and credentials stay local unless an operator configures an explicit adapter.
Export
Optional outbound adapters carry a scoped notice under an adapter contract.
Rules of engagement
Every state names what the operator can do, what waits for approval, and where sensitive context stays.
State is read from local hooks and local files.
Human review is required before this lane can advance.
An optional outbound action is blocked until approved.
Guided preview state for product orientation.
Sensitive data classes
No hosted account is required for the core local workflow.
Prompt bodies are not part of the default public-site workflow.
Repository paths, file names, and file contents stay in the local product context unless an operator chooses otherwise.
Secrets and tokens are not requested by this site.
Tracking and runtime personalization are not part of the launch site.
Launch posture: no hosted form, analytics script, runtime fetch, sockets, beacons, storage writes, cookie writes, or route prefetcher.
Review Security ->Role routes
Each route frames the cockpit around a different job: team coordination, platform control, founder visibility, or power-user command.
Provider and adapter surface
Compatible producers can follow the event contract. Optional exits carry scoped notices only after an operator configures them.
Sources
Local core
Event contract + local server + cockpit
Default localOptional exits
Optional exits require operator configuration. They carry outbound notices only - no inbound command control.
Field notes
Product thinking, updates, and roadmap direction for operators building around AI coding agents.
Command ready
Zero-install product preview hosted separately from this website. Use the public GitBook docs for setup, event contracts, and operator context.
Synthetic demo destination
External docs destination