Enterprise-grade visibility and control for AI coding assistants
Viberails gives your team complete oversight of AI coding tool activity across your organization. Know what your AI assistants are doing, catch risky operations before they happen, and maintain compliance—all without slowing down your developers.
AI coding assistants like Claude Code, Cursor, and Copilot are transforming how developers work. But with great power comes great responsibility:
- What tools are your AI assistants executing? File operations, shell commands, API calls—do you know what's happening across your team?
- Are sensitive files being accessed? Configuration files, credentials, proprietary code—AI assistants can read and modify anything.
- How do you maintain compliance? Auditors want logs. Security teams want visibility. Viberails delivers both.
| Without Viberails | With Viberails |
|---|---|
| No visibility into AI tool usage | Complete audit trail of every action |
| Risky operations go unnoticed | Real-time authorization controls |
| Compliance gaps | Full audit logs for security reviews |
| Each developer is an island | Team-wide visibility and policies |
| Hope nothing goes wrong | Know exactly what's happening |
-
Multi-Tool Support - Works with the most popular AI coding assistants:
- Claude Code
- Cursor
- Gemini CLI
- OpenAI Codex CLI
- OpenCode
- OpenClaw
-
Zero Friction Setup - Install in under 2 minutes with automatic tool detection
-
Team Collaboration - One person sets up the team, everyone else joins with a single command
-
Privacy Controls - Choose what gets sent to the cloud:
- Full audit (tool calls + prompts)
- Tool authorization only (no prompts)
- Fully local operation
-
Fail-Safe Design - Configurable fail-open/fail-closed behavior ensures developers aren't blocked
macOS/Linux:
bash <(curl -fsSL https://get.viberails.io/install.sh)Windows (PowerShell):
irm https://get.viberails.io/install.ps1 | iexSecurity Note: We get it - piping curl to bash requires trust. You can review the install script before running, or download binaries directly:
Verify checksums via release.json.
This downloads Viberails and launches the interactive setup. You'll be prompted to:
- Select an OAuth provider (Google, Microsoft, or GitHub)
- Enter your team name
- Complete authentication in your browser
To use an existing LimaCharlie organization, run:
viberails init-team --existing-org <OID>viberails installViberails automatically detects which AI tools you have installed and lets you choose which ones to hook:
? Select AI coding tools to install hooks for:
[x] Claude Code [detected]
[x] Cursor [detected]
[ ] Gemini CLI [not found]
[ ] OpenAI Codex CLI [not found]
After setup, you'll receive a command to share with your colleagues. They can join with a single command:
macOS/Linux:
bash <(curl -fsSL https://get.viberails.io/install.sh) join-team <YOUR_TEAM_URL>Windows (PowerShell):
$u="<YOUR_TEAM_URL>"; irm https://get.viberails.io/join.ps1 | iexThat's it! Your team now has complete visibility into AI coding assistant activity.
viberails show-configThis displays your current configuration including:
- Fail Open - Whether tools are approved locally when cloud is unreachable (default: true)
- Audit Tool Use - Send tool calls to cloud for authorization (default: true)
- Audit Prompts - Send prompts/chat to cloud for audit logging (default: true)
- Organization - Your team name and webhook URL
Configuration can be modified by editing ~/.config/viberails/config.json.
| Command | Alias | Description |
|---|---|---|
init-team |
init |
Create a new team via OAuth |
join-team <URL> |
join |
Join an existing team |
install |
Install hooks for detected AI tools | |
uninstall |
Remove hooks and optionally the binary | |
list |
ls |
Show installed hooks |
show-config |
Display current configuration | |
upgrade |
Update to the latest version | |
debug |
Enable/disable debug logging | |
debug-clean |
clean-debug |
Remove accumulated debug logs |
Run viberails --help for detailed usage information.
If hooks aren't working as expected, enable debug mode to capture detailed logs:
# Enable debug logging
viberails debug
# Use your AI coding tool - detailed logs will be captured
# ...
# View the logs
ls ~/.local/share/viberails/debug/
cat ~/.local/share/viberails/debug/debug-*.log
# Clean up logs when done (they accumulate over time)
viberails debug-clean
# Disable debug mode
viberails debug --disableDebug logs include:
- Full payload data from AI tools
- Hook invocation details
- Cloud API request/response information
- Tool use vs prompt classification decisions
Note: Debug logs may contain sensitive information. Use only for troubleshooting and disable when done.
Hooks not triggering:
- Run
viberails listto verify hooks are installed - Enable debug mode and check if logs are created when using the AI tool
- Check the regular log at
~/.local/share/viberails/viberails.log
Events not reaching LimaCharlie:
- Enable debug mode to see cloud API responses
- Verify your team URL with
viberails show-config - Check if
audit_tool_useandaudit_promptsare enabled
Viberails is powered by LimaCharlie, a security infrastructure platform trusted by enterprises worldwide. This gives you:
- Enterprise-grade reliability - Built on battle-tested security infrastructure
- Scalability - From small teams to large organizations
- Security - Your data is handled with the same care as enterprise security telemetry
- Extensibility - Integrate with your existing security tools and workflows
┌─────────────────────────────────────────────────────────────┐
│ AI Coding Tool (Claude Code, Cursor, etc.) │
└────────────────────────┬────────────────────────────────────┘
│ Hook triggers on tool use
▼
┌─────────────────────────────────────────────────────────────┐
│ Viberails Hook │
│ • Captures tool call details │
│ • Sends to cloud for authorization │
│ • Returns allow/deny decision │
└────────────────────────┬────────────────────────────────────┘
│
▼
┌─────────────────────────────────────────────────────────────┐
│ LimaCharlie Backend │
│ • Stores audit logs │
│ • Evaluates authorization policies │
│ • Provides team-wide visibility │
└─────────────────────────────────────────────────────────────┘
Access your team's dashboard at app.viberails.io:
- Real-time Activity Feed - Watch AI tool usage across your team as it happens
- Policy Management - Define rules for what tools can and cannot do
- Analytics & Reporting - Understand AI tool usage patterns
- Alerts - Get notified when sensitive operations occur
- Compliance Reports - Generate audit reports with one click
# Clone the repository
git clone https://github.com/refractionPOINT/viberails.git
cd viberails
# Build
cargo build --release
# Run
./target/release/viberails --help- Windows, macOS, or Linux
- One or more supported AI coding tools installed
- Internet connection for team features
The binary is installed to ~/.local/bin/viberails. If this directory isn't in your PATH, add it:
# Add to ~/.bashrc or ~/.zshrc
export PATH="$HOME/.local/bin:$PATH"We welcome contributions! Before submitting code:
cargo clippy -- -D warnings # No warnings allowed
cargo test # All tests must passThese checks are enforced by pre-commit hooks.
- Issues: GitHub Issues
- Documentation: docs.viberails.io (coming soon)
- Community: Discord (coming soon)
Viberails is licensed under the Apache License 2.0.
Built with security in mind by Refraction Point, the team behind LimaCharlie.