vibevote
v0.1.0
Published
Play Vibe Vote in your terminal: a one-tap would-you-rather in the dead air while your AI agent works.
Maintainers
Readme
vibevote (CLI)
A would-you-rather in your AI's dead air. Run it in a split terminal pane next to Claude Code or Codex: while your agent works, tap one key to vote on the spiciest takes in sports, reality TV, music, and movies, and see how vibe coders really voted. vibevote.ai
npx vibevoteNo sign-up needed to start (anonymous by default). Works alongside any agent.
Usage
vibevote Play. With the Vibe Vote Claude Code plugin installed, a
question only appears while your agent is actually working.
vibevote --solo Ignore the agent gate, play freely anytime.
vibevote --smoke Non-interactive self-test: cast one vote, print JSON, exit.
vibevote --helpKeys: A/B (or ←/→) to vote, space for the next one, q to quit.
Env: VIBEVOTE_API overrides the API base (default https://api.vibevote.ai; set
http://localhost:8000 for local dev).
Dead-air gating (with the Claude Code plugin)
The Vibe Vote Claude Code plugin writes the agent's
working/idle state to ~/.vibevote/agent-state.json via hooks. This CLI watches
that file and only surfaces a vote while the agent is working, standing down
when it needs you. Without the plugin, the CLI just plays freely.
How it works
- Anonymous identity, server-issued, solving Proof-of-Work when the backend
requires it (same scheme as the web/extension). Stored in
~/.vibevote/config.json. - One tap is your vote (no predict step). The reveal shows the crowd split blended with a seeded estimate so "you're with X% of vibe coders" reads sensibly from vote one, plus your XP and streak.
- Observe-only: talks only to the Vibe Vote backend. It never reads or touches your agent's model traffic, tokens, auth, or output.
Develop
node src/index.mjs --help
node src/index.mjs --smoke # against VIBEVOTE_API
node test/smoke.mjs # self-contained smoke (starts a stub server)Dependency-free Node (>= 18), ES modules.
