# AI Game Developer v0.22.1 — The Knowledge Base becomes easy to reach, and the agent gets spaces

The Knowledge Base is a project knowledge base the agent keeps as markdown notes in.ai-game-dev/knowledge/, committed with your project and shown as a 3D graph. You can now open it from the status bar, from the session's Tools row, from the Explorer and from the right panel.

_Last updated: 2026-10-07_

Released 2026-10-07. All releases: https://ai-game.dev/releases

## Featured

### The Knowledge Base is now easy to open

A status bar entry shows how many notes the project has, briefly pulses when the agent writes a note, and opens the graph. The session's Tools row gains an "Open the Knowledge Base graph" button, Knowledge Base folders and notes in the Explorer gain "Open in Knowledge Base graph", and until now the graph could only be reached from the command palette. (#695)

### Knowledge Base spaces

Any Knowledge Base folder with a README is a space with a title and a short description. The agent sees a short catalogue of spaces, opens one when it needs it, and can create new spaces. (#701)

## New

### Knowledge Base view in the right panel

The Knowledge Base now has its own view in the right panel, next to the full graph window, with its own UI and header. It is built on general kernel support, so packages can contribute right-panel views with their own header and layout. (#698)

## Improved

### Package windows look like the app

The Knowledge Base graph window and other windows opened by packages now use the app's own header instead of the operating system frame, and follow your theme live, including window controls. This is a host capability, so any package window gets the same treatment. (#696)

### Themed graph controls and quieter glow

The graph's depth dropdown and scrollbars now follow your theme instead of the operating system's drawing, and nodes glow only when you hover or focus them rather than all the time. (#699)

### The agent files notes and decisions more carefully

The agent records decisions you state in the same turn together with their reason and what they replaced, links each new note from its space's README, and reports links per folder as well as per note. Notes filed in a space are no longer reported as orphans, and unlinked notes in no space still are. (#710)

## Fixed

### Knowledge Base watching no longer blocks folder renames

The Knowledge Base watches files only while the graph window is open, so on Windows you can rename the project folder again once the graph is closed. It also notices when the Knowledge Base folder itself is renamed or replaced, and large graphs stay responsive because the layout no longer blocks the interface. (#693)

### Two copies of the app no longer rewrite shared package files in a loop

When two copies run on one machine, for example the desktop app and the command line tool, they no longer rewrite the shared package files in a loop, and when they start at the same moment neither loses the other's default packages or package choices. This holds when both copies are 0.22.0 or newer; an older copy running alongside can still rewrite the shared files until it is updated to 0.22.0 too. (#692)

### The shared-file loop is also gone for plugins and shared dependencies

The same shared-machine problem is fixed when the packages involved share plugins or shared dependencies: the plugin requirements and dependency ranges needed by a package another copy runs are kept instead of being dropped and written back. The previous mixed-version caveat still applies. (#708)

### Recovering from repeated compaction failures

After repeated compaction failures, /clear in the desktop app now starts a fresh conversation while keeping the old session in your history, and /clear and /reset in the CLI start a fresh context and reset the context counters; the CLI waits until an in-flight request has fully finished, teardown after Stop included, before it will reset. The app also shows concrete recovery guidance when compaction keeps thrashing. Serious client errors and handled agent failures can be linked to the account that experienced them, and that identity follows authentication, survives an account switch and is cleared on sign-out; agent failure reports use safe error codes instead of the raw provider message, prompt or project contents, and reporting still respects your existing settings. (#714)

## Under the hood

- chore: release v0.22.0 (#711)

---

Source (HTML): https://ai-game.dev/releases/0.22.1