Open source · local-first · by Kontour
Bring your agents, projects, and devices together. Hand a Task to the agent you choose, and keep the gates, evidence, and receipts beside the work so "done" means proven rather than asserted.
Active development under Apache-2.0. Run from source on macOS or Linux, or try the macOS Nightly desktop build. A verified installer ships with the first stable release.
Platform
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 the context, the gates, and the record.
Understand agents and connectionsProjects, Tasks, Sessions, changed files, artifacts, and receipts stay linked. Reopen a Task later with its workspace binding and evidence intact.
Understand Projects, Tasks, and SessionsGate outcomes, missing evidence, route-backs, exceptions, and readiness stay visible beside the work they describe. A confident answer is never mistaken for a verified outcome.
Understand gates and receiptsStation data lives on your machine by default. Hosted Model connections, Engines, paired devices, remote computers, and export endpoints carry your data only when you configure and use them; desktop builds also check their release feed for updates.
Get startedPair a phone, tablet, or laptop to your Station with scoped, revocable access. Delegate work to another computer you own over SSH and let it run with that machine's own agents and credentials.
Read about computer relationshipsPlugins add layouts, agents, tools, knowledge, connections, skills, and purpose-built work surfaces on the same SDK the core uses.
Read the plugin guideUse cases
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.
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.
Point a Station agent at a local model server. Inference stays on this machine, and every other data-carrying connection is one you add yourself.
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.
Build the container image from the checkout, run it behind your own authenticated ingress, and pair devices with scoped, revocable access. A published image is not yet available for anonymous pulls.
Read the deployment guideWrite a plugin: a review workbench, a release console, a domain-specific layout. Plugins get the same primitives as the core.
Who it is for
Keep your preferred connections, project context, reusable skills, and agent work in one local workspace you own.
A trusted group can run one Station on a machine it controls and use separate device grants with scoped access, keeping verification evidence attached to the work. Station does not yet provide per-person membership, roles, or person-level attribution; those are on the roadmap.
Self-host on infrastructure you control, keep data local by default, and make readiness, policy depth, and receipts visible. Person-level access control and hosted multi-tenant operation are delivery targets, not available today.
Get Station
Station is open source and under active development. A signed stable release ring has not been published yet, so the verified installer is not available yet.
macOS and Linux. Needs Node.js 24, npm 10 or newer, and git. Clone the repository, install dependencies with the managed lifecycle command, and start the app from the checkout.
Source instructionsmacOS on Apple silicon. A rolling pre-release published from the main branch for testers. It installs alongside a stable Station and updates through its own channel. Not a stable release.
Nightly desktop pre-releaseArrives with the first stable release. The bootstrap verifies the release's build attestation and checksum before installing, and upgrades in place when run again. Not available until a signed release ring is published.
Read the install guideDevelopers
Layouts, agents, tools, knowledge, and connections ship as plugins on a published SDK. Start from the scaffold, then use the full reference and runnable examples.
Build your first pluginA published client manages chats, agents, sessions, and remote Stations from a terminal, and a contributor entry point drives a checkout.
CLI referenceAuthenticated routes and streaming events on one origin, with server, connection, and orchestration contracts published as packages.
API referencePresent agent work inside your application, add a tool to a workspace, or run a private environment. The integration guide names the public contracts and the evidence to retain.
Integration guideA module map records each module's interface, seams, adapters, and test surface. Design records and ADRs carry decisions and their status.
Module mapIssue-first, safe-direct, and discuss-first paths; a pull-request contract that asks for the outcome, the exact commands and receipts, and every unverified claim.
Contributing guide
Published packages: @kontourai/station-sdk (plugin SDK),
@kontourai/station-cli (client),
@kontourai/station-contracts and
@kontourai/station-shared (server, connection, and
orchestration contracts plus shared helpers). Station consumes Kontour's
primitives — Surface, Flow, Veritas, Survey, and Flow Agents —
through the same published contracts available to any consumer.
Run Station, connect a model or an engine, open a project, and keep the first Task's evidence with the work from the beginning.
Get started