Skip to content

Restore the agents' memory from S3 - #9

Merged
joshuanapoli merged 2 commits into
mainfrom
s3-memory
Nov 4, 2026
Merged

joshuanapoli merged 2 commits into
mainfrom
s3-memory

Conversation

@joshuanapoli

@joshuanapoli joshuanapoli commented Oct 21, 2026 •

Copy link
Copy Markdown
Member

Why

The agents' auto-memory never carried over between runs. The Actions cache entry that claude-code-memory saves 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, respond and fix-ci take memory-bucket and memory-role and pass them to claude-code-memory. With no bucket given, the memory step is skipped, so a caller that doesn't set these keeps working, just without memory.
  • The issue, review-rework and ci-rework reusable 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 on main.
  • The jobs already hold id-token: write, which the role assumption needs.

Before merging

claude-code-memory is pinned to 0cedc537 on its s3-store branch, 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.
  • actionlint is clean on the three workflows.

joshuanapoli and others added 2 commits October 21, 2026 15:45
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
alok27a self-requested a review November 4, 2026 15:04

@alok27a alok27a left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks

@joshuanapoli
joshuanapoli merged commit e183982 into main Nov 4, 2026
3 checks passed
@joshuanapoli
joshuanapoli deleted the s3-memory branch November 4, 2026 15:10
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