Single operators can run many agent workflows, but the work becomes hard to revisit when status, prompts, tools, files, and validation are scattered. FactionOS gives that work a local operating picture.
Power users
Keep local agent work visible while you stay in control.
Use mission state, prompt lifecycle markers, approvals, replay context, and diagnostics while staying in control.
Power users need fast local feedback and enough structure to revisit decisions, troubleshoot gaps, and keep risky steps visible.
- Focuscontrol
The problem
Where the work loses its shape.
Before and after
What changes with an operating picture.
Prompt lifecycle
Before
Prompt starts, tool calls, file touches, and completions blur together.
With FactionOS
Lifecycle markers can become reviewable local mission state.
Lifecycle markers do not mean prompt bodies upload by default.
Approvals
Before
Risky moments depend on memory or raw terminal context.
With FactionOS
Approval and review surfaces can keep the next decision visible.
Approvals and local tool trust prompts remain under operator control.
Diagnostics
Before
Missing hook events or broken local setup produce confusing gaps.
With FactionOS
Diagnostics can show failure posture and setup health explicitly.
Diagnostics must avoid exposing raw secrets, env values, or local paths.
Replay and demo
Before
It is hard to revisit what happened or inspect the product before setup.
With FactionOS
Replay is local product context, and the public demo remains a guided preview.
The zero-install demo is a guided preview and stays separate from local sessions.
Surface mapping
Which surface does the job.
Availability and guardrail columns keep local, optional, and outbound clearly separated.
| Capability | Surface | Availability | Guardrail |
|---|---|---|---|
| CLI | apps/cliLocal commands keep setup, validation, and operator posture close to the terminal. | local | Command examples are references; operators run local commands themselves. |
| Cockpit | apps/web cockpitMission state, replay context, approvals, and diagnostics become inspectable locally. | local | Cockpit state is local runtime behavior when the install is running. |
| Demo | guided public demoA zero-install preview lets power users inspect the feel before local setup. | preview | The zero-install demo is a guided preview and stays separate from local sessions. |
Operator proof
How this path shows up in the cockpit.
Lifecycle
Prompt and tool state
Prompt lifecycle and tool activity can be reviewed as structured local events.
Evidence Useful when a power user wants to understand why work moved forward.
Do not expose prompt bodies, secrets, or source files by default.
Control
Approval posture
Approval and replay surfaces keep high-friction moments visible.
Evidence Useful when a local operator wants context before continuing risky work.
Product pages are descriptive and cannot change local tool permissions.
Boundaries
What stays true for this role.
- localLocal
Prompt lifecycle, replay, exports, and diagnostics start as local product behavior.
- docsWebsite
This route describes setup and product surfaces; the installed product handles local runtime state.
Power user path
Try the guided preview, then read the setup docs.
Zero-install product preview hosted separately from this website. Use features to compare control surfaces and docs for the local setup path.
The demo and docs are separate external destinations. They do not create an account or upload your local agent state by default.