docs+fix: EverOS-wrapper quickstart, ms-timestamp fix, live-validated - #14
Merged
Conversation
Now that the ergonomic EverOS client ships, show it as the primary usage instead of the low-level MemoryApi/ApiClient assembly. - README Quickstart: EverOS wrapper snippet (this is the PyPI project page). - quickstart.md: rewritten wrapper-first (add/flush/get/search/edit/delete/ upload via client.*), with the typed low-level client kept as an Advanced section (client.memory / client.storage). - ci.yml drift check: extended to map instance vars to their class, so it now validates EverOS wrapper methods in addition to MemoryApi/StorageApi. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Live validation against the real v2 API surfaced two issues: - MessageItem.timestamp must be a unix MILLISECOND timestamp (>= 1e12); the wrapper defaulted to int(time.time()) (seconds), which the API rejects (422). Fixed to int(time.time() * 1000); tests + the low-level example use ms too. - get/search require user_id or agent_id — the quickstart/README examples omitted it (422). Added user_id (+ a sender_id) so the walkthrough is self-consistent. Verified: full live round-trip add->flush->get->search->upload->delete is green against api.evermind.ai; 18 unit tests + drift check green. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
dani1005
changed the title
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
The PyPI project page (README) and quickstart still showed the low-level
MemoryApi/ApiClientassembly from before the wrapper existed. Now thatEverOSships, lead with it.EverOSwrapper snippet (5 lines instead of ~18). This is what renders on the PyPI project page.add / flush / get / search / edit / delete / uploadviaclient.*, plus a method table and a "Low-level typed client (advanced)" section preserving the typedMemoryApi/StorageApiusage (client.memory/client.storage).EverOSwrapper methods too (not justmemory.*/storage.*).Validated locally against the installed rc3 package: drift check resolves all 7 wrapper + 2 low-level methods, 18 wrapper tests green.
🤖 Generated with Claude Code