Release v0.3.4 - #89
Merged
Merged
Conversation
Bump the marketplace-stream hosts -- Claude Code, Codex, Kimi Code, and Copilot -- to 0.3.4, along with the shared MCP client's default clientInfo version. pi versions independently and is untouched. This release is about the sessions routing could not reach. A session with nothing connected is the case routing exists for, and it was the one case that could not route: the resolved mode was persisted on every write, so every machine that had ever saved a context had the old "ask" default written into ~/.neatcontext/plugin-routing.json, where no change of default could reach it. Schema 2 keeps an unchosen mode out of the file and reads a schema 1 "ask" as the default it was, and the nothing-connected text now leads with the route the session can take itself. Saving now connects the session that had nothing to what it just wrote, so there is no `use` on the context you just saved; a session that already has one keeps it. On Copilot, the slash commands and the MCP bridge finally agree on which session they are in -- they were hashing different working directories and answering from different selections.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bump the marketplace-stream hosts — Claude Code, Codex, Kimi Code, and Copilot — to 0.3.4, along with the shared MCP client's default
clientInfoversion and therefthe Claude marketplace installs from. pi versions independently and is untouched.This release is about the sessions routing could not reach.
A session with nothing connected is the case routing exists for, and it was the one case that could not route (#87). The resolved mode was persisted on every routing write, so every machine that had ever saved a context had the old
askdefault written into~/.neatcontext/plugin-routing.json— where no change of default could reach it, reinstall or not. Schema 2 keeps an unchosen mode out of the file and reads a schema 1askas the default it was. The nothing-connected text now leads with the route the session can take itself instead of a slash command.Saving connects the session that had nothing to what it just wrote (#85), so there is no
useon the context you just saved. A session that already has one keeps it — saving under another name is Save As, not a re-grounding.On Copilot, the slash commands and the MCP bridge now agree on which session they are in (#86). They were hashing different working directories and answering from different selection files, with no error on either side. Copilot's published session identity is used, with the workspace digest kept as a fallback, and the cross-process session pointer is promoted into
shared/core/.Plus the pi README now names
autoas the default routing mode (#88) — the last place in the repo still describing the old behavior.Checks
npm run check— pass (includes thesync:evidenceandsync:contextdrift checks)npm test— 496 pass, 0 failnpm run validate:plugin— pass, strict, both manifestsAfter merge:
git tag v0.3.4 && git push origin v0.3.4, then publish the GitHub release. Marketplaces install from the tag.