Skip to content

Recall memories directly on substantive prompts - #76

Merged
graphite-app[bot] merged 1 commit into
mainfrom
codex/direct-recall
Sep 23, 2026
Merged

graphite-app[bot] merged 1 commit into
mainfrom
codex/direct-recall

Conversation

@ishaanxgupta

@ishaanxgupta ishaanxgupta commented Aug 22, 2026 •

Copy link
Copy Markdown
Contributor

Add automatic memory recall for substantive prompts with configurable modes and per-session deduplication.

ishaanxgupta commented Aug 22, 2026 •

Copy link
Copy Markdown
Contributor Author

How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

  • merge-queue - adds this PR to the back of the merge queue
  • fast-track - for urgent changes, fast-track this PR to the front of the merge queue

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

Dhravya
Dhravya previously approved these changes Sep 1, 2026

Dhravya commented Sep 1, 2026 •

Copy link
Copy Markdown
Member

Merge activity

  • Sep 1, 6:37 AM UTC: A user started a stack merge that includes this pull request via Graphite.
  • Sep 1, 6:39 AM UTC: Graphite rebased this pull request as part of a merge.
  • Sep 1, 6:39 AM UTC: Graphite couldn't merge this PR because it was not satisfying all requirements (PR does not have required approvals).
  • Sep 1, 6:44 AM UTC: A user started a stack merge that includes this pull request via Graphite.
  • Sep 1, 7:04 AM UTC: Graphite couldn't merge this PR because it failed for an unknown reason (GitHub is reporting that this PR is not mergeable, despite passing required status checks defined by your branch protection rules. Please check your rulesets for additional blocking criteria. Graphite Merge Queue does not currently support rulesets. Please contact Graphite support for further assistance.).
  • Sep 1, 9:53 AM UTC: A user started a stack merge that includes this pull request via Graphite.
  • Sep 1, 10:13 AM UTC: Graphite couldn't merge this PR because it failed for an unknown reason (GitHub is reporting that this PR is not mergeable, despite passing required status checks defined by your branch protection rules. Please check your rulesets for additional blocking criteria. Graphite Merge Queue does not currently support rulesets. Please contact Graphite support for further assistance.).
  • Sep 23, 12:50 AM UTC: Dhravya added this pull request to the Graphite merge queue.
  • Sep 23, 12:54 AM UTC: Merged by the Graphite merge queue.

@Dhravya
Dhravya changed the base branch from codex/recall-quality to graphite-base/76 September 1, 2026 06:37
@Dhravya
Dhravya changed the base branch from graphite-base/76 to main September 1, 2026 06:37
@Dhravya
Dhravya dismissed their stale review September 1, 2026 06:37

The base branch was changed.

@Dhravya
Dhravya force-pushed the codex/direct-recall branch from 2b79fed to 36bc167 Compare September 1, 2026 06:38
Add automatic memory recall for substantive prompts with configurable modes and per-session deduplication.
@graphite-app
graphite-app Bot force-pushed the codex/direct-recall branch from 36bc167 to 3d77cd8 Compare September 23, 2026 00:51
@graphite-app
graphite-app Bot merged commit 3d77cd8 into main Sep 23, 2026
3 of 4 checks passed
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.

2 participants