Skip to content
kandown
GitHubnpm
98 releases

Changelog

2026-07-21

v0.33.3CLI Recovery

  • Fixed: Default kandown Launch Regression — restored the pre-split zero-setup startup flow where running kandown inside any project automatically initializes .kandown/ when needed, refreshes the web bundle, starts the per-project daemon, and enters the normal board launch path.
  • Fixed: Global Flag Command Parsing — repaired CLI dispatch so global flags such as --no-update-check, --no-open, --path, and --port no longer get mistaken for commands. This fixes the auto-updater restart path and the daemon spawn path that launches --no-update-check daemon run internally.
  • Fixed: Missing init Command After Modularization — restored kandown init by adding the initializer module back to the source tree, copying the shipped HTML/config/agent templates, and creating project-root tasks/ exactly as documented.
  • Fixed: One-Shot Task Commands — restored the scriptable task command surface that had been partially lost during the split: kandown list, show, create/new, move, assign, commit, and tasks. JSON output and command-substitution output are clean again because decorative messages are emitted on stderr.
  • Fixed: Daemon Command Surface — restored kandown daemon start, status, restart, stop, run, and refresh-all handling, including preferred port parsing for explicit daemon runs.
  • Fixed: TUI Command Entrypoints — restored kandown board and kandown settings, and made the bundled bin/tui.js executable directly so the parent CLI can spawn the terminal interface reliably.
  • Fixed: MCP Stdout Contract — restored kandown mcp dispatch while keeping stdout JSON-only, with initialization and status notices sent to stderr so MCP hosts and shell pipelines can parse responses safely.
  • Fixed: Unsafe Global Symlink Rewrites — removed the daemon-side behavior that attempted to rewrite global kandown symlinks from a bundle-relative path. Package managers now remain the source of truth for the executable, preventing the web daemon from bricking the command.
  • Fixed: Project HTML Refresh Path Resolution — refreshed .kandown/kandown.html from the resolved package root instead of an incorrect import.meta.url relative path, ensuring project web bundles are updated from the installed package.
  • Changed: Auto-Updater Global Install Targeting — hardened the auto-updater to prefer the npm/pnpm executable living next to the active kandown binary. This prevents machines with multiple Node prefixes from updating a different global install than the command the user actually launched.
  • Added: Basic Import Recovery Command — restored kandown import <file.json> for list-shaped JSON and Kandown export-shaped JSON, allowing task files to be recreated from exported data during CLI recovery workflows.