kontourai/station

**The agent workspace where work ships with receipts.**
Station is Kontour's open-source, local-first workspace for agent work. Bring
your agents, projects, and devices together, hand a Task to the agent you
choose, and keep execution history, files, review evidence, and receipts beside
the work. A completed run and a passed review are separate facts.
Product site ·
Documentation ·
Getting started ·
Concepts ·
Contributing
> **Status:** open source under active development (Apache-2.0). Run Station
> from source on macOS or Linux, or try a Nightly desktop build.
> The portable installer requires a published release in the selected ring. See
> Get Station.
Why Station
Station brings several parts of agent work into one workspace:
- **Evidence beside the work** — inspect gate results, missing evidence,
review receipts, and exceptions where the configured workflow provides them.
Creating or completing a Task does not by itself prove a gate passed.
- **Supported engines, one workspace** — run Station agents on a local or
hosted model, or connect supported agent CLIs and compatible custom engines
as External agents. Each engine keeps its own behavior and tool loop;
Station supplies project context, execution records, and configured workflow
integrations.
- **Work that outlives a chat** — Projects, Tasks, Sessions, changed files,
artifacts, and receipts stay linked. Reopen a Task later with its recorded
workspace binding and evidence, then check the workspace's current availability.
- **Your devices, your Station** — pair a phone, tablet, or laptop to your
Station with scoped, revocable access, and delegate work to another
computer you own over SSH.
- **Local-first ownership** — Station data lives under ~/.station by
default. Networked features have separate settings and destinations;
review those boundaries under Data and privacy.
- **Built to extend** — plugins add layouts, agents, tools, knowledge,
connections, skills, and work surfaces through the public SDK and extension
contracts. Private core services are not part of that plugin API.
What people use it for
| You want to… | In Station |
| --- | --- |
| Ship a code change you can stand behind | Open the repository as a Project, create a Task, pick an agent, and keep the commands that ran, their results, and the review receipts with the change. |
| Keep a long piece of work alive | A Task spans as many Sessions as it needs. Follow it from a paired device and come back to the same context, files, and evidence. |
| Use agents without a cloud account | A configured local model can provide inference without a cloud account. Tools, engines, and other enabled integrations retain their own network behavior. |
| Coordinate several agents | Delegate bounded work from one agent to another, or run it on a remote computer over SSH with that machine's own agents, credentials, and workspace. |
| Run Station on a server you control | Review the deployment recipe, image provenance, home ownership, and authenticated ingress. |
| Build a purpose-built work surface | Write a plugin using the public SDK: a review workbench, a release console, or a domain-specific layout. |
Get Station
Run from source (macOS, Linux)
Requires Node.js 24.x, npm 10 or newer, and git. On Linux, interactive
terminal panes additionally need a C++ toolchain (g++, make, python3);
without one Station still runs and reports that capability as degraded.
Open the UI address the command prints, then follow
First steps. The developer guide
covers instances, ports, temporary homes, and the desktop app build.
Nightly desktop build
The Nightly desktop pre-release
carries macOS Apple silicon and Windows x64 builds for testers. Choose an asset