Repo Memory

Repo memory provides persistent file storage via Git branches with unlimited retention. The compiler auto-configures branch cloning/creation, file access at /tmp/gh-aw/repo-memory-{id}/, commits/pushes, and merge conflict resolution (your changes win).

---
tools:
  repo-memory: true
---

Creates branch memory/default at /tmp/gh-aw/repo-memory-default/. Files are stored within the branch at the branch name path (memory/default/). Files auto-commit/push after workflow completion.

---
tools:
  repo-memory:
    branch-name: memory/custom-agent-for-aw
    branch-prefix: tracking  # Custom prefix instead of "memory"
    description: "Long-term insights"
    file-glob: ["memory/custom-agent-for-aw/*.md", "memory/custom-agent-for-aw/*.json"]
    max-file-size: 1048576  # 1MB (default 10KB)
    max-file-count: 50      # default 100
    max-patch-size: 102400  # 100KB max (default 10KB)
    target-repo: "owner/repository"
    create-orphan: true     # default
    allowed-extensions: [".json", ".txt", ".md"]  # Restrict file types (default: empty/all files allowed)
---

Branch Prefix: Use branch-prefix to customize the branch name prefix (default is memory). The prefix must be 4-32 characters, alphanumeric with hyphens/underscores, and cannot be copilot. When set, branches are created as {branch-prefix}/{id} instead of memory/{id}.

File Type Restrictions: Use allowed-extensions to restrict which file types can be stored (default: empty/all files allowed). When specified, only files with listed extensions (e.g., [".json", ".txt", ".md"]) can be saved. Files with disallowed extensions will trigger validation failures.

Patch Size Limit: Use max-patch-size to limit the total size of changes in a single push (default: 10KB, max: 100KB). The total size of the git diff (all staged changes combined) must not exceed this value. If it does, the push is rejected with an error. Use this to prevent large unintentional memory updates.

Note: File glob patterns must include the full branch path structure. For branch memory/custom-agent-for-aw, use patterns like memory/custom-agent-for-aw/*.json to match files stored at that path within the branch.

---
tools:
  repo-memory:
    - id: insights
      branch-prefix: daily  # Creates daily/insights branch
      file-glob: ["daily/insights/*.md"]
    - id: state
      file-glob: ["memory/state/*.json"]
      max-file-size: 524288  # 512KB
---

Mounts at /tmp/gh-aw/repo-memory-{id}/ during workflow execution. Required id determines folder name; branch-name defaults to {branch-prefix}/{id} (where branch-prefix defaults to memory). Files are stored within the git branch at the branch name path (e.g., for branch memory/code-metrics, files are stored at memory/code-metrics/ within the branch). File glob patterns must include the full branch path.

Branches auto-create as orphans (default) or clone with --depth 1. Changes auto-commit after validation (file-glob, max-file-size, max-file-count), pull with -X ours (your changes win), and push when changes detected and threat detection passes. Auto-adds contents: write permission.

For fast 7-day caching without version control, see Cache Memory.

• Branch not created: Ensure create-orphan: true or create manually.
• Permission denied: Compiler auto-adds contents: write.
• Validation failures: Match file-glob, stay under max-file-size (10KB default), max-file-count (100 default), and max-patch-size (10KB default).
• Patch too large: If the total diff exceeds max-patch-size (default 10KB), the push is rejected. Reduce the number or size of changes, or increase max-patch-size in the configuration.
• Changes not persisting: Check directory path, workflow completion, push errors in logs.
• Merge conflicts: Uses -X ours (your changes win). Read before writing to preserve data.

Don’t store sensitive data in repo memory. Repo memory follows repository permissions.

Use private repos for sensitive data, avoid storing secrets, set constraints (file-glob, max-file-size, max-file-count, max-patch-size), consider branch protection, use target-repo to isolate.

See Deep Report and Daily Firewall Report for long-term insights and historical data tracking.

• Cache Memory - GitHub Actions cache-based storage with 7-day retention
• Frontmatter - Complete frontmatter configuration guide
• Safe Outputs - Output processing and automation