docs: add inspeximus to community session implementations#3906
Draft
DanceNitra wants to merge 1 commit into
Draft
docs: add inspeximus to community session implementations#3906DanceNitra wants to merge 1 commit into
DanceNitra wants to merge 1 commit into
Conversation
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
seratch
marked this pull request as draft
July 21, 2026 21:08
Member
|
Thanks for sharing this. It seems like the project is still pretty new, so we'd like to wait and see whether people start using it. |
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
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.
Adds one row to the community session implementations table, per the standing invitation at the end of that section.
inspeximus(MIT, zero-dependency core) implements theSessionprotocol asinspeximus.integrations.openai_agents.InspeximusSession, backed by a JSON file — no server and no extra install beyond the package itself.Checked against
SQLiteSessionRather than assert "drop-in", I ran both implementations through the same scenarios and compared the observable results: round-trip ordering,
limitreturning the latest N oldest-first,limit=0, LIFOpop_itemandNoneon empty,clear_session(including on an already-empty session), adding an empty list, and isolation between two session ids. 13 checks, no differences, onopenai-agents 0.18.3. The audit runs in CI, and it has a falsification mode that swallows writes — if that mode still passed, the comparison would be proving nothing.The one thing it adds beyond persistence:
session.forget_subject(request_id=...)hard-deletes a user's turns across sessions and leaves a signed, content-free tombstone, so the erasure is provable and does not read as tampering.To be straight about scope: a
Sessionis a verbatim turn log, so the library's supersession features do not silently rewrite replayed messages. This row is about the session backend only.AI disclosure
This contribution was drafted with AI assistance. A human reviewed it, and the parity numbers above come from a run rather than from the README.