vibes

The vibe engineering mech suit.

vibes augments you—the human developer—with AI-powered superpowers: remote session control, persistent context, and a learning system that remembers what works. You stay in command; vibes amplifies your reach.

Getting Started

• Features — What vibes does
• Quick Start — Install and run
• Usage — CLI commands and examples
• Documentation — Architecture, plugins, and roadmap
• Glossary — Key terms explained

Features

• Remote Access — Control Claude Code sessions from your phone, tablet, or any device via web UI
• Session Mirroring — Real-time sync between your terminal and remote devices
• Plugin System — Extend vibes with native Rust plugins for custom commands and workflows
• Continual Learning — groove learns your patterns and preferences across sessions
• Cross-Platform — Single binary for Linux, macOS, and Windows

Quick Start

# Clone with submodules
git clone --recursive https://github.com/run-vibes/vibes
cd vibes

# Enter dev environment (requires Nix)
direnv allow

# Build (release)
just build-release

# Run
./target/release/vibes claude

# Or for development (debug build)
just build
cargo run -p vibes-cli -- claude

Persistent event storage is automatic—no additional setup required.

Linux: io_uring Requirement

On Linux, the event storage system (Iggy) uses io_uring for high-performance async I/O. This requires sufficient locked memory:

# Check current limit
ulimit -l

# If less than 64 MB, increase it:
ulimit -l unlimited

For persistent configuration, add to /etc/security/limits.conf:

* soft memlock unlimited
* hard memlock unlimited

If the limit is insufficient, vibes will display a helpful error message and refuse to start until the system is configured correctly.

Usage

# Use like claude, but with superpowers
vibes claude "refactor the auth module"

# All claude flags work
vibes claude -c                          # Continue last session
vibes claude --model claude-opus-4-5     # Model override
vibes claude --system-prompt "Be terse"  # Custom system prompt

# Vibes additions
vibes claude --session-name "auth-work"  # Human-friendly session names
vibes claude --no-serve                  # Disable background server

# Configuration
vibes config show                        # Display merged configuration
vibes config path                        # Show config file locations

# Access from any device on your network
# Web UI available at http://localhost:7432

Testing

# Unit + integration tests (recommended for development)
just test

# All tests including those requiring Claude CLI
just test-all

# E2E browser tests (requires Playwright installed)
just test-e2e

# Pre-commit checks (fmt, clippy, test)
just pre-commit

Documentation

• Architecture — System design, event flow, and component overview
• Plugins — Plugin system and in-tree plugins (including groove)
• Roadmap — Development phases and milestone tracking
• Product Requirements — Full design specifications
• Planning Board — Kanban board tracking implementation status
• Planning Conventions — How to create design and implementation plans
• CLAUDE.md — Development guidance for contributors
• Glossary — Key terms explained

License

MIT License — see LICENSE for details.