You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Ending an unknown Session is rejected instead of creating a ghost row #41
Calling /agentmemory/session/end with a Session id that was never started answers 404 session_not_found and writes nothing, so the Session list only ever holds Sessions that happened. The Engine's update-creates-missing-key behaviour is unchanged; the PR body reports every other caller that updates a key without first checking it exists.
Acceptance criteria
Unknown id → 404 with session_not_found; no row appears in the sessions scope afterwards
Known id still ends normally with the same response as today
The audit of other update-without-check callers is written into the PR body
Done in 3dc4085 on fix/api-bounds: session/end answers 404 session_not_found for an unknown id and writes nothing; known ids unchanged. Audit of other update-without-check callers is in the commit and will be in the PR body.
Activity
possiblyneal commentedon Sep 22, 2026
Done in 3dc4085 on fix/api-bounds: session/end answers 404 session_not_found for an unknown id and writes nothing; known ids unchanged. Audit of other update-without-check callers is in the commit and will be in the PR body.
fix(api): refuse session/end for a Session that never started