-
Notifications
You must be signed in to change notification settings - Fork 361
fix: harden GPT/Codex tool linkage, follow-up outcomes, and memory persistence contracts #386
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
jamiepine
merged 7 commits into
spacedriveapp:main
from
tomasmach:fix/gpt-codex-hardening-pass
Mar 10, 2026
Merged
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
c79c9e9
fix: harden openai linkage and memory persistence completion contracts
tomasmach 555bbd6
fix: preserve call_id when serializing openai responses tool calls
tomasmach 6d76df1
refactor: remove redundant memory persistence contract tracking
tomasmach 5863ed2
fix: address review findings from PR #386
tomasmach 271c82e
fix: delete associations before memory row in embedding failure compe…
tomasmach c280140
fix: apply memory persistence contract to ingestion, extract retry pr…
tomasmach 3f0aaa7
Merge branch 'main' into fix/gpt-codex-hardening-pass
jamiepine File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1 +1 @@ | ||
| Review the recent conversation and persist any important information as memories. Start by recalling existing memories related to the topics discussed, then save new or updated memories with appropriate associations. | ||
| Review the recent conversation and persist important information as memories. Required order: use memory_recall first, then memory_save when appropriate, then finish by calling memory_persistence_complete. Never invent memory IDs. |
1 change: 1 addition & 0 deletions
1
prompts/en/fragments/system/memory_persistence_contract_retry.md.j2
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1 @@ | ||
| You must finish this memory-persistence run by calling memory_persistence_complete. First recall relevant memories, then save real memories if needed, then call memory_persistence_complete with either outcome="saved" and exact saved_memory_ids from successful memory_save calls in this run, or outcome="no_memories" with a short reason and no saved IDs. Do not invent memory IDs. |
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1 @@ | ||
| Finish a memory persistence run with a terminal outcome. Use outcome="saved" only with exact memory IDs returned by successful memory_save calls in this run, or outcome="no_memories" with a short reason and no IDs. |
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
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.