Skip to content

RepoMemory changelog

dev.repomemory/repomemory

1 change recorded. MCP Harbor re-reads this listing from the official registry every six hours and asks the live server what it exposes, and keeps what changed between one look and the next.

  • llms.txt +7

    https://repomemory.dev/llms.txt

    + - [Full reference for LLMs](https://repomemory.dev/llms-full.txt): this file plus every parameter and the guides and comparisons in full+ ## Guides+ - [Cursor rules for a team: project rules, team rules and shared memory](https://repomemory.dev/guides/cursor-rules-for-teams): How a team shares Cursor rules: .cursor/rules in git, Team Rules from the dashboard, AGENTS.md, and a shared ledger for decisions the rules don't cover.+ - [CLAUDE.md vs shared memory for coding agents](https://repomemory.dev/guides/claude-md-vs-shared-memory): CLAUDE.md is instructions loaded into every session; shared memory is history an agent searches when it needs it. When to use each, with examples.+ - [How to give Claude Code memory between sessions](https://repomemory.dev/guides/claude-code-memory-between-sessions): Claude Code starts every session with a fresh context. What CLAUDE.md and auto memory carry over, where they stop, and how to add a shared project ledger.+ - [How to share AI coding agent context across a team](https://repomemory.dev/guides/share-ai-agent-context-with-team): Each teammate's agent starts from zero. How to share instructions, decisions, lessons and tasks across Claude Code, Cursor and Codex in one team.+ - [How to stop AI coding agents repeating reverted changes](https://repomemory.dev/guides/stop-ai-agents-repeating-reverted-changes): Agents redo changes you already reverted because the reason lives in a PR or a chat. Record it as a lesson they recall before the next change.