Sno Station 🧊 — Agents, assemble. Two heads are better than one, and smarter by morning.
Read in other languages: English · 中文 · Deutsch · Español · Français · Русский · 한국어 · 日本語 · 繁體中文
Sno Station is your agents' workstation: open-source software that turns the AI agents you already run, coding agents and general-purpose working agents alike, into one squad on your own machine. When one of them hits its rate limit, the other picks up with the context intact. They review each other's work, so fewer mistakes reach you. And the workspace they share gets smarter every night: it reads their sessions, proposes changes to their own skills, and waits for you to say yes.
Yours, and it stays yours. Memory, messages and skills live in one workspace on your laptop. No daemon, no server, no cloud required; the cloud side, when it comes, is optional and the product is complete without it. Apache-2.0, edge to edge. The memory store is encrypted on your machine from first use, with a key that is provisioned once and never leaves it; Sno never receives your database or your key. The full boundary, what it protects against and what it does not, is in docs/security.md.
Works in your language. Talk to your agents in English, Chinese (Simplified or Traditional), Japanese, Korean, German, French, Spanish or Russian; the memory engine stores each memory with its language, classifies by locale, and keeps CJK text intact in every key and search. The Duo skills are written to be followed in whatever language you use with your agent, and this README ships in nine.
Open in public. This repository has been public since 2026-09-18. Everything here is real and runs. Every block below says when it was last updated.
Install · Connect your account · How to use · What runs today · Memory that forgets on purpose · Design partners · References
Install
Last updated 2026-10-07. Shared memory installs today. It gives Claude Code, Codex, OpenClaw and Hermes Agent one encrypted memory on your machine, with no account and no API key. The easiest way: tell your AI agent "install sno.ai from GitHub". Or install the sno command once, then run sno setup for each agent:
# Install the sno command once
sh -c 'sno_installer_body=$(curl -fsSL https://sno.ai/install) && printf "%s\n" "$sno_installer_body" | sh'
# Codex CLI
sno setup --harness codex
# Claude Code
sno setup --harness claude
# OpenClaw
sno setup --harness openclaw
# Hermes Agent
sno setup --harness hermes
Walkthroughs: Codex · Claude Code · OpenClaw · Hermes
sno setup also installs Sno Reach, the small helper programs, the skills and the nightly loop, and every command is sno <name>: the full list is in docs/sno-commands.md. Say "Sno onboarding" inside your agent and it walks you through the same setup in conversation. It also starts by itself right after the install.
# inside any Claude Code, Codex or OpenClaw conversation:
Sno onboarding
The agent runs the setup itself through the sno CLI: shared memory, Sno Reach, the
Duo skills, and the hooks each harness needs. No package names to remember.
Connect your sno.ai account
Last updated 2026-10-08. Optional: everything works without an account. Connect to see on your sno.ai dashboard what your agents did for you: problems their reviews caught, what the nightly loop taught them, skills that got better, how long they kept working, and what they remembered.
Connecting never creates an account for you. sno setup gives each computer an anonymous identity; connecting attaches it to your account, so everything the computer sent before and after counts as yours.
No account yet (computer first). Onboarding shows a link made for this computer only (a one-time code that expires). Open it, sign up, and you land back on the approval page; click Approve. Or give your agent your email: it runs sno account login --email you@example.com and you sign in once.
Already have an account (account first). On the computer, run one command:
sno account claim
Open the link it prints while signed in to sno.ai and click Approve. The computer shows up on your computers page by itself. There is no separate update step: sno updates itself when it finds a newer release.
How to use
Last updated 2026-09-19. Once installed, you keep working exactly as before, in whichever agent you like. Three things change:
- One of them hits its cap. Say
sno reach callfrom the other one; it picks up the task from the shared memory and the mailbox, context intact. - You want a second pair of eyes. Ask either agent to
peer-reviewthe other's work. The reviewer is always from the other harness. - Every night the RSI loop runs. In the morning,
sno rem-reflect accept <id>for the proposals you like. Nothing changes without that accept.
"I yelled at my agent last night. It took notes."
What this looks like on our own machine. Three days, three reports. Last updated 2026-09-19.
Day one — it learns.
That is a real report from the RSI loop we run on this repository. Once a day it reads our own agent sessions, finds the mistakes that repeat, and proposes changes to the agents' own skill files. A human reads the proposals and accepts or rejects them. Nothing changes without that accept. The two things the owner was frustrated about that evening were rules in the live skills by the next morning; nobody typed them in.
Day two — it checks its own homework.
The next run fired on its own at 00:58, read 113 sessions, and measured the three skills it had changed the day before. Failures in all three dropped to zero. It also found a real bug in our release script that zsh had been hiding from bash. Nobody told it to look.
Day three — you install it. The RSI loop is a skill in this repository, and sno setup installs
it with the rest. This section updates as the loop runs: a new report each week, nothing retouched.
It is inspired by two pieces of work we keep coming back to: Andrej Karpathy's "LLM Wiki" — the idea that an agent should keep a persistent, editable wiki of what it has learned instead of re-deriving it every session — and "WikiSkill" from Google Research and Virginia Tech, which compiles an agent's own experience into persistent knowledge that rewrites its skills. Links in References.
"In months, the other one has never once said 'looks good.'"
We have had Claude Code review Codex's work and Codex review Claude Code's on this repository for months. Not one review has come back empty. Not one. We used to think that meant the work was bad. It means one reviewer from one harness is never enough.
We call the pair a Duo: the smallest squad. We never say which one is the careful one and which one is the fast one. It flips by month and by job. The point is that they differ.
"I went to bed. It changed shifts."
What this looks like on our own machine, 2026-09-18.
One of our agents was twenty-one tasks into a twenty-seven-task build when its weekly quota reached 2%. It did not stop there and wait to die. It wrote a handover brief: what was done, what was half-done, the exact commit to continue from. Then it woke an agent from the other harness and would not let it touch anything until it had measured the brief's size and checksum and said so.
One thing went wrong, and it is the part worth reading. The receiver started editing before it had acknowledged the release. The sender caught it, paused it, rewrote the brief, and released again properly. Fourteen minutes and forty-one seconds after the handover began, the second agent was working and the first one signed off with 1% left. Every commit from before the handover is intact; the second agent continued from the first unchecked task, not from the beginning. I was asleep for all of it.
The whole night is in docs/evidence/rotation-2026-09-18/: every quota reading five minutes apart, both versions of the brief, the readiness and release receipts, and the commit summary. Host names, addresses and session ids are redacted; nothing else is touched.
What runs today
*Last updated 202