Skip to main content
gridworkapache-2.0stage 5/6 · workspacepre-1.0

Built in the open

An agent operating system for the terminal.

GridWork is the operating layer for a fleet of coding agents: one append-only event log, one kernel, and one place that says what needs a human.

Read the docsView source
binary
gwa single Rust binary
truth
append-only event logevery view is a projection
surface
terminal-nativeno web console
$ cargo run -p gwk-cert -- crates/gwk-cert/fixtures/valid-stream.json
[]
gwk-cert: certified — 16 events, 0 findings
$ gw kernel health
{"type":"health","ready":true,"sealed":true}

Install GridWork

cargo install gridworkCopy
cargo build --workspace # stable Rust · msrv 1.94

Pre-1.0: expect breakage. Schemas, protocols, and the binary change without notice until 1.0. The headless CLI needs PostgreSQL 16 and separate admin and runtime roles. Review the prerequisites.

Where it actually is

Pre-alpha, at stage 5 of 6. The contract, kernel, engines, and console are done; the workspace multiplexer is the work now.

Working

  • The contract and kernel are published.
  • Certification runs against a real PostgreSQL 16.
  • The performance envelope is measured, not asserted.
  • The headless gw CLI speaks the kernel protocol.
  • gw tui opens five live lenses over the estate.

Not built yet

  • The exportable-as-evidence half of replay — recordings replay in the console, but not yet ledger-synced.
  • The workspace: the real multiplexer.
  • Engine host packaging — a separate, unpublished process until 1.0.

Read the six-stage roadmap

The architecture stays legible

Four boundaries define what owns truth, how clients behave, and where engine control belongs.

Read the architecture

Six stages, in order

Stages land when their gates are green. Contract, kernel, engines, and console have shipped; the workspace is current.

  1. 01

    Contract

    shipped

    The shared language and conformance surface.

  2. 02

    Kernel

    shipped

    The sole writer, projections, blobs, attention, and authority.

  3. 03

    Engines

    shipped

    PTY and agent-control adapters, certified by the parity matrix.

  4. 04

    Console

    shipped

    Five lenses over one estate: hall, work, fleet, flow, term.

  5. 05

    Workspace

    current

    A daily-driver terminal multiplexer.

  6. 06

    Context runtime

    planned

    Skills, memory, and knowledge as measured, receipted surfaces.

Principles that won't move

  • One append-only log owns every truth; user interfaces are projections of it.
  • The kernel is the sole writer; clients are thin.
  • Control never rides keystrokes.
  • Terminal only. No web console.

Full roadmap

Built by the thing it builds

The public repository begins after months of agent-operated software work, with authorship stated plainly.

7,300+
contributions in the measured window
5 mo
through July 2026
1 public repo
the first from this operating system

This profile's contribution graph is the receipt — 7,300+ contributions in the five months to July 2026, nearly all agent-authored, and until this repo, all of it in private repos. This is the first public one, and the agents that produced that graph are writing this codebase too: most commits here are agent-authored under human direction and review. That's disclosed as a fact, not a caveat — the same gates apply regardless of who typed the code.

Inspect the public repository

Clean-room means a traceable boundary

Apache-2.0 engine work is derived from permitted specifications and observations, never incompatible source.

Permitted

  • Public specifications cited by stable derivation ID.
  • Observed wire behavior captured in the public registry.

Forbidden

  • Code copied, ported, or mechanically translated from an incompatibly licensed project.
  • Copyleft terminal-multiplexer source in a gated engine author's context.

Independent second reader. Every clean-room change gets an additional fresh-context review with no exposure to the implementing session. The reader is not a second human, and the status check does not claim reviewer independence.

Read the derivation trail

Crates, without padding the surface

Published contract and kernel crates sit beside the engine and TUI work that remains planned.

Published and planned crates · stable Rust, MSRV 1.94
CrateWhatStatus
gwk-domainShared types, events, state machines — the contract0.0.2
gwk-certStream checker, plus the storage suite a backend runs against its own event store0.0.2
gwk-themeThe 15 SIGNAL design tokens — one source for the site, the TUI, and the generated TypeScript0.0.2
gwk-kernelDaemon: event store, projections, blobs, attention, authority, the wire0.0.2
gridworkShips the gw binary — the CLI that speaks the kernel's protocol0.0.2
gwkNamespace root for the gwk-* crates. No API0.0.2, name only
xtaskCodegen and release glue. Not publishedin-tree
gwk-ptyPTY engine: server-side VT, render-state deltas, reattachin tree, unpublished
gwk-pty-hostResident PTY engine host: session registry, spawn, detach/reattach routingin tree, unpublished — not in cargo install gridwork until its own release
gwk-adapter-*Per-engine ACP + hooks adaptersin tree, unpublished
gwk-parityThe engine parity matrix harness — runs locally, never in CIin tree, unpublished
gwk-textPure column arithmetic and extended grapheme boundariesin tree, unpublished
gwk-tuiThe client: modes, lenses, palettein tree, unpublished — five lenses and the live estate runtime
Before contributing, review the prerequisites and enforced gates in CONTRIBUTING.md.