Release notes

0.16.2 · The product site moves to acahti.dev#

2026-11-15 · web 0.7.3 · CLI 0.14.1

The docs, skill and installer have their own domain, the site is rebuilt around Track, and every release now has notes here, with the latest version on every page.

acahti.dev

The product site, the agent skill and install.sh now live at https://acahti.dev. Every instance's whoami.skill_url and MCP instructions point there, and so do the documentation links in the app. acahti.benchyard.com answers every old path with a 301 to the same path on acahti.dev, so released instances and cached skills keep working.

The site is the docs

The root is the overview, and pages moved from /docs/<page>/ to /<page>/; old /docs/ links redirect. The sidebar is regrouped into Use Acahti, Concepts, Features, The app and Self-host. New pages cover the agent-native idea, Track as the mainline, a tour of the app, the Board, Repos and Packages, with fresh screenshots and diagrams that follow light and dark and the page's language.

Release notes and the version

This page lists every release, newest first, with the web and CLI it ships. The header shows the latest version and the home page announces it. The site build refuses a release without notes for the version in versions.env, so the notes ship with the release.

Also in this release

• Web 0.7.3: the account menu and the admin Documentation page open acahti.dev at the new paths.
• CLI 0.14.1: the npm package's homepage and README point at acahti.dev.
• GitHub releases carry these notes.

0.16.1 · Faster MCP requests#

2026-11-15 · web 0.7.2 · CLI 0.14.0

The MCP server keeps one handler per tool set instead of building one for every request.

One handler per tool set

Every MCP request used to build a server and register all 168 tools again, about 80 ms of CPU each time. The server now keeps one handler per distinct tool set and still reads the caller's identity from each request, so callers stay isolated. Under load this removes the timeouts that busy test runs saw, and every agent call costs less CPU.

0.16.0 · One current schema, no legacy paths#

2026-11-15 · web 0.7.2 · CLI 0.14.0

The database schema is one file applied idempotently, and the compatibility paths kept for older releases are gone.

One schema

internal/store/schema.sql is the whole current schema, applied idempotently under the migration lock. One-time changes go in numbered migrations, starting at 013. The old baseline, migrations 001–012 and their backfills are gone. Instances older than 0.15.x upgrade through 0.15.2 first.

Removed

• The work_projects alias (use project_list) and /ui/work/projects-catalog.
• user_update's git_name alias, and the "workspace" document visibility.
• /health; use /healthz.
• The ACAHTI_IMAGE fallback and automatic database creation.

Web 0.7.2 drops the matching fallbacks in the app.

0.15.2 · Planning that agents and people share#

2026-11-14 · web 0.7.1 · CLI 0.14.0

Iterations measure scope, load and burn-up in one read; closing an iteration settles every unfinished todo; tickets are verified by the person who reported them. Covers 0.15.0 to 0.15.2.

One read for planning

planning_brief measures a project and an iteration at once: status, risks (overdue, blocked, deferred twice), each assignee's estimate against the working days left, unestimated work, scope against the baseline the iteration started with, and a daily burn-up. Aidy writes status updates from it. Work added after an iteration starts is out of plan, with who, when and why.

Closing an iteration

iteration_close is the only way to release or cancel. It handles every unfinished todo in the same step: move it, unplan it, or keep it with a reason. Only cancelled iterations can be deleted. Deliveries name the todos they carry and draft the changelog. The CLI adds iteration close and delivery draft.

Tickets and time

Tickets run todo, in progress, verifying, then closed or rejected. Only the reporter or a Work manager closes or rejects one, and rejecting needs a reason. Ticket lists filter by several projects. Due dates are Shanghai calendar days. Todos take estimates and count deferrals. From 18:00 on working days, anyone with work in progress and no time logged is reminded once, and time_entry_suggest proposes the day's entries.

Patches

• 0.15.1: the docs cover planning, ticket verification, document outlines and section links.
• 0.15.2: the docs take the app's design and exist in English and Chinese; web 0.7.1 opens them in the app's language.

0.14.9 · Argos built in, and Aidy acts#

2026-11-14 · web 0.6.3 · CLI 0.13.0

Argos moves into the gateway, Aidy becomes an agent that acts with confirmation, Track gets per-type stage templates and a personal activity view, and knowledge files open in Office. Covers 0.14.0 to 0.14.9.

Argos in the gateway

Argos test results, per-case history, failing environments and their tickets are part of Acahti itself; the Argos plugin is retired and its data moved over. Track reads Argos results directly.

Aidy acts

Aidy is a tool-calling agent over the caller's own MCP catalog. It proposes a write and waits for confirmation, never reports an action it did not take, starts questions with search and its filters, and links every record it mentions. Agent mode is Aidy expanded.

Track

Each flow type has its own stage template, adjustable per flow, and each person has an activity view across Work, repositories and pipelines.

Knowledge in Office

Knowledge files open for editing in the browser with ONLYOFFICE Docs, full screen, alongside PDFs.

Patches

• 0.14.2: the uv pipe resolves internal packages from the organization's Acahti PyPI.
• 0.14.3–0.14.5: Aidy calls Work operations as named tools, filters search by state, and cites the sources it names.
• 0.14.6: Argos lists clamp any page_size like every other list.
• 0.14.9: org admins archive and restore repositories through Acahti (acahti repo archive); CLI 0.13.0.