FactionOS
Open Demo (external link) Read Docs (external link)
FactionOS square brand mark.

Local-first agent command

FactionOS

Mission control for AI coding agents.

Watch parallel agent work, keep session intent visible, and steer implementation from a cockpit built around local developer workflows.

Open Demo (external link) Read Docs (external link)
Runtime local-first Telemetry simulated Collection absent

Homepage readouts are synthetic static samples only: no analytics, no visitor tracking, no hosted runtime calls.

local cockpit preview sample only
  1. operator@local factionos watch --workspace ./repo 3 synthetic agent lanes staged for a local demo Local CLI
  2. session@s1401 inspect mission --focus homepage hero, CTAs, and privacy boundary locked before scroll Spec session
  3. events@static tail cockpit.timeline --sample no network request, browser storage, or analytics event created Static sample
Agent lanes
Codex, CLI, review
Source
local event contracts
Mode
deterministic sample

Static cockpit

Simulated local runtime

Static local posture sample. These values do not query a workstation, agent session, analytics service, or hosted runtime.

  • Local server Ready Static sample for a developer workstation posture.
  • Active agents 3 staged Synthetic lanes only; no hosted agent session is queried.
  • Event stream Sampled Timeline rows are deterministic copy, not live telemetry.
  • Mission state On rails Spec, tasks, and validation gates stay visible to operators.

Static by design The public website ships as Astro output with no server adapter in this session.

No runtime collection Hero panels do not read visitor identity, storage, prompts, or local paths.

External actions labeled The zero-install demo is synthetic and separate from real local sessions. Public GitBook documentation hosted separately from this website.

Battlefield preview

A synthetic mission map, not a live session.

The board below shows how FactionOS can stage agent work, route intent, and keep review state visible without reading a visitor device.

Mode Static sample Data synthetic Runtime no live calls

Synthetic mission battlefield preview

Static sample
  1. A1
  2. B2
  3. C3
  4. D4
  1. north
  2. center
  3. south
  1. Plan to build handoff Active sample route
  2. Build to review handoff Ready sample route
  3. Claim boundary check Warning sample route
  1. recon Recon lane Plans scope Active sample

    Blue status ring means the sample lane is in motion.

    Active planning ring
  2. builder Builder lane Stages changes Ready sample

    Green status ring means the sample lane is ready.

    Ready implementation ring
  3. review Review lane Checks gates Queued sample

    Purple status ring means the sample lane is awaiting review.

    Queued review ring
  4. risk Risk marker Flags claims Warning sample

    Red status ring marks a sample copy-risk checkpoint.

    Warning boundary ring

Legend pairs each color with text state and description.

  • Active Cyan ring with active text label.
  • Ready Green ring with ready text label.
  • Queued Purple ring with queued text label.
  • Warning Red ring with warning text label.

Sample objective

Mission state

Objective sample Access static only
Active objective
Coordinate planning, implementation, and review lanes for a sample launch task.
Mission progress
68% sample Deterministic progress marker for product storytelling only.

No live telemetry All lanes, coordinates, traces, and events are authored sample data. The page does not inspect prompts, local paths, terminal output, or hosted sessions.

Sanitized sample

Trace rail

  1. 01 Spec packet Homepage mission brief

    Sample artifact label only; no file path, prompt, or content body is shown.

  2. 02 Tool window Approval checkpoint

    Shows a bounded decision state, not a command transcript or executable action.

  3. 03 Review note Copy claim gate

    Flags hosted-runtime wording before the sample story moves forward.

  4. 04 Build gate Static route check

    Represents a package validation gate without terminal output.

Deterministic rows

Event stream

Static sample timeline. These rows are not live telemetry, replay data, or hosted runtime output.

  1. Mission staged

    Synthetic lanes loaded from the typed homepage data module.

  2. Route linked

    Sample handoff connects planning, build, and review states.

  3. Boundary checked

    Copy remains static, local-first, and free of visitor telemetry claims.

  4. Gate ready

    Sample build and review states are visible without live runtime access.

Product pillars

What the cockpit makes visible.

FactionOS frames agent work around observable local events, mission-level progress, and a clear boundary around what stays on the developer machine.

Observe

Keep agent work legible while it is happening.

Signal local hooks

FactionOS is shaped around hook events, prompt lifecycle markers, file-touch visibility, and local REST snapshots so operators can see what changed without scraping a visitor browser.

  • Hook lifecycle events become readable session rows.
  • File-touch and command-status signals stay attached to the local workspace context.
  • REST snapshots give the cockpit bounded state instead of raw terminal scrollback.

Coordinate

Turn parallel work into missions, lanes, and reviewable progress.

Frame missions

The battlefield layer gives active work a roster, objective, progress state, and handoff trail so a human can recover context after several agents or tasks move at once.

  • Mission labels separate planning, build, and review work.
  • Roster lanes show who or what is waiting, active, or blocked.
  • Progress states make handoffs visible without claiming perfect executor knowledge.

Contain

Start from the developer machine, not a hosted control plane.

Default no upload

Local-first by default for the core workflow. Prompts, paths, credentials, and runtime state stay local unless an operator deliberately configures an external adapter with its own contract.

  • The local server receives development events before any optional integration exists.
  • The browser cockpit reads local state surfaces instead of this public website.
  • External notifications remain adapter-bound and optional rather than automatic telemetry.

Hook to cockpit

A local event loop visitors can understand.

FactionOS turns local workflow signals into cockpit state through explicit contracts, bounded snapshots, and optional adapters that remain separate from website analytics.

Website static copy Runtime local install Adapters optional
  1. 01

    Local hook event

    A CLI or editor-side hook records a bounded lifecycle marker such as prompt started, tool requested, file touched, task updated, or validation completed.

    Input
    Agent workflow signal
    Output
    Structured local event

    Boundary The event begins on the developer machine and is not collected by this website.

  2. 02

    Local server ingest

    The local FactionOS server accepts the event, normalizes the contract, and prepares a small snapshot for the cockpit instead of shipping raw prompts or repository paths to a public host.

    Input
    Structured local event
    Output
    Bounded REST snapshot

    Boundary Ingest describes local product behavior; this homepage does not call that server.

  3. 03

    Cockpit stream update

    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.

    Input
    Bounded state change
    Output
    Visible cockpit update

    Boundary The sequence here is authored copy, not a live WebSocket or replay embed.

  4. 04

    Optional adapter notification

    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.

    Input
    Operator-approved signal
    Output
    External notice if enabled

    Boundary Adapters are optional and are not visitor analytics, account tracking, or automatic telemetry.

No live telemetry

Static sequence

This homepage section is rendered from typed Astro data. It does not connect to a local server, open a WebSocket, send visitor analytics, or embed a runtime replay.

Security boundary

The public site names what does not leave by default.

Local-first by default for the core workflow. The website is static, and the default product posture does not require hosted identity or uploading sensitive development context.

Hosted account

Default not required

No hosted account is required for the core local workflow.

Prompts

Default no upload

Prompt bodies are not uploaded by this website or promised as hosted collection.

Files and paths

Default local scope

Repository paths, file names, and file contents stay out of the public website surface.

Credentials

Default never asked

Secrets and tokens are not requested, stored, or transmitted by the static site.

Analytics

Default absent

Visitor analytics and runtime personalization remain absent from this first-release website.

Static website posture

Guardrails

  • The homepage does not host forms, auth, accounts, replay viewers, iframes, or runtime session queries.
  • The zero-install demo is synthetic and separate from real local sessions.
  • Future integrations must state payloads, controls, and local-only fallback behavior before being presented as defaults.

Latest field notes

Current product thinking and changelog signals.

Homepage previews are resolved at build time from non-draft content collection entries, then capped so this section stays a preview rather than a full index.

Mode static Drafts filtered Order newest first

Blog

Product and architecture notes

View all

Blog

From hook events to a local cockpit

A technical explainer for how FactionOS turns local agent events into readable cockpit state without adding hosted transfer by default.

Published
Author
FactionOS Team
Category
Architecture
Read
2 min
  • cockpit
  • hook events
  • local-first
  • technical

News

Release and changelog updates

View all

News

Blog and news publishing surfaces get launch polish

FactionOS public website publishing routes now have featured entries, category groups, related links, and draft-safe validation coverage.

Published
Author
FactionOS Team
Category
Changelog
Version
website-0.0.13
Read
1 min
  • changelog
  • publishing
  • website

News

FactionOS public site expands trust and content routes

The static FactionOS public website is expanding from product pages into use cases, security, publishing, and launch-support content.

Published
Author
FactionOS Team
Category
Company
Version
site-expansion
Read
2 min
  • company
  • public site
  • website

Next action

Open the synthetic demo, then keep the docs nearby.

Synthetic zero-install demo hosted separately from this website. Use the public GitBook docs for setup and product context. Both destinations are separate from this static homepage.

Open Demo (external link) Read Docs (external link)
External demo separate site

Synthetic zero-install demo hosted separately from this website.

External docs separate site

Public GitBook documentation hosted separately from this website.

Boundary These calls to action leave the public website. They do not embed a hosted app, create an account, collect prompts, query local paths, or start telemetry from this page.