Everyone gets an agent. The knowledge stays shared.

Each person's agent is theirs. Team knowledge travels through Git and plain files. No server to run.

Your agent is yours.

Personal by default. You decide what to share.

It fits the way you work. Personal notes, shortcuts, preferences, all private. You share what you want, when you want.

// Each person has their own agent You: What are my code review preferences? Agent: From your personal vault: - Always check error handling first - Flag any function over 50 lines - Skip nitpicks on draft PRs (only you see these)

Share what's useful.

Team conventions, opt-in. No cloud.

When the team agrees on conventions, connect a shared vault. Everyone still works the way they want to. Nobody has to change their setup.

# Connect the team vault (one time) $ npx @soleri/cli vault connect ../team-standards ✓ Connected: team-standards ✓ 42 team patterns now available in search ✓ Your personal vault still ranks first # Teammates do the same — no server needed

Distribute knowledge like code.

Version it, install it, keep everyone on the same page.

Package your team's standards the same way you'd ship a library. Version them, publish them, install with one command.

# Install a team knowledge pack $ npx @soleri/cli pack install ../team-standards ✓ Installed team-standards@0.2.0 ✓ 18 patterns, 4 playbooks, 2 skills # Or from npm $ npx @soleri/cli pack install @your-org/api-conventions ✓ Installed api-conventions@1.0.0

New person? Ready in minutes.

They get the current standards on day one.

New teammate connects the team vault and immediately sees every convention, ranked by importance. Beats a week of reading onboarding docs nobody maintains.

// Day 1 — new developer joins New dev: What are the critical patterns for this project? Agent: Top patterns from the team vault: 1. API errors: { error, code, details } 2. Auth: httpOnly cookies, never localStorage 3. DB: always set migration rollback 4. Tests: name files *.test.ts, not *.spec.ts Want me to walk you through the code review playbook?

Control what gets in.

Works like PR review, but for knowledge.

Shared stuff goes through review before it's live. You set the rules: auto-approve the small things, require sign-off on the rest.

# Set governance for the team vault $ npx @soleri/cli governance --preset moderate Policy: Suggestions auto-approve Warnings propose for review Critical propose for review Quota 50 entries per domain Duplicate check enabled # Like PR review, but for team knowledge

Try it.

One command to start. Works with Claude Code, Cursor, Codex, and OpenCode.

Explore on GitHub Get started