vibe

command module
v0.0.4 Latest Latest
Warning

This package is not in the latest version of its module.

Go to latest
Published: Mar 13, 2026 License: MIT Imports: 1 Imported by: 0

README


AI-powered task runner driven by plain-English recipes. An MVP implementation of the Vibefile spec.

Install

Download the CLI:

curl -sSL https://get.vibefile.dev | bash

Or build from source:

git clone https://github.com/vibefile-dev/vibe.git
cd vibe
go build -o vibe .

Quick start

Create a Vibefile in your project root or try vibe init to generate one for you:

model = claude-sonnet-4-6
env = production

build:
    "compile and bundle the project for $(env)"

test:
    "run the test suite"

deploy: test build:
    "deploy to $(env) on fly.io"

Set your API key:

export ANTHROPIC_API_KEY=sk-ant-...

Run a target:

vibe run build

Commands

Command Description
vibe run <target> Run a target and its dependencies
vibe run <target> --dry Show generated script without executing
vibe run <target> --recompile Force LLM regeneration for this target
vibe run <target> --recompile-all Force LLM regeneration for target + all deps
vibe list List all targets with descriptions
vibe check Validate the Vibefile syntax
vibe status Show compiled/uncompiled state of all targets

Compiled target caching

The first time a codegen target runs, the LLM-generated script is saved to .vibe/compiled/<target>.sh with a .lock file tracking the inputs. Subsequent runs skip the LLM entirely — no latency, no API cost.

The cache is invalidated automatically when any input changes:

  • Recipe text edited in the Vibefile
  • Variable values changed
  • Relevant context files changed (e.g. package.json, go.mod)
  • Model version changed
first run                          subsequent runs
──────────────────────────────     ───────────────────────────
vibe run build                     vibe run build
  → collect context                  → load .vibe/compiled/build.sh
  → call LLM API        (cost)      → run script              (free)
  → save .vibe/compiled/build.sh
  → run script

The .vibe/compiled/ directory should be committed to version control so the team shares compiled targets.

API key resolution

Keys are resolved in this order:

  1. --api-key CLI flag
  2. VIBE_API_KEY environment variable
  3. Provider-specific env var (e.g. ANTHROPIC_API_KEY, OPENAI_API_KEY)
  4. ~/.vibeconfig file
# ~/.vibeconfig
default_model: claude-sonnet-4-6
anthropic_key: sk-ant-...
openai_key: sk-...

Documentation

The Go Gopher

There is no documentation for this package.

Jump to

Keyboard shortcuts

? : This menu
/ : Search site
f or F : Jump to
y or Y : Canonical URL