Louis Knight-Webb f631c8d6cf Editing task description to remove it doesn't work (vibe-kanban) (#862)
* Perfect! The fix is implemented and compiles successfully.

**What I fixed:**
- Replaced the simple `.or()` fallback with proper empty string handling
- Empty strings (including whitespace-only) now clear the description field
- Non-empty strings update the description as before
- Omitted fields still preserve existing values

**How it works:**
- `{"description": "new text"}` → updates description to "new text"
- `{"description": ""}` → clears description (sets to NULL)
- `{"description": "   "}` → clears description (whitespace trimmed)
- `{}` (field omitted) → keeps existing description unchanged

The fix is simple, backwards-compatible, and handles the exact issue you described without requiring API changes or type modifications.

* Cleanup script changes for task attempt 42e1596a-5b1a-4061-b704-1a30d09f8192

* Perfect! The fix is complete and both frontend and backend checks pass.

**What I fixed:**
- **Frontend**: Changed `description || null` to `description` in all 3 places (edit, create, create-and-start)
- **Backend**: Already handles empty strings as clearing (from previous fix)

**How it works now:**
- When users clear a task description, frontend sends `""` (empty string)
- Backend detects `s.trim().is_empty()` and sets description to `None` (NULL in database)
- Description gets properly cleared after saving

The simple frontend change aligns both systems perfectly. Users can now clear task descriptions by editing them to be empty and saving.

* Cleanup script changes for task attempt 42e1596a-5b1a-4061-b704-1a30d09f8192
2025-09-26 11:56:46 +01:00
2025-09-19 13:57:03 +01:00
2025-08-08 13:53:27 +01:00
2025-08-08 13:53:27 +01:00
2025-09-26 10:12:18 +00:00
2025-09-04 10:52:18 +01:00
2025-09-22 16:02:42 +01:00
2025-08-08 13:53:27 +01:00
2025-08-08 13:53:27 +01:00
2025-07-11 15:57:30 +01:00
2025-09-04 10:52:18 +01:00
2025-07-11 16:31:08 +01:00
2025-09-26 10:12:18 +00:00
2025-06-14 15:14:08 -04:00
2025-06-25 09:27:29 +01:00
2025-06-25 09:27:29 +01:00
2025-07-04 11:11:45 +02:00

Vibe Kanban Logo

Get 10X more out of Claude Code, Gemini CLI, Codex, Amp and other coding agents...

npm Build status Ask DeepWiki

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

  1. Run build-npm-package.sh
  2. In the npx-cli folder run npm pack
  3. 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:

  1. Create a GitHub OAuth App at GitHub Developer Settings
  2. Enable "Device Flow" in the app settings
  3. Set scopes to include user:email,repo
  4. Build with your client ID:
    GITHUB_CLIENT_ID=your_client_id_here pnpm run build
    
Description
Get 10X more out of Claude Code, Codex or any coding agent
https://www.vibekanban.com/
Readme Apache-2.0 48 MiB
Languages
Rust 51.1%
TypeScript 46.6%
CSS 1.1%
JavaScript 0.7%
PLpgSQL 0.2%
Other 0.2%