Changelog

What shipped and what is planned.

v0.1 and v0.2 are released. v0.2.1 is in progress and v0.3 is planned. This list can change as work progresses.

v0.3Planned

Change direction without losing earlier work

Record technical decisions with the plan. When one changes, Ajiya will find tickets that may be affected. An agent assesses the impact, then a person approves the update. Replaced work keeps its history and evidence.

Planned: optional tags, changed-file reporting, decision records, superseded history and a change-request workflow with human approval.

v0.2.1In progress

Small fixes and doc changes

Nine small polish tickets:

  • ajiya ticket done reminds you to commit the plan change
  • ajiya app add quotes the path it registered
  • Guide: other trailers can share the Ajiya paragraph
  • Nested projects: ajiya init warns, and hooks check the owning plan
  • ajiya status counts only tickets that can start
  • Guide: what ajiya ticket done and ajiya build change
  • README: non-interactive init and the auto-added trailer
  • ajiya init finds per-app test commands in a monorepo
  • MCP asks for roots only from clients that support them
v0.2.0ReleasedReleased 2026-09-30

Connect agents and simplify installation

All 74 v0.2 milestone tickets are complete. Shipped:

  • ajiya status and ajiya ticket list
  • The MCP server (ajiya mcp)
  • ajiya mcp install for Claude Code, Codex and Cursor
  • The install script and the PowerShell script
  • npm packages
  • A Homebrew cask
  • Signed and notarised macOS binaries
  • The Claude Code plugin
  • ajiya phase remove

Release notes and downloads →

v0.1Complete

Keep the project plan and handoff in your repo

All 37 v0.1 milestone tickets are complete. The CLI, local dashboard, project setup, ordered milestones, imports, checks and release build are in place.

Ajiya tracks its own release work.

We use Ajiya to plan its releases, link changes to commits and review what remains. This is the Overview view of Ajiya's own plan.

Ajiya · ajiya serve
Ajiya
Overview
Next up
Board
Dependencies
Phases
Tickets
Apps
Checks
Activity
Ajiya plan · 2026-10-01

Overview

Progress per milestone, in order, and per phase.

Milestones

In order. Each counts the tickets it needs, including what they depend on; closed means done or dropped.

1v0-1100%
37/37 closed · 0 in progress · 0 can start now
2v0-2100%
74/74 closed · 0 in progress · 0 can start now
3v0-2-189%
74/83 closed · 0 in progress · 9 can start now
4v0-388%
74/84 closed · 0 in progress · 1 can start now
Phases
Commit-rule8/9 · 88%
Apps-launch14/15 · 93%
Outputs12/12 · 100%
Onboarding17/21 · 80%
Release5/5 · 100%
Agent-access6/9 · 66%
Install24/24 · 100%
Decisions-and-changes0/11 · 0%

Generated by ajiya build on 2026-10-01. Milestone names such as v0-2-1 are the names used in the plan. Each milestone counts the tickets it needs, including earlier work.