Tokens saved 0 0 0 0 0 0 0 0 0

Vibe Rails

An opinionated framework that keeps vibe coding from going off the rails

Run the install command for your platform
Windows
irm https://raw.githubusercontent.com/robstokes857/vibe-rails/main/Scripts/install.ps1 | iex
Linux
wget -qO- https://raw.githubusercontent.com/robstokes857/vibe-rails/main/Scripts/install.sh | bash
Mac
curl -fsSL https://raw.githubusercontent.com/robstokes857/vibe-rails/main/Scripts/install.sh | bash
GitHub
github.com/robstokes857/vibe-rails
Works with your stack

Multiple LLMs and Code Editors

Claude

Codex

Deepseek

Z.AI

Grok

Kimi

Copilot

AntiGravity

OpenCode

VS Code

Tokens Saved

tokens

Credit where it's due: we got this idea from rtk

Stay on track

Key Features

Make Your AI Budget Go Further

Reduce token overhead by compressing supported tool output before it reaches the model. Smaller requests can lower costs and leave more room for useful context.

  • Reduce repeated lines and unnecessary formatting
  • Condense supported command output before it is sent
  • Tune compression settings for your workflow
  • Review the results as you adjust token usage
Tokens
Smaller requests
Budget
Potential cost savings
Context
Less repetitive output
Tool output compression examples
Repeated lines Condense repeated output Reduce
Formatting Trim excess whitespace Reduce
Test output Summarize passing test lines Reduce
Savings vary with model, workload and settings. Provider pricing and repeat requests affect the final cost.

Review the Work Behind the Code

Understand how AI-assisted changes were made. Follow recorded sessions from the request to the result, with evidence your team can inspect.

  • Read captured prompts alongside saved code changes
  • Replay recorded terminal activity and inspect logs
  • Download available session data for further review
  • Support handoffs, audits and compliance reviews with evidence
Session evidence when captured
prompts Requests that guided the work Context
changes File diffs saved with the session Review
playback Recorded terminal activity and logs Replay
Evidence depends on what the session captured. Hosted session history is currently in limited preview.

Make Quality Checks Repeatable

Give AI-assisted work a consistent review process. Combine project rules, scripts and agent reviews so developers can inspect the results before accepting changes.

  • Define project rules with WARN, COMMIT or STOP levels
  • Reuse scripts and agent reviews in Automations
  • Inspect test output, code changes and review findings
  • Keep developers in control of what gets accepted
viberails: example review workflow
$ git diff --stat
Inspect the scope of the changes
$ dotnet test
Read test results and investigate failures
Review Check changes against project rules
Assess findings before accepting the work
---
A repeatable process, with a developer in control.

Keep Your Team Moving

Keep context close, reuse your setup and stay connected to the work.

Clearer Team Handoffs

Keep the task and its history together so the next developer or agent has a useful starting point.

  • Organize work on a board with clear tasks and status.
  • Keep decisions and progress in card comments.
  • Link commits and recorded sessions to the task.

Less time reconstructing what happened. More context for the next step.

Reusable Developer Environments

Keep familiar coding tools and reuse the settings that work for your projects.

  • Save prompts, arguments and tool settings in profiles.
  • Keep environment configurations separate.
  • Reuse proven profiles across tasks and projects.

Spend less time repeating setup and more time on the work.

Remote Terminal Access

Check in on a running coding session from your browser, even when you are away from your desk.

  • Sign in and connect to your active terminal.
  • Follow progress from your phone, tablet or desktop.
  • Use the interactive terminal to steer the work.

Stay connected when a session needs your attention.