HARNESS.OS ·SASH.DEV ·CLI.AGENTS ·SKILL.INJECTION ·ROOM.URLS ·MODULE.CONTRACTS ·WIDGET.SURFACES ·OPEN.SPEC ·FIWORK.STEWARDSHIP ·DEVELOPMENT.CHANNEL ·HARNESS.OS ·SASH.DEV ·CLI.AGENTS ·SKILL.INJECTION ·ROOM.URLS ·MODULE.CONTRACTS ·WIDGET.SURFACES ·OPEN.SPEC ·FIWORK.STEWARDSHIP ·DEVELOPMENT.CHANNEL ·HARNESS.OS ·SASH.DEV ·CLI.AGENTS ·SKILL.INJECTION ·ROOM.URLS ·MODULE.CONTRACTS ·WIDGET.SURFACES ·OPEN.SPEC ·FIWORK.STEWARDSHIP ·DEVELOPMENT.CHANNEL ·

OPEN-SOURCE AGENTIC RUNTIME / DEV CHANNEL

The shell, the harness, the workspace.

Sash is being built as FIWORK's reference implementation of Harness OS: a CLI-native runtime for agents, skills, visual workspace primitives, domain modules, and multiplayer rooms.

VIEW BUILD STATUS AUDIENCE MAP

NODE_agentDEV

> OPEN NODE_AGENT
> CHANNEL: DEVELOPMENT
> STATUS: ADAPTER TARGET

- Claude Code, Codex CLI, Gemini CLI, OpenCode, Manus.
- Sash stays above the per-agent harness and dispatches work at the task boundary.

WHAT IS BEING BUILT

A real workspace around whatever CLI agent you already use.

These are product primitives under development, not finished claims. The current posture is spec stability before feature breadth.

TERMINALDEV

The agent keeps its native CLI surface, with Sash coordinating the shared workspace around it.

BROWSER PANELDEV

A real browser surface the runtime can expose, drive, and hand back to the human.

WIDGETSDEV

Structured charts, tables, forms, leaderboards, and domain-specific surfaces authored by modules.

SIDE PANELDEV

Persistent context for notes, memory, strategy, and session state beside the terminal.

FILE SURFACEDEV

Sash-aware review flows for diffs, approvals, and file operations.

MODAL / NOTIFYDEV

Human decision points and long-running alerts when the agent needs attention.

SASH_POSITIONING.LOGLIVE DRAFT

BUILDER PITCH

Superpowered CLI: your agent gets a real workspace, structured surfaces, injected skills, and room URLs.

ENTERPRISE PITCH

Everywhere: see, govern, and operate AI work across agents, teams, approvals, credentials, and audit.

DISTRIBUTION FRAME

Multiplayer rooms are the Class B loop: every collaboration moment becomes an invitation event.

BOUNDARY

Not an IDE, not an agent framework, not a vendor-specific SaaS. Sash is the runtime layer.

AUDIENCE TARGETING

PRIMARYROUTE

Builders

Power-user developers already running CLI agents daily. The message is artifact quality: a runtime they recognize as the thing they were about to build.

ECOSYSTEMROUTE

Module Authors

Domain experts packaging conductor agents for legal, science, devops, design, finance, content, and the long tail.

PROTOCOLROUTE

Runtime Implementers

Teams that may implement Harness OS in their own product. They need a stable spec and proof that modules can travel.

LATERROUTE

Enterprise Buyers

CTOs, platform, and security leaders who need to see, govern, and operate agent work across mixed vendor stacks.

DEVELOPMENT STATUS

NOW

Development site, Harness OS v0.1 work, runtime prototype framing.

PHASE 0

Single-player runtime credibility, room substrate, and multiplayer access model.

PHASE 1

First-party dogfooding across Canon, Viberfy, Rank; markdown import bridge.

PHASE 2+

Community modules, registry, ship primitive, hosted Sash, enterprise controls.