🪨 why use many token when few token do trick — Claude Code skill that cuts 65% of tokens by talking like caveman
CLI and AI console for Solana node management
SLV manages the full lifecycle of Solana validators, RPC nodes, and gRPC streaming from a local CLI. The AI Console (`slv c`) routes your request to specialist agents, then uses SSH, keys, snapshots, firewall setup, and Ansible playbooks to do the work.

Builders who run Solana infrastructure and want agent-guided deployment and operations.
You can deploy, check, and update Solana nodes from plain-language requests instead of doing every setup step by hand.
What it does
AI Console for node operations
`slv c` opens a conversational console that can deploy and operate Solana infrastructure through specialist agents.
Validator and RPC workflows
The tool supports validator, RPC, and gRPC Geyser deployments, including Jito, Agave, Firedancer, Yellowstone, and Richat.
Ansible-based execution
Requests are turned into Ansible playbooks and Jinja2 templates that run against the target server.
Standalone agent skills
The repo ships skills such as `slv-validator`, `slv-rpc`, and `slv-grpc-geyser` for use in other agents.
Direct non-AI automation
You can run the underlying Ansible playbooks directly for deployment, restart, and Solana build tasks.
Node health checks
Commands like `slv check`, `slv check rpc`, `slv check grpc`, and `slv check shreds` inspect server and service health.
How to get it
- 1Run
# 1. Install SLV curl -fsSL https://storage.slv.dev/slv/install | sh # 2. Configure your environment (AI provider, SSH keys, API keys) slv onboard # 3. Launch the AI Console slv c
- 2That's it. The AI Console guides you through everything
You: Deploy a mainnet Jito validator on 203.0.113.10 Agent: I'll set up a mainnet Jito validator. Let me walk you through: - Checking SSH connectivity... - Generating validator identity and vote keys... - Building Solana from source... - Downloading snapshot from nearest region... - Starting validator and monitoring slot sync...
README
SLV — Solana Node Manager with AI Console
Deploy and manage Solana validators, RPC nodes, and gRPC streaming in 3 commands.
SLV is a CLI tool that handles the full lifecycle of Solana infrastructure — from bare metal to running node. The built-in AI Console lets you deploy and operate nodes through natural conversation.
🆕 What's New
- 🟢 DoubleZero support — First-class integration with the DoubleZero low-latency network
- AI Console — Deploy nodes through conversation with specialist AI agents
- Performance tuning — Automated CPU governor, IRQ pinning, and kernel optimization
- Multi-region snapshots — 7 global snapshot endpoints for fast node bootstrapping
Quick Start
# 1. Install SLV
curl -fsSL https://storage.slv.dev/slv/install | sh
# 2. Configure your environment (AI provider, SSH keys, API keys)
slv onboard
# 3. Launch the AI Console
slv c
That's it. The AI Console guides you through everything:
You: Deploy a mainnet Jito validator on 203.0.113.10
Agent: I'll set up a mainnet Jito validator. Let me walk you through:
- Checking SSH connectivity...
- Generating validator identity and vote keys...
- Building Solana from source...
- Downloading snapshot from nearest region...
- Starting validator and monitoring slot sync...
What Can SLV Do?
| Task | Command |
|---|---|
| Install SLV | curl -fsSL https://storage.slv.dev/slv/install | sh |
| Initial setup | slv onboard |
| AI Console (interactive) | slv c |
| Check node status | slv check |
| Update Solana version | slv update |
| Server health | slv check rpc / slv check grpc / slv check shreds |
Supported Node Types
- Validators — Jito, Agave, Firedancer (mainnet & testnet)
- RPC Nodes — Standard, Index, Geyser gRPC, Index+gRPC
- gRPC Geyser Streaming — Yellowstone, Richat
AI Console Agents
The AI Console (slv c) includes specialist agents for different tasks:
| Agent | Role |
|---|---|
| Cecil | Validator deployments (Jito, Agave, Firedancer) |
| Tina | RPC & gRPC Geyser deployments |
| Figaro | Server procurement and pricing |
| Setzer | Solana app development |
Just describe what you need in plain language. The agent handles SSH, keys, builds, snapshots, firewall, and monitoring.
How It Works
SLV uses Ansible playbooks and Jinja2 templates under the hood:
Your request → AI Agent → Ansible playbooks → Target server
Design principles:
- Remote-only — manage everything from your local machine, no SSH into nodes
- Dummy key start — validators start with unstaked identity, then hot-switch
- Source builds — Solana binaries built from GitHub source
- Firewall-first — SSH restrictions and nftables from day one
- DoubleZero ready — opt-in low-latency networking for validators and RPC
Using AI Agent Skills (Advanced)
SLV also provides standalone AI agent skills that work with any AI coding agent — OpenClaw, Claude Code, Codex, Cursor, Windsurf, and more.
| Skill | What It Does |
|---|---|
| slv-validator | Deploy & manage validators |
| slv-rpc | Deploy & manage RPC nodes |
| slv-grpc-geyser | Deploy & manage gRPC Geyser streaming |
# OpenClaw (via ClawHub)
npx clawhub install slv-validator
# Claude Code — copy skill into your project
cp -r dist/oss-skills/slv-validator /your/project/.claude/skills/
# Any agent — add SKILL.md to your agent's context
cp dist/oss-skills/slv-validator/SKILL.md /your/project/AGENTS.md
Each skill includes SKILL.md (AI knowledge), Ansible playbooks, setup scripts, and example inventories. No lock-in — they're plain Markdown + Ansible.
Using Without AI (Direct Ansible)
cd dist/oss-skills/slv-validator/ansible/
# Deploy a mainnet Jito validator
ansible-playbook -i inventory.yml mainnet-validator/init.yml \
-e '{"validator_type":"jito","solana_version":"v3.1.8-jito"}'
# Restart a validator
ansible-playbook -i inventory.yml mainnet-validator/restart_node.yml
# Build Solana from source
ansible-playbook -i inventory.yml cmn/build_solana.yml \
-e '{"solana_version":"v3.1.8"}'
ERPC Network Benefits
Servers from erpc.global automatically get:
- Dedicated snapshot endpoints — 7 global regions
- Internal routing — lower bandwidth costs
- Auto-detection — SLV finds the nearest snapshot server via ping
Prerequisites
- ansible-core >= 2.15 (
pip install ansible-core) - SSH access to target servers (key-based auth)
- solana-cli (optional, for local key generation)
slv onboard handles most of this automatically.
For Developers
git clone https://github.com/ValidatorsDAO/slv.git
deno task dev --help
deno task build
deno test -A
Community
Contributing
Bug reports and pull requests are welcome. This project follows the Contributor Covenant code of conduct.
License
Files in the repo
- .claude
- .codex
- .github
- .husky
- .vscode
- ansible
- cli
- cmn
- dist
- docker
- docs
- oss-skills
- release-assets
- scripts
- sh
- slv-plugins
- template
- test-solana-key
- .gitignore
- build-skill-oss.sh
- build-skill.sh
- CODE_OF_CONDUCT.md
- deno.json
- deno.lock
- inventory.yml
- LICENSE.txt
- pr-body.md
- README.md
Discussion (0)
Ask about usage, or say what you built with itSign in to join the discussion.
No comments yet. Be the first to say what this is good for.
More tools
The best-benchmarked open-source AI memory system. And it's free.
Orca is the ADE for working with a fleet of parallel agents. Run any coding agent with your own subscription. Available on desktop, mobile and remote runtime.

A cross-platform desktop All-in-One assistant for Claude Code, Codex, OpenCode, OpenClaw, Grok Build & Hermes Agent. Only official website: ccswitch.io
Never stop coding. Free MIT AI gateway: one endpoint, 352 providers (150+ free), 1200+ models Kimi, Claude, GPT, Gemini, GLM, DeepSeek, MiniMax. Works with Claude Code, Codex, Cursor, OpenCode, Cline & Copilot. Quota-aware auto-fallback, RTK+Caveman compression saves 15-95% tokens, MCP/A2A, Desktop/PWA. Built by 550+ contributors
Compress tool outputs, logs, files, and RAG chunks before they reach the LLM. 20% fewer tokens for coding agents, 60-95% fewer tokens for JSON, same answers. Library, proxy, MCP server.