Repository navigation
Restore the agents' memory from S3 - #9
Merged
Merged
Conversation
claude-code-memory moves its store from the Actions cache to S3, because a cache entry saved by a pull request run is visible only to that pull request. Triage, respond and fix-ci take the bucket and the role that reaches it as memory-bucket and memory-role, and skip the store when no bucket is given. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The reusable workflows take memory-bucket and memory-role and pass them to the agent that restores the store, and pin all of their own actions to 866bb78, which accepts them. Merge this with a merge commit: 866bb78 has to stay on main for these pins to resolve. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
alok27a
self-requested a review
November 4, 2026 15:04
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.
Why
The agents' auto-memory never carried over between runs. The Actions cache entry that
claude-code-memorysaves is visible only to the ref that saved it, and in CVector-Energy/ui every entry so far came from a pull request. CVector-Energy/claude-code-memory#6 moves the store to S3.What changes
triage,respondandfix-citakememory-bucketandmemory-roleand pass them toclaude-code-memory. With no bucket given, the memory step is skipped, so a caller that doesn't set these keeps working, just without memory.issue,review-reworkandci-reworkreusable workflows accept the same two inputs and pass them through. They pin their own actions to 866bb78, the commit that accepts the inputs. Merge with a merge commit so 866bb78 stays onmain.id-token: write, which the role assumption needs.Before merging
claude-code-memoryis pinned to0cedc537on itss3-storebranch, the head of CVector-Energy/claude-code-memory#6. Once that PR is merged and released (as v0.2.0), re-pin to the release commit.Testing
npm test: 132 tests pass.actionlintis clean on the three workflows.