Skip to content

v3.0.2 — a follow-up that did not resume now says so

Choose a tag to compare

View all tags
@elkaix elkaix released this 12 Sep 18:09
· 3 commits to main since this release
v3.0.2
bfb4dcf
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

A follow-up that did not resume now says so

agy answers --conversation <id> for an id it cannot find from a brand-new conversation and exits 0, only warning on the side. Through 3.0.1, a follow_up with a stale or mistyped session id therefore returned an answer with none of the earlier history and reported it as a normal continuation.

The bridge now compares the conversation a call asked for with the one agy reports, on both the warm and cold paths. A mismatch adds a line to the fenced header:

[claude-agy-mcp 1a2b3c] SESSION NOT RESUMED — you asked to continue <old-id>, but agy answered from a different conversation (<new-id>), so this answer has none of that history. …

Structured responses carry resumed: false. When agy reports no id, nothing is claimed either way.

Also

  • CI now rejects either broken npx install form from v3.0.0, via a test in the repo rather than an external check.
  • The bundled skills and CLAUDE.md explain the new warning.

Install or update the skills with:

npx --package @pymodel/claude-agy-mcp claude-agy-mcp-install-skills

Full changelog: v3.0.1...v3.0.2

Assets 2
Loading