Open Orchestrators
Back to directory
Sn

Player profile

Sno Station

An Apache-2.0 local coordination layer where coding agents share memory and a file-based mailbox, hand off tasks across provider limits and request review from another agent.

903 GitHub stars

Profile

Where it fits

Sno Station connects Codex, Claude Code, Cursor, Hermes Agent and OpenClaw on one computer. Shared memory, a file-based mailbox and reusable skills support handoffs and peer review without a long-running server or daemon. Linux and macOS are documented supported platforms.

Self Learning proposes skill changes for human acceptance. Data handling depends on configuration: REM Enhanced processes memory in Sno cloud, while Agent Native uses the configured agent model but uploads sessions for nightly Self Learning by default. Its session upload and cloud lesson retrieval can both be disabled in settings.

Builder web analytics

Measure outcomes from Sno Station-assisted work

Sno Station helps coordinate agent work. Separately configured product analytics can show the observed user-facing results of a deployed change.

This is an optional measurement workflow, not a native Sno Station integration with Agent Analytics. Configure product tracking and authorized analytics access separately; the listing does not install tracking or report agent-run telemetry.

First loop to measure

  1. a team coordinates and reviews a change to a product surface
  2. the reviewed change is deployed to a separately instrumented project
  3. a human or an authorized agent reads observed product outcomes
  4. the team uses that evidence to select the next task

Copyable prompt

If product tracking and analytics access are already configured, inspect the deployed change over an appropriate observation window. Report measured outcomes, missing evidence and limitations. Do not infer causation from before-and-after movement or treat agent activity as product usage.