StarNet

Local-first desktop agent harness

The map is the permission model.

A pixel-art station could be decoration. Here the project insists it is a projection of live runtime state, and publishes what each drawn element actually means.

Read the sourceInstall guide
The stated product law

The interface must never assert state the harness cannot prove. Quoted from the project, and it is the reason this page has a legend rather than a screenshot.

What you draw, and what it grants

The project's own contract
A room
is a capability-scoped team.
A hallway
is an authorized handoff lane.
A placed object
is a real capability grant.

Shapes here stand in for the station's rendering; they are a legend, not a screenshot.
The project states the layout you draw is the workflow the agents run.

Real calls

Model calls stream through a local sidecar, with tools gated by capability and consent checks.

Real state

Memory, transcripts, spend records, tasks and schedules persist on disk.

Real separation

Agents run concurrently with separate workspaces and bounded permissions.

What it does not simulate

Revenue, completed work, model activity, or spend. That list is the project's own, and keys stay in the OS keychain rather than the frontend. MIT licensed, with Windows described as the most-tested desktop target.