Feature inventory

Agent work you can review while it happens.

Cockpit visibility, review control, lineage, and outbound notifications stay separated by boundary.

The features page turns the product overview into concrete capability groups: what the local cockpit shows, where approvals and replay fit, how subagent work is traced, and which optional outputs leave the machine only when configured.

Defaultlocal
Adaptersoutbound
Controloperator-led

Open Demo How It Works

Core workflows start locally. External demos, docs, and adapters are separate, intentional actions.

Cockpit surfaces translate local hook and server state into mission, roster, battlefield, and detail views that an operator can scan during real work.

Navigation and rosterMove between mission lanes, active agents, alerts, settings, and diagnostics with local runtime context.
Mission feed and mapUse feed rows and battlefield state to understand active work through the command surface.
Mission detailKeep objectives, state, file/tool context, and next review action together for one mission.

Public pages describe these surfaces. The installed product handles local workspace state and runtime streams.

Product Open Demo How It Works

Prompt lifecycle, approvals, replay, file timelines, and tool timelines keep review state explicit while limiting what needs to be exposed.

Prompt lifecycleRepresent prompt started, tool requested, file touched, validation completed, and failure markers as structured events.
Approvals and replayKeep high-friction moments visible while local tool approvals stay under operator control.
File and tool timelinesShow review context as grouped activity while avoiding secret values, broad paths, or raw source by default.

Review features depend on local product runtime behavior. Operators still control local command authorization.

How It Works Security Read Docs

FactionOS is built for multi-agent coordination where planner, builder, reviewer, and subagent work should remain tied to one operating picture.

Orchestration deckCompare lane ownership, progress, and review posture across simultaneous local agent work.
Subagent lineagePreserve parent-child context and handoffs so delegated work remains explainable.
DiagnosticsSurface hook, server, and validation health so missing events do not become invisible failures.

Orchestration visibility is separate from remote execution. Remote control needs its own threat model.

Product How It Works Read Docs

Outbound adapters, export paths, and audit trails make handoff deliberate, narrow, and reviewable.

Outbound adaptersDiscord, Telegram, and generic HTTPS adapters are optional outbound paths.
ExportPrepare local or operator-directed handoff material without making hosted storage the default.
Audit trailPreserve event history for review while keeping certification and compliance work separate.

Adapters do not become inbound command channels, website analytics, background upload, or remote execution.

Security Read Docs Open Demo

Capability	Workflow	Surface	Availability	Guardrail
Cockpit navigationTop-level lanes let operators move between missions, agents, review states, settings, and diagnostics.	cockpit	apps/web cockpit	local	Navigation is runtime UI, not a hosted account surface.
Live rosterActive agent and lane posture is visible as structured status instead of background guesswork.	cockpit	apps/web cockpit	local	Roster state is local runtime state when the local install is running.
Mission feedMission rows group lifecycle, review, and validation activity so operators can scan active work.	missions	apps/web cockpit	local	Feeds summarize structured events for the local cockpit.
Battlefield mapThe visual map gives product context for agents, work zones, alerts, and tactical state.	missions	apps/web and demo	preview	The zero-install demo is a guided preview and stays separate from local sessions.
Mission detailA focused mission view keeps objectives, current state, files, and follow-up signals together.	missions	apps/web cockpit	local	Details should stay narrow and avoid exposing secrets or full raw transcripts by default.
ReplayReplay helps revisit a local sequence of events and decisions without implying public replay hosting.	review	apps/web cockpit	local	Replay data is local product state unless an explicit later integration says otherwise.
ApprovalsReview gates keep risky actions and checkpoints visible to the operator before work proceeds.	review	apps/web cockpit	local	Approvals and local tool trust prompts remain under operator control.
File and tool timelinesFile touches and tool activity are grouped as reviewable event context instead of free-form log sprawl.	review	protocol and cockpit	local	Timeline copy must avoid displaying credentials, raw source, or broad local paths.
Prompt lifecyclePrompt start, tool use, completion, and validation markers become lifecycle state for review.	review	hooks and protocol	local	Lifecycle markers do not mean prompt bodies are uploaded by default.
DiagnosticsHealth, validation, and hook status signals help spot broken local setup or missing events.	trust	CLI, server, cockpit	local	Diagnostics should produce explicit failure states rather than silent gaps.
SettingsLocal preferences and reset affordances keep operator control visible.	trust	apps/web cockpit	local	Settings are separate from hosted identity and erasure policy.
Orchestration deckPlanner, builder, and review lanes can be compared so parallel work stays understandable.	orchestration	apps/web cockpit	local	Orchestration visibility does not imply remote execution from the website.
Subagent lineageSubagent handoffs and parent-child work context stay attached to the mission story.	orchestration	protocol and cockpit	local	Lineage is event context, not a promise that every external agent provider is supported.
Outbound adaptersDiscord, Telegram, and generic HTTPS adapters are optional outbound paths. Each adapter sends narrow notifications only when enabled.	adapters	apps/adapters	outbound	Adapters are outbound notifications only, not inbound commands or remote execution.
ExportExport paths support review and handoff without turning the website into hosted storage.	export	local product surface	local	Exports remain local or explicitly operator-directed.
Audit trailBounded event history helps explain what happened, what changed, and where review occurred.	trust	protocol and cockpit	local	Audit wording stays separate from certification and compliance programs.

local

Local-first by default for the core workflow.

Security

explicit

Adapters and War Room collaboration are optional handoffs, not automatic uploads, analytics, or inbound command channels.

Read Docs

public

Public pages describe the product; installed runtime surfaces handle workspaces, sockets, and local commands.

Product

separate

Hosted identity, hosted storage, public replay hosting, and erasure policy need separate product work.

Security

Compare the product map, then inspect the demo.

Use the product overview for surface boundaries, the how-it-works page for the hook pipeline, and the external demo for a guided preview. Zero-install product preview hosted separately from this website.

Open Demo How It Works

Demo and docs open as separate destinations.

Agent work you can review while it happens.

What the cockpit shows, grouped by job.

See the active mission without reading every log line.

Turn lifecycle noise into checkpoints an operator can inspect.

Track parallel agent work by lane, mission, and lineage.

Send only the outputs an operator has chosen to send.

Every capability, with its boundary attached.

The posture that stays constant.

Local machine first.

External signals are deliberate.

Pages describe product behavior.

Hosted identity and storage are separate.

Compare the product map, then inspect the demo.