Error tracking drawer, bulk status and token logging
Most of this release is error tracking. The new detail on an error needs kendo-error-tracker ^0.2; an error reported by an older version says so.
New ​
- Error drawer. Click an error's message on Error Tracking or a project's Errors page to open it in a side drawer, with Prev and Next through the list. Change its status, create an issue, or open its tracked issue without leaving the list.
- Bulk Resolve, Ignore and Reopen. Tick errors on either error page, or tick the header to select every error your search and filters leave, then change them all at once.
- Regressed errors. A resolved error that occurs again reopens and shows Regressed, along with who resolved it and how often it reopened. An event from the release it was resolved in keeps it resolved. An issue created from the error shows the same status in its Issue Source section.
- What happened. An error's page and drawer list the exception and each exception that caused it, with a one-line summary of how often it was seen, by how many users, where it ran, and in which releases.
- Token usage from every member. Members can now record an agent session's AI token usage on an issue: with the
record-token-usageMCP tool,kendo tokens log, or the token events API, naming the issue by key or id. Every existing non-admin role may now send it. Send the same session id again (external_event_id, or--idin the CLI) and its totals are replaced instead of added to. - Token Usage guide. The new Token Usage guide includes a Claude Code hook that sends a session's usage to the issue named in its branch when the session ends.
kendoCLI v0.15.0.kendo tokens logrecords a session's token usage on an issue, andkendo issue viewshows the issue's AI token total. Upgrade to get both.
Improved ​
- One error table, more columns. Both error pages share one table with a column picker and "is" / "is not" filters on Status, Environment, Release and, on Error Tracking, Project. New columns: Trend (14 daily bars), Users, Status, First seen, Release, First release, Context (the route, job or command the error ran in) and Resolved by; search also matches the context.
- Readable stack traces. The error page folds vendor frames under App frames, with All frames one click away, and shows each Caused by trace in its own collapsed section.
- Release and runtime panels. The error page adds By release and Runtime (memory and hosts) beside Details. Details gains Affected users, and its Release field is now First release.
- Per-tenant affected users. In an app with one database per tenant, kendo-error-tracker
^0.2.1can count each tenant's users apart; the error tracking guide has the one-line setup. - Error APIs.
POST /api/projects/{projectId}/error-eventsaccepts the cause chain, exception code, runtime, framework, memory use, context, host and a keyed user hash, all optional.POST /api/error-groups/bulk-statuschanges the status of up to 500 errors in one call. - Sprints in date order over MCP. The
kendo://projects/{id}/sprintsresource lists sprints by start date, oldest first.
Fixed ​
- Oversized uploads skipped up front. Files over 20 MB on issues, epics and comments are skipped with a note before uploading, instead of uploading in full and then failing with "Upload failed". A pasted image over 20 MB is not sent either; the editor shows "Image upload failed".
- Failed downloads say why. A failed download, preview or export now shows the server's error message, instead of nothing or "Kendo is updating".