2026-04-03 · Sessions Now Actually Stay Project-Aware

Published: April 3, 2026
Tags: release chat project context

Core changes

New sessions can bind a project before the first real message. No more dummy first turn just to make project context stick.
Session skills now load from the session's actual project context:
- read .agents/skills from the selected project
- keep workspace-installed skills
- distinguish same-name skills by stable refs instead of merging by display name
A project's own AGENTS.md and project context now flow into a dedicated Project Context block.
The project badge in chat header is now actionable:
- change the project directory there
- remove the project there
- refresh skills immediately after project changes

Project context no longer waits for a first persisted message to become real.
Project skills no longer silently disappear or get mixed with same-name workspace skills.
Skill lists now refresh immediately after project changes instead of showing stale data.
Removing project context now updates the visible header state consistently.

This is a coordinated npm patch release, not a one-package hotfix. Key published packages include:

Related channel plugin patches were published in the same batch to keep dependency alignment clean.

Start a new chat session.
Set the project directory first.
Open the skill picker and confirm that .agents/skills from the project is already available.
Send the first message and let the model work in that project context from turn one.
Change or remove the project later from the header badge.