v0.18.0

New features

• Request attention on an issue with kata notify and read requests with kata inbox. Clear requests after handling them. Closed issues leave the inbox, and reopening restores uncleared requests.
• Attribute issues, comments, and attention requests to teammates, temporary participants who share an existing account. Set KATA_TEAMMATE or use --teammate, and address requests to actor/teammate. Upgrade all participating daemons before relying on federation to preserve attribution.
• Delegate an issue and its descendants with expiring credentials through the CLI or MCP. Recipients can read and complete delegated work and create children without unrestricted daemon access. The TUI and web credential audit show scope, expiry, revocation, and recorded use.
• Find open work grouped by author and teammate in the web app's new Delegated view.
• Receive an inbox notification when an issue reaches its scheduled date or deadline. Kata notifies the owner or author, preserves manual requests, and avoids repeating acknowledged notices.
• Search only open or closed issues with kata search --status open or --status closed. HTTP and MCP searches accept the same filter. Status-filtered CLI and MCP requests require daemon API 0.19.0.
• List the oldest issues first with kata list --sort oldest, including across projects with --all. Sorting happens before --limit, and human-readable output uses a flat list to preserve chronology.
• Connect federated projects through an operator-supplied credential helper without manually copying federation tokens. Connections support read-only replicas, collaboration, and explicit migration, with approval and expiry information in status.
• Discover running HTTP MCP listeners with kata mcp status --json, including their ports, backend targets, and token-file paths. Use kata mcp serve --runtime-dir to select an already running daemon.

Improvements

• Open issues in the browser using links included in show, list, ready, and search results. CLI JSON exposes web_url, and MCP includes links in issue summaries. API-only instances omit them.
• Identify existing issues directly from create-conflict errors. CLI JSON includes the error details, and agent output includes the matching issue references.
• Skip the TUI quit confirmation by setting confirm_quit = false under [tui]. Confirmation remains enabled by default.

Bug fixes

• Keep the local daemon and web UI current after kata update. The updater restarts a running daemon that supports automatic restart and preserves its settings. Older daemons prompt for a manual kata daemon restart.
• Use Kata's MCP tools with the Anthropic Messages API without rejection for unsupported top-level schema combinations.
• Read issue titles while editing in narrow web panes. The editor places the title above the actions when the pane is narrower than 640 pixels.
• Follow destructive-command confirmation help without a rejected value. The help now shows the required project-qualified issue ID.
• Avoid connector readiness failures on Windows when a temporary file-sharing violation occurs. Kata retries those reads.

v0.17.2

Bug fixes

• Commands such as kata tui no longer fail during daemon upgrades or later startup when the operating system reuses an old daemon's process ID for another process.

v0.17.1

Bug fixes

• Restore the complete release downloads, including Homebrew archives, Debian and RPM packages, and a source archive with the dependencies and web assets needed to build Kata offline.

This release contains the same application code as 0.17.0. It repairs release packaging and includes the finalized 0.17.0 documentation.

v0.17.0

New features

• Check issue ownership with kata status <ref>. It reports the issue's status and revision, your effective identity, the owner, and whether a federation write lease, which reserves an issue for a holder, is active, expired, or pending.
• Extend a timed federation lease without releasing it first with kata federation lease renew <issue-ref> --ttl <duration>. Renewal accepts durations from 60 seconds to 24 hours.
• Claim an issue only if nobody owns it with kata claim --if-unowned. Use kata unassign --expect-owner <owner> to remove an assignment only if the owner still matches.
• Retry an issue close after a lost response with kata close --idempotency-key. Reusing the key for the same request returns the original result and avoids duplicate follow-up comments. Add --if-match to reject the close if the issue has changed.
• Mount the browser application below a URL path when embedding Kata. Navigation, API requests, sessions, live updates, and assets stay under the selected path.
• Grant database-backed identity tokens permission to administer connectors and links to external issues with allow_identity_connector_administration = true alongside require_token_identity = true. This setting defaults to off and grants every active identity token that permission across the daemon.

Improvements

• Start CLI commands with less delay. In a 200-run cold-start comparison, median time for a validation command falls from 19.8 ms to 8.9 ms.
• Send simple remote create, edit, comment, and label add commands with one HTTP request instead of three. Upgrade the remote daemon alongside the CLI because older daemons reject the new project selectors. Commands involving relationships still require a separate project lookup.
• Read more context in kata search --agent results, including owner, priority, revision, and a body excerpt. Agent output for list and show also includes the revision needed for --if-match writes.
• Receive empty JSON arrays and objects instead of null collections in API responses. Requests now require case-sensitive field names and reject null for arrays. Update custom clients that rely on the previous behavior.
• Find a new step-by-step guide at /guide/ on katatracker.com and reference documentation under /docs/. Existing documentation URLs redirect to their new locations.

Bug fixes

• Keep audit history from before an issue move during SQLite upgrades and project-filtered legacy exports. Unexplained missing events stop the upgrade and leave the original database unchanged. This fix does not restore history lost during an earlier upgrade.
• Preserve original issue, comment, and relationship authors when adding an existing project to federation across multiple batches, including resumed transfers.
• Preserve relationship creation dates in new federation snapshots and subsequent rebuilds on SQLite and PostgreSQL. Older snapshots without dates retain their existing behavior.
• Avoid delaying unrelated PostgreSQL writes by skipping unchanged comments during federation rebuilds.
• Recognize uncertain issue creation results after timeouts, cancellations, dropped connections, or truncated responses as create_outcome_unknown. Check whether the issue exists before retrying, and use --force-new only after confirming that no issue was created.
• Limit similar-issue checks to the first 500 Unicode code points of the title and body, avoiding oversized queries for long issues.
• Keep comment retries working after an issue moves between projects. Comment idempotency keys now belong to individual issues.

v0.16.0

New Features

• Add external root bridges across the daemon, CLI, and MCP.
• Add a connector protocol SDK and conformance kit.
• Support external evidence when completing issues.
• Add per-project merge imports.
• Automatically shut down idle, auto-started daemons.

Improvements

• Cap embedding batches by token budget.
• Improve CLI wait behavior and output state reporting.
• Preserve daemon credential provenance.
• Make JSON schemas and federation lease aliases self-describing.
• Standardize web actions on Kit UI components.

Bug Fixes

• Restore local web UI access and improve narrow-screen layouts.

v0.15.1

Release 0.15.1

• Adds Streamable HTTP transport for MCP clients.

• Daemon discovery reports whether discovered daemons are supported.

• CLI errors clearly explain when restricted environments prevent daemon autostart.

• Prevents remote TUI clients from bypassing daemon close safeguards.

• Improves runtime-store writability detection.

v0.15.0

Release 0.15.0

• Expands native MCP support across issues, projects, activity, recurrences, federation, synchronization, imports, tokens, and storage.

• Adds due-date management to CLI and MCP workflows.

• Adds a contract output mode for agent guidance and hooks.

• Adds the conventional kata --version flag.

• Allows trusted local web sessions when embedded browsers omit the Origin header.

• Lets legacy federation bindings rebind cleanly.

• Improves SQLite fast-mode performance by eliminating durability flushes.

• Reports clear errors when the local daemon is unreachable.

v0.14.3

Release 0.14.3

• Lets Forge reuse Kata’s issue details, including properties, checklists, links, and comments.

• Ensures release artifacts use the requested release tag.

• Restores login discovery for web UI tabs opened directly.

v0.14.2

Release 0.14.2

• Add Homebrew installation support.

• Support importing issues from SQLite-era Beads databases.

• Preserve TUI new-issue drafts by confirming before discarding them.

• Correct scheduled_on timezone handling and civil-time semantics.

v0.14.2-rc.2

Release 0.14.2-rc.2

• Import issue data from SQLite-era Beads databases.

• Prompt before discarding unsaved TUI new-issue drafts.