c6407c64ac
* ## ✅ Implementation Complete! I've successfully implemented the warning system for Claude Code when `apiKeySource` is not "/login managed key". Here's what was implemented: ### **Changes Made:** 1. **Added `api_key_source` field to `ClaudeJson::System`** - Added `#[serde(default, rename = "apiKeySource")] api_key_source: Option<String>` field - Backward-compatible with existing JSON parsing 2. **Created warning helper function** - `warn_if_unmanaged_key()` function that generates warning entries when API key source is not managed - Includes both UI warning and server-side `tracing::warn!()` logging 3. **Modified system message processing** - Updated `normalize_entries()` to check API key source and emit warnings immediately - Warning appears for any `apiKeySource` value except "/login managed key" and `None` 4. **Added comprehensive test coverage** - Test for warning generation with unmanaged keys - Test for no warning with managed keys - Test for no warning when field is missing - All existing tests pass ### **Warning Message:** ``` ⚠️ Using apiKeySource "ANTHROPIC_API_KEY" – calls will be billed to that key. Run `claude-code login` (or set `/login managed key`) if you want to route usage through the managed key. ``` ### **Key Features:** - **Immediate visibility**: Warning shows up immediately in the UI as a normalized system message - **Server-side logging**: Also logs to server with `tracing::warn!()` - **Backward compatible**: No breaking changes, works with existing implementations - **Comprehensive**: Handles all cases (managed, unmanaged, missing field) - **Actionable**: Provides clear guidance on how to fix the issue The implementation is ready for production use! * Cleanup script changes for task attempt 4345b766-b8ed-4949-aefb-32e20e891a01 * ## ✅ Review Feedback Addressed! I've successfully updated the implementation based on your review comments: ### **Changes Made:** 1. **Updated warning logic (Line 621)** - Changed from checking "not `/login managed key`" to specifically checking for `"ANTHROPIC_API_KEY"` - Now only warns when `apiKeySource` equals exactly `"ANTHROPIC_API_KEY"` - All other values (including `/login managed key`, missing field, or other keys) do not trigger warnings 2. **Updated warning message (Line 631)** - Changed from the generic billing warning to the specific message: - **New message:** `"ANTHROPIC_API_KEY env variable detected, your Anthropic subscription is not being used"` 3. **Updated tests to reflect new behavior** - Tests now verify warning only appears for `"ANTHROPIC_API_KEY"` - Tests confirm no warning for managed keys, other keys, or missing field - Validates exact warning message content ### **Final Behavior:** - ✅ **Warning shown**: When `apiKeySource` = `"ANTHROPIC_API_KEY"` - ✅ **No warning**: When `apiKeySource` = `"/login managed key"` - ✅ **No warning**: When `apiKeySource` = any other value - ✅ **No warning**: When `apiKeySource` field is missing The implementation now specifically targets the `ANTHROPIC_API_KEY` environment variable scenario and provides a clear, focused warning message about Anthropic subscription usage. * Cleanup script changes for task attempt 4345b766-b8ed-4949-aefb-32e20e891a01 * ## ✅ Warning Triangle Added! I've successfully added the warning triangle (⚠️) to the warning message as requested. ### **Final Warning Message:** ``` ⚠️ ANTHROPIC_API_KEY env variable detected, your Anthropic subscription is not being used ``` ### **Changes Made:** - **Line 628**: Added `⚠️` to the warning message content - **Updated test**: Modified the test assertion to expect the warning triangle in the message The warning now has a clear visual indicator (⚠️) that makes it more noticeable to users when the `ANTHROPIC_API_KEY` environment variable is being used instead of their Anthropic subscription through Claude Code. The implementation is complete and ready for production use!
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 frontend and backend with live reloading. A blank DB will be copied from the dev_assets_seed folder.
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