Ai

Spec Kit v0.9.0: Agent Context Migration to Extension

Spec Kit v0.9.0: Agent Context Migration to Extension

Spec Kit's latest release, v0.9.0, introduces a significant architectural change: agent context updates are now handled by the agent-context extension. This is a deliberate move toward modularity, but it comes with a transitional setup that developers need to understand.

What Changed

Previously, Spec Kit automatically updated agent context as part of its core functionality. With v0.9.0, that logic has been extracted into a separate extension. The update also includes a compatibility fallback — the extension is auto-enabled to preserve existing behavior. This fallback is deprecated. It will be removed entirely in v0.12.0.

The command to install the new version is straightforward: uv tool install specify-cli --from git+https://github.com/github/[email protected]. After that, running specify init my-project initializes a new project.

Why It Matters

Decoupling agent context from the core makes Spec Kit more flexible. Developers can now opt in to automatic updates by explicitly configuring the extension. The change is also a precursor to richer context management features down the line.

But here's the catch: if you rely on automatic agent context updates and ignore this notice, your workflows will break come v0.12.0. That's six versions from now — enough time to adapt, but easy to overlook. I'd recommend updating your configuration immediately. Run specify extension enable agent-context after upgrading to v0.9.0.

The team is signaling a shift in philosophy: less magic, more explicit control. It's a pattern we've seen across developer tools, and it tends to pay off in clarity. For now, the fallback keeps things running. But don't get comfortable. v0.12.0 is coming.

Official Source: https://github.com/github/spec-kit/releases/tag/v0.9.0