TL;DR

Sno Station (sno-ai/sno-station) is an open-source layer that sits on top of the coding agents you already pay for (Claude Code, Codex, Cursor, Hermes Agent and OpenClaw) and makes them work as one team. They share one encrypted local memory, message each other directly, review each other’s code in fresh sessions, and hand a long task to a different agent when one runs out of quota. A nightly “Self Learning” job proposes edits to the agents’ own skills, which you approve one by one.

Not run by us: our container test lab could not run today (GitHub Actions refused to start the job for a billing reason on our side), and Sno Station’s core features need signed-in Claude Code or Codex subscriptions anyway. Nothing below comes from running Sno Station ourselves. It is based on the repository, its docs, release notes, published eval receipts, the pricing page and a read of the install script.

Facts as of November 18, 2026:

  • 1,026 GitHub stars and 372 forks; repository public since September 2026.
  • 3 open issues (issues only, not pull requests).
  • Latest release: v2.1.1, published November 18, 2026. Version 2.0.0 (“Tag Team”) shipped November 4, 2026. The installer currently fetches the sno CLI 1.3.2.
  • License: Apache-2.0 (both the station repo and the sno CLI repo).
  • Runs on Linux, macOS and WSL2. No API key; it drives your existing agent subscriptions.
  • A free sno.ai account tier exists, plus Plus ($19/month) and Max ($199/month) tiers for the cloud parts.

Verdict: Sno Station is the most complete attempt so far at the “two vendors, one team” workflow: builder plus reviewer from different vendors, quota handoff, shared memory. It is unusually candid about what it has and has not proven. But it is a big, fast-moving install (hooks, timers, skills, shell profile edits) whose defaults upload session data to Sno’s cloud. Try it on a non-sensitive repo first, and set sno station consent before you point it at client code.

Quick Reference

FieldValue
What it isShared memory, agent messaging, review/handoff skills and a nightly learning loop across coding agents
AgentsClaude Code, Codex, Cursor (app on macOS, cursor-agent CLI), Hermes Agent, OpenClaw
Install`curl -fsSL https://sno.ai/install
Start a builder + reviewersno reach pair "Fix the login redirect"
Dashboard of your agentssno squad
Morning summarysno away-brief run
MemoryLocal SQLite, AES-256 page encryption (SQLCipher v4-compatible)
PlatformsLinux, macOS, WSL2 (no native Windows)
LicenseApache-2.0
Latestv2.1.1 (November 18, 2026)

What Problem Sno Station Solves

If you run Claude Code in one terminal and Codex in another, you are the one copying diffs between windows, and when Claude hits its five-hour limit at 2 a.m., the task sits until morning. The README’s design rule is “the work does not stop because one agent did”: a usage limit triggers a handover, review happens in a different agent’s fresh session, “done” must be backed by a real command run, and you come back to one summary page. It is explicitly not another agent or model; it is glue between the harnesses you already have.

How It Works

Sno Station has five main parts. The sno CLI is the only command it puts on your PATH; everything else is a subcommand.

1. Shared memory

All connected agents read and write one memory store via hooks (SessionStart, UserPromptSubmit, Stop and so on). Facts are retired when a newer one replaces it. The v2.1.0 release leans on this: say a rule to Claude Code, change your mind in Codex, and the old version stops reaching every agent. Agents can also use it explicitly:

sno memory remember --harness claude "Staging Postgres listens on 5433"
sno memory recall --harness codex "staging database port"
sno memory correct --harness codex <id> "Staging Postgres moved to 5434"

Retrieval is hybrid keyword plus local vector search, then a local reranker (about 206 MB, downloaded on first recall) runs on your CPU.

2. Sno Reach: agent-to-agent messaging

Reach gives agents two channels: Instant Messenger (ask another agent now and wait for its actual reply) and Agent Email (leave a task in its inbox and read the reply later). It also works across machines on a LAN or over Tailscale, with no central messaging server: each machine runs its own receiver.

sno reach call reviewer "Check the error handling in this diff" --timeout 600
sno reach pair "Fix the login redirect"

reach pair is the headline command of 2.0: it starts two agents in tmux windows, one building and one challenging the result. With only one vendor signed in you still get two sessions, and the command tells you the review “stayed in the same family”.

3. Squad skills

The behaviour lives in sno-station-skills (Apache-2.0, 865 stars as of November 18, 2026), installed into Claude Code and Codex. The important ones:

  • rotate-agent: at 2% of remaining quota, write a handover (done, half-done, exact commit) and wake the other vendor’s agent. sno subscription-quota-check reads Claude Code and Codex quota without spending any.
  • peer-review: review by a different agent in a fresh session, with hard caps (3 rounds on code, 5 on a plan, 1 on tests) before it stops and waits for a person, and a findings ledger so a disputed finding is not raised as new every round.
  • Work orders / /deliver: a “charter” with success checks; sno deliver-proof run records the proving command output.
  • Chief of staff (/cos in Claude Code, $cos in Codex): one agent becomes your single contact and opens a lead agent per project.

4. Finish: timed and long-running work

Tell an agent “check the nightly build tomorrow at 9” and a per-minute service starts an agent at that time, even if the conversation was closed. sno heartbeat --due --problems lists what did not run and why. Per the docs, timed tasks start Claude Code and Codex only, and a full computer restart “has not been through a real test”.

5. Self Learning (the “REM” loop)

Every night a separate model reads the day’s sessions from all your agents, finds mistakes that repeat, and proposes edits to the agents’ own skills. Nothing changes until you accept a proposal:

sno rem-reflect accept <id>

In Claude Code and Codex, an accepted lesson applies from the next reply, not the next session.

Installation

The official one-liner:

curl -fsSL https://sno.ai/install | sh

Or, inside Claude Code, Codex, Cursor, Hermes or OpenClaw: install sno.ai from GitHub, then Sno onboard.

We read the install script before writing this. What it does, in order:

  1. Downloads the sno binary from the sno-ai/sno-cli GitHub releases and checks its SHA-256 against a digest embedded in the script, plus the reported version. Good hygiene for a curl | sh.
  2. Installs to ~/.local/bin/sno and edits your shell startup files (for zsh both .zprofile and .zshrc) between # BEGIN SNO PATH markers.
  3. Runs sno init, then sno setup automatically, which connects every agent it finds: hooks, skills, Reach, memory and the nightly timer.
  4. Prints a block of instructions addressed to your AI agent, telling it to run sno skills onboard next and ask you two questions: which memory mode, and whether to link the computer to a free sno.ai account.

So the script’s output is partly a prompt for your agent. That is transparent (the script is short and readable), but the “install it for me” path hands a lot of setup authority to the agent at once. The memory service (@snoai/memory) needs Node.js 22.22.3+, 24.15.0+ or 25.9.0+, and updates are automatic: once a day the first sno command installs any new release.

Privacy: Read This Before You Install

Sno Station’s local story is solid, and its docs are clear about where it stops:

  • The memory store is SQLite with page-level AES-256 (SQLCipher v4-compatible). The key lives in ~/.sno/settings.json (mode 0600); Sno never receives it, and there is no recovery copy.
  • docs/security.md says it does not protect against malware running as your user, OS swap, or what you send to your LLM provider.

The cloud side depends on the memory mode you pick at onboarding:

ModeWhat leaves your machine
Local FirstNo memory text uploaded
Agent NativeBy default, the day’s sessions upload to Sno nightly for Self Learning; can be switched off in ~/.sno/settings.json
REM EnhancedYour memory text and learned lessons go to your own space in Sno’s cloud

Separately, the sno CLI README says the telemetry consent setting defaults to full, which “also uploads the sessions and skills Self Learning reads, and short excerpts for review”. sno station consent off uploads nothing; metadata-only sends usage counts only. If you work on proprietary or client code, set that first.

Pricing

The software is free and Apache-2.0. The cloud allowance for memory processing and Self Learning is metered weekly, per the sno.ai pricing page as of November 18, 2026:

PlanPriceWeekly allowance
Free$0Memory for about 150 messages, Self Learning from about 20 sessions
Plus$19/month3× memory, 5× Self Learning
Max$199/month45× memory, 65× Self Learning

An unlinked computer gets one tenth of the free allowance until you run sno account claim. When the allowance runs out, your balance is used, and after that Sno falls back to your own agent’s model. Your Claude and OpenAI subscriptions are, of course, still separate costs.

What the Project’s Numbers Say

Sno publishes “receipts” in evals/, all first-party:

  • LongMemEval-S retrieval: the project reports R@5 95.4% over 500 questions, retrieval only.
  • LoCoMo: 1,492/1,542 (96.76%), which the receipt itself says is a merged answer set re-answered after fixes, so “not a single-run score”.
  • Memora (forgetting): FAMA 87.2 with a 3.76-point forgetting penalty; the project calls its comparison to the paper’s systems “directional”.

Each receipt states its own caveat and links per-question evidence, but “the public harness is not included yet”, so nobody outside the team can rerun them. None measure the squad features (handoff, cross-vendor review).

What Is Proven and What Is Not

The README’s status table (last updated November 4) says “proven” only once a row has run on a clean machine. Shared memory across all five agents is proven end to end. The 2.0 squad features were run with real Claude Code and Codex agents. Cursor’s CLI is proven on clean Linux; the macOS app is “still being proven”. Hermes Agent and OpenClaw “have not been through these journeys on real installs”.

So in practice this is a Claude Code + Codex product today, with Cursor close behind and the other two on memory only.

Community Reaction

Sno Station is young (public since mid-September 2026) and we found no substantial independent discussion on Hacker News or Reddit yet. The README quotes complaints from r/ClaudeCode and r/codex (“Ran out of my 5-hour limit within 30 minutes”, “Codex never finishes a review”) and maps a feature to each. Those are the right problems; whether the answers hold up in other people’s repos is still open.

The project also published a handover that went wrong on September 18: the second agent started editing before confirming the handover, and the first agent paused it and redid the note. Everything is in docs/evidence/rotation-2026-09-18. That is one night run by the authors, not a reliability rate.

Honest Limitations

  • Big install surface. Hooks into every agent, a per-minute service, a nightly timer, skills, shell profile edits and silent daily self-updates. Easy to start, more to audit. sno uninstall --purge-state exists; know where it is.
  • Data leaves by default. Telemetry consent defaults to full, and Agent Native uploads sessions nightly unless you turn it off. Local First and consent off exist; you have to choose them.
  • Two subscriptions to get the main benefit. Cross-vendor review and quota rotation need both Claude Code and Codex signed in. With one vendor, review stays “in the same family”, which is exactly the weakness the project argues against.
  • Fast churn. Five releases between November 4 and November 18. Good for fixes, harder for a team that wants a stable tool.
  • Open bugs are small but real: cancelling a timed task whose action contains " | " picks the wrong text (#241), and a heartbeat case fails when tmux runs commands with bash (#236).
  • Key custody is on you. Lose settings.json and the memory is unrecoverable.

Sno Station vs. Alternatives

ToolPick it when
Sno StationYou pay for Claude Code and Codex and want them to cover for each other
Agent multiplexers (Herdr, tmux)You want to see and drive agents, not have them coordinate
Single-vendor subagentsOne subscription; accept same-model blind spots
Standalone memory layersYou only need memory, not handoff or review

Who Should Use It

Good fit: solo developers and small teams running Claude Code and Codex side by side on long tasks, who are tired of shuttling diffs and losing overnight runs to usage limits.

Wait or go narrow: teams with strict data rules (start in Local First with consent off), Windows-native users, and anyone whose main agent is Hermes or OpenClaw, until those journeys are proven.

FAQ

What is Sno Station?

Sno Station is an Apache-2.0 open-source workstation layer that connects Claude Code, Codex, Cursor, Hermes Agent and OpenClaw on one machine or across machines. The agents share one encrypted memory, message each other through Sno Reach, review each other’s work in fresh sessions, and hand tasks over when one hits a usage limit.

Does Sno Station need an API key?

No. It drives the agents you already have signed in, using their subscriptions. A free sno.ai account is optional but recommended: an unlinked computer gets one tenth of the free cloud allowance. Paid tiers are $19 and $199 per month as of November 2026.

How does the usage-limit handoff work?

Tell the working agent to use the rotate-agent skill. At 2% of remaining quota it writes a handover with finished work, half-finished work and the exact commit, then wakes a different agent (for example Codex for a Claude Code task), which continues from that commit.

Does Sno Station send my code to the cloud?

The memory database stays local and encrypted. What leaves depends on settings: the CLI’s consent defaults to full, which uploads sessions Self Learning reads and short excerpts, and Agent Native mode uploads daily sessions by default. Choose Local First and run sno station consent off to upload nothing.

Which agents are fully supported?

Claude Code and Codex get every feature. Cursor gets memory, skills, review and takeover, with the macOS app still being proven. Hermes Agent and OpenClaw share the memory but have not been through the squad journeys on real installs.

Sources