Skip to content

fix(agentstudio): send the documented precondition object on memory update - #212

Closed
foleydang wants to merge 1 commit into
mainfrom
dev/agentstudio-memory
Closed

foleydang wants to merge 1 commit into
mainfrom
dev/agentstudio-memory

Conversation

@foleydang

Copy link
Copy Markdown
Collaborator

Follow-up to #210: the public memory-store docs (and CMA) specify the
optimistic lock as a nested {"type": "content_sha256", "content_sha256": ...} object. #210 shipped the flat content_sha256 form (the control
controller flattens both, so both worked on the wire); this sends the
documented shape instead:

  • memories.update() takes a precondition argument — the sha string
    (wrapped into the documented object automatically) or the full object
  • docstring/param docs updated; unit tests + pre-release e2e green

🤖 Generated with Claude Code

…pdate

The public memory-store docs (and CMA) specify the optimistic lock as a
nested {"type": "content_sha256", "content_sha256": ...} object; the
control controller flattens it, so the flat form also worked, but the
SDK now sends the documented shape: update() takes a `precondition`
argument accepting either the sha string (wrapped automatically) or
the full object. Verified by e2e against the pre-release environment.

Co-Authored-By: Claude Code <noreply@anthropic.com>
@foleydang foleydang closed this Oct 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant