40615190cd
* Perfect! The implementation is now complete and working correctly. ✅ **Successfully implemented the requested feature** The CI check for `npm run generate-types` now validates **all** generated files, not just `shared/types.ts`. 1. **Enhanced `crates/server/src/bin/generate_types.rs`**: - Added `generate_schema_content<T>()` helper function to generate schema content in-memory - Added `check_schemas()` function that validates all 7 JSON schema files - Updated the `--check` mode to validate both TypeScript types AND schema files 2. **Comprehensive validation**: - Checks `shared/types.ts` (existing functionality) - Checks all schema files: `amp.json`, `claude_code.json`, `codex.json`, `cursor.json`, `gemini.json`, `opencode.json`, `qwen_code.json` 3. **Clear error reporting**: - Shows exactly which files are outdated - Provides actionable error message: "Please run 'npm run generate-types' and commit the changes." - ✅ Passes when all files are up to date - ❌ Fails with exit code 1 when any file (types or schemas) is outdated - ✅ CI integration already in place (`.github/workflows/test.yml:66`) The CI will now catch any case where developers modify Rust types that affect either TypeScript generation or JSON schema generation without running `npm run generate-types` and committing all resulting changes. ✅ **Successfully restored the lost cursor schema descriptions!** 1. **Added proper schemars attributes** to `crates/executors/src/executors/cursor.rs`: - `force` field: `#[schemars(description = "Force allow commands unless explicitly denied")]` - `model` field: `#[schemars(description = "auto, sonnet-4, gpt-5, opus-4.1, grok")]` 2. **Regenerated schema files** using `npm run generate-types` 3. **Verified the fix** - `shared/schemas/cursor.json` now contains the proper descriptions: - Line 15: `"description": "Force allow commands unless explicitly denied"` - Line 22: `"description": "auto, sonnet-4, gpt-5, opus-4.1, grok"` - **Source-controlled**: Descriptions are now defined in Rust source code instead of auto-generated files - **Future-proof**: Future schema regenerations will automatically include these descriptions - **Proper architecture**: Follows the intended pattern of defining schema metadata in the source code - **CI compatible**: The enhanced CI check will ensure these descriptions are preserved The schema descriptions that were accidentally lost in the last commit have been properly restored to the correct location in the source code. * clippy * remove macro * Surface error, remove unneede vec!
Get 10X more out of Claude Code, Gemini CLI, Codex, Amp and other coding agents...
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
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
Please open an issue on this repo if you find any bugs or have any feature requests.
Contributing
We would prefer that ideas and changes are raised with the core team via GitHub issues, 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 |
|---|---|---|---|
GITHUB_CLIENT_ID |
Build-time | Ov23li9bxz3kKfPOIsGm |
GitHub OAuth app client ID for authentication |
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.
Custom GitHub OAuth App (Optional)
By default, Vibe Kanban uses Bloop AI's GitHub OAuth app for authentication. To use your own GitHub app for self-hosting or custom branding:
- Create a GitHub OAuth App at GitHub Developer Settings
- Enable "Device Flow" in the app settings
- Set scopes to include
user:email,repo - Build with your client ID:
GITHUB_CLIENT_ID=your_client_id_here pnpm run build