85f6ee5237
* fix: skip watching heavy directories to avoid memory leak * fix: reduce memory usage in filesystem watcher for pnpm projects Use gitignore-aware directory collection to prevent OS-level watchers from being set up on heavy directories like node_modules. Changes: - Use WalkBuilder's git_ignore(true) to respect .gitignore when collecting watch directories - Use NonRecursive watch mode for each directory instead of single Recursive watch - Simplify ALWAYS_SKIP_DIRS to only contain .git (not in .gitignore but should be skipped) This fixes high memory usage when running vibe-kanban on pnpm-managed repositories, which contain many symlinks in node_modules. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> * fix: simplify filesystem watcher error handling and fix clippy warnings - Remove debug logs that were added during development - Fail fast on watch errors instead of continuing in a partially broken state - Collapse nested if statements to satisfy clippy::collapsible_if 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> * fix: check only parent directories in path_allowed Only check parent directory names against ALWAYS_SKIP_DIRS since should_skip_dir is meant for directories, not file names. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> * fix: add watch directories changes * Stop leaking filesystem watcher Use weak references so the background thread exits once the diff stream releases the debouncer. * Memoize ignored-descendant scan Cache per-directory results so collecting watch targets stays linear. * Improve watcher gitignore classification Use real metadata when available, fall back to the old heuristic only when the file is already gone, and document the limitation. * Handle directory renames in watcher * Deduplicate watch directories more efficiently Sort once and do a single sweep instead of quadratic filtering. * Document gitignore watcher limitation * Cascade watcher removal on directory delete Drop all descendant watchers when a parent directory disappears so stale handles don’t linger. * Watch subdirectories when new directories are added Track recursive parent watchers so we skip redundant child watches and prune them when a parent becomes recursive. * Always ignore node_modules * Use a high-performance line count diff implementation The `similar` diff stat implementation was causing cpu spikes of up to 600% over 10 seconds. * exclude node_modules from git diff commands --------- Co-authored-by: Claude <noreply@anthropic.com> Co-authored-by: Solomon <abcpro11051@disroot.org>
Get 10X more out of Claude Code, Gemini CLI, Codex, Amp and other coding agents...
We're hiring!
Overview
AI coding agents are increasingly writing the world's code and human engineers now spend the majority of their time planning, reviewing, and orchestrating tasks. Vibe Kanban streamlines this process, enabling you to:
- Easily switch between different coding agents
- Orchestrate the execution of multiple coding agents in parallel or in sequence
- Quickly review work and start dev servers
- Track the status of tasks that your coding agents are working on
- Centralise configuration of coding agent MCP configs
- Open projects remotely via SSH when running Vibe Kanban on a remote server
You can watch a video overview here.
Installation
Make sure you have authenticated with your favourite coding agent. A full list of supported coding agents can be found in the docs. Then in your terminal run:
npx vibe-kanban
Documentation
Please head to the website for the latest documentation and user guides.
Support
We use GitHub Discussions for feature requests. Please open a discussion to create a feature request. For bugs please open an issue on this repo.
Contributing
We would prefer that ideas and changes are first raised with the core team via GitHub Discussions or Discord, where we can discuss implementation details and alignment with the existing roadmap. Please do not open PRs without first discussing your proposal with the team.
Development
Prerequisites
Additional development tools:
cargo install cargo-watch
cargo install sqlx-cli
Install dependencies:
pnpm i
Running the dev server
pnpm run dev
This will start the backend. A blank DB will be copied from the dev_assets_seed folder.
Building the frontend
To build just the frontend:
cd frontend
pnpm build
Build from source
- Run
build-npm-package.sh - In the
npx-clifolder runnpm pack - You can run your build with
npx [GENERATED FILE].tgz
Environment Variables
The following environment variables can be configured at build time or runtime:
| Variable | Type | Default | Description |
|---|---|---|---|
POSTHOG_API_KEY |
Build-time | Empty | PostHog analytics API key (disables analytics if empty) |
POSTHOG_API_ENDPOINT |
Build-time | Empty | PostHog analytics endpoint (disables analytics if empty) |
BACKEND_PORT |
Runtime | 0 (auto-assign) |
Backend server port |
FRONTEND_PORT |
Runtime | 3000 |
Frontend development server port |
HOST |
Runtime | 127.0.0.1 |
Backend server host |
DISABLE_WORKTREE_ORPHAN_CLEANUP |
Runtime | Not set | Disable git worktree cleanup (for debugging) |
Build-time variables must be set when running pnpm run build. Runtime variables are read when the application starts.
Remote Deployment
When running Vibe Kanban on a remote server (e.g., via systemctl, Docker, or cloud hosting), you can configure your editor to open projects via SSH:
- Access via tunnel: Use Cloudflare Tunnel, ngrok, or similar to expose the web UI
- Configure remote SSH in Settings → Editor Integration:
- Set Remote SSH Host to your server hostname or IP
- Set Remote SSH User to your SSH username (optional)
- Prerequisites:
- SSH access from your local machine to the remote server
- SSH keys configured (passwordless authentication)
- VSCode Remote-SSH extension
When configured, the "Open in VSCode" buttons will generate URLs like vscode://vscode-remote/ssh-remote+user@host/path that open your local editor and connect to the remote server.
See the documentation for detailed setup instructions.