sno-ai/sno-station
Sno Station — your Claude Code and Codex working as one squad on your own machine. Shared encrypted memory, agent-to-agent messaging (Reach), squad skills for handoff and cross-vendor review, and a nightly loop that rewrites the agents' own skills with your approval. Open source, no daemon, no cloud required. Assembled in public.
From the publisher
README & documentation
Preview queuedRead the project’s overview, installation instructions and usage examples. The original README is the source of truth.
This entry is waiting for a bounded documentation import. You can read its original README now; no generated text has been substituted.
Read the full README ↗ · No documentation snapshot yet
Documentation belongs to its respective authors. Reported project/model license: Apache-2.0. A listing is not a grant of reuse or training rights. Confirm the document’s own terms at the source.
What this repository does
Sno Station — your Claude Code and Codex working as one squad on your own machine. Shared encrypted memory, agent-to-agent messaging (Reach), squad skills for handoff and cross-vendor review, and a nightly loop that rewrites the agents' own skills with your approval. Open source, no daemon, no cloud required. Assembled in public.
Repository facts
- Owner
- sno-ai
- Primary language
- TypeScript
- Stars
- 232
- Forks
- 193
- Open issues + pull requests
- 6
- License
- Apache-2.0
- Archived
- No
- Default branch
- main
- Created
- 2026-09-19T06:55:24.000Z
- Last push
- 2026-09-26T01:56:10.000Z
Topics and intended use
Owner-supplied topics: agent-communication, agent-memory, agentic-ai, ai-agents, claude-code, codex, coding-agents, developer-tools, local-first, long-term-memory, multi-agent, open-source, openclaw, own-your-data, self-improving, shared-memory, sno, sno-ai, squad, typescript
Review the README for scope, installation, examples and limitations. We do not run repository code or certify it.
Evaluate before installing
Review licensing and dependencies, inspect recent commits and unresolved issues, and test in an isolated environment before production use. Stars and forks alone cannot answer these questions.
Source and freshness
Source: GitHub. Metadata observed 2026-09-26T12:03:50.182Z. Daily imports are snapshots, not real-time monitoring.
Popularity and source listings do not establish security, suitability, licensing rights or benchmark performance.