Our take
- Activity
- 19
- Community
- 31
- Issues
- 21
- Pull requests
- 20
-3 stars in the last 30 days
Project history
Daily GitHub snapshots since Oct 7, 2026. History covers stars and forks; health signals are not tracked historically.
Stars
4,817Forks
239Change since Nov 17, 2026: +1 stars·0 forks
Overview
vibe-tools is a globally installed CLI that gives AI coding agents additional tools and specialist AI assistance. It is designed for Cursor Composer, but its installer also supports instruction setup for Claude Code, Codex, Windsurf, Cline, and Roo, as well as other agents that can run commands.
The project addresses a common gap in coding-agent workflows: an agent may need current web research, broad repository context, browser interaction, or issue and documentation access in addition to local code editing. vibe-tools exposes these capabilities through commands and agent instructions. It is most useful when you want your agent to call purpose-built tools rather than handle each task through a single model conversation.
Key Features
- Web research through the
webcommand, using Perplexity. - Repository questions, reviews, and planning with codebase context assembled using Repomix.
- Browser automation for opening pages, observing elements, performing actions, and extracting content through Stagehand and Playwright.
- Direct model queries and configurable providers, including Gemini, OpenAI, Anthropic, Perplexity, OpenRouter, and others.
- Integrations for GitHub issues and pull requests, Linear issues, and Xcode build, run, and lint tasks.
- Documentation generation for local or GitHub repositories, with optional external documents as context.
- YouTube video analysis for summaries, transcripts, questions, and implementation plans.
- An installer that configures agent instruction files and supports interactive and CI-oriented setup.
Use Cases
- A developer using a coding agent can ask for a repository-aware explanation or review when local context alone is insufficient.
- An agent-driven team can research current APIs and library behavior before implementing changes that depend on external information.
- Web developers can automate browser checks, inspect console or network activity, and capture screenshots while debugging or testing.
- Developers handling issues across GitHub or Linear can bring issue descriptions and discussion context into their agent workflow.
- Teams maintaining unfamiliar dependencies can generate local documentation from external repositories for agent reference.
Getting Started
Requires Node.js 18 or later. Install globally and run the setup in your project:
npm install -g vibe-tools
vibe-tools install .
The README covers provider keys, configuration, commands, and integrations. Perplexity and Google Gemini API keys are listed as requirements; browser actions also need an OpenAI or Anthropic key.
Considerations
- Many capabilities rely on third-party model APIs and their credentials, so availability and usage costs depend on the configured providers.
- The README lists Perplexity and Gemini keys as requirements, while some additional commands require their own provider keys. Check the setup and command-specific requirements before adopting it.
- Browser automation installs Playwright's Chromium browser during setup, and Stagehand actions require a supported model provider.
- Repository analysis and documentation send repository content as model context. The README describes
.repomixignoreand Repomix configuration for controlling included files. - The project collects anonymous usage telemetry. The README says users can opt out with
VIBE_TOOLS_NO_TELEMETRY=1; review its telemetry documentation if this matters to your environment.
Found this useful?
Share it with someone who would like vibe-tools.