More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    ShareMemory

    1

    Shared project memory and handoffs for Claude Code and Codex, stored in your repository.

    $4

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    ShareMemory

    ShareMemory

    Example session with this skill installed

    Initialize ShareMemory in a fresh local project. Use English memory and leave Git recovery disabled. Then run memory status and verify that a second process can read a handoff from the same AI_MEMORY/ folder.

    Verification example below: a deterministic local fixture using the packaged templates and helpers; it is not a transcript from two live AI models.

    • Read your context and instructions
    • Compiled the sharememory

    Verified local package example

    The packaged v1.3 files were extracted into a disposable project and exercised with two fixture identities. This is a local file/lock test, not a live-agent transcript.

    Initialized project structure

    target-project/
    ├── AGENTS.md
    ├── CLAUDE.md
    ├── MEMORY_PROTOCOL.md
    ├── scripts/
    │   ├── check_memory.sh
    │   └── memory_lock.sh
    └── AI_MEMORY/
        ├── CONFIG.md
        ├── PROJECT.md
        ├── DECISIONS.md
        ├── TASKS.md
        ├── LEARNINGS.md
        ├── SYNC_LOG.md
        └── archive/
    

    Complete verification summary

    CheckResult
    Existing template/lock acceptance suite21/21 passed
    ZIP and extracted-fixture checks20/20 passed
    Both agent skill pathsResolved to the same extracted SKILL.md
    InitializationPassed memory lint
    First fixture identity holds the lockSecond identity is blocked
    Wrong-identity lock releaseRejected
    First identity writes a handoffIndependent process reads the same note
    Second identity acknowledges the handoffSucceeds after the first releases the lock
    Updated log versus prior boot receiptStatus reports the change
    Final stateMemory lint passed; no held lock or Git repository

    Observed helper output included

    ✓ lock acquired by FixtureA
    ✓ memory OK
    ✓ lock released
    ✓ boot recorded for FixtureB
    ✓ lock acquired by FixtureB
    ✓ lock released
    

    Use it in your project

    After installing the complete skill folder, ask "init memory", choose your language and Git preference, then use "memory status" and "update memory" during coding handoffs. Both coding agents must open the same project directory.

    Resolved to the same extracted SKILL.md

    Connects securely to your tools. The creator never sees your data.

    About this skill

    ShareMemory gives Claude Code and Codex one shared, project-local memory folder. Keep decisions, active tasks and handoff notes in plain Markdown so the next coding session can pick up the work.

    What you get

    • One AI_MEMORY/ folder per project with project context, decisions, tasks, learnings and a daily handoff log.
    • Shared startup instructions in AGENTS.md and CLAUDE.md, plus a MEMORY_PROTOCOL.md that describes how to read and update memory.
    • Two Bash helpers: an advisory write lock with stale-lock recovery, and a linter for memory structure, size limits and basic secret-pattern checks.
    • Instructions for initializing, updating, checking, consolidating, repairing and migrating project memory.

    Getting started

    1. Install the complete skill folder in the project where you want shared memory. For Claude Code and Codex together, use one canonical skill copy and the documented symlink layout.
    2. Ask your coding agent to "init memory". Choose the memory language and whether to enable Git history recovery.
    3. Open the same project directory with the other agent. Ask for "memory status" to inspect the shared state.
    4. Use "update memory" to record a handoff or refresh the current project context.

    Designed for local coding workflows

    Both agents need access to the same project files. The workflow requires local file read/write access, Bash and standard shell utilities. It does not require a hosted memory service, database or API keys.

    The lock is advisory: it helps agents that follow the protocol coordinate their writes. It cannot stop an agent that ignores the rules or make simultaneous editing universally safe. ShareMemory is project-scoped and does not provide cross-project memory or built-in remote synchronization.

    Included buyer guide

    The package includes BUYER_GUIDE.md with setup, daily usage, troubleshooting and license information. Detailed operation steps are in references/operations.md, supplied with the skill.

    Verification

    The v1.3 package passed 21 existing acceptance checks and 20 package/local-fixture checks. The fixture covered initialization, shared file paths, handoffs and lock behavior. These checks did not run two live AI agents or validate Agensi connector delivery.

    Project-scoped, local file memory; no built-in cross-project or remote synchronization. Agents must follow the protocol: write locks are advisory, and the linter cannot guarantee memory accuracy or detect every secret. Bash and project read/write access are required. Current checks cover templates, files and locks, not two live model sessions or Agensi connector delivery.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 1 month ago

    Requires

    Claude Code or Codex
    Bash
    Standard shell utilities
    Git

    Permissions

    Terminal / Shell
    Read Files
    Write Files

    File Scopes

    AI_MEMORY/**
    AGENTS.md
    CLAUDE.md
    MEMORY_PROTOCOL.md
    scripts/check_memory.sh
    scripts/memory_lock.sh
    *.bak.*

    Reads and writes only the target project's memory, boot instructions and helper scripts. Initialization creates AI_MEMORY/, AGENTS.md, CLAUDE.md, MEMORY_PROTOCOL.md and scripts/check_memory.sh + scripts/memory_lock.sh; existing boot files are backed up before marker-block updates. Runs local Bash helpers for locks and linting. Optional Git recovery requires user consent. No connected service accounts, environment-variable harvesting or network calls are required by the memory workflow.

    Listed1 month ago
    Updated27 days ago

    What's inside

    Frequently Asked Questions

    Both coding agents read and update the same project-local AI_MEMORY/ Markdown files. The protocol organizes context, decisions, tasks, learnings and handoffs. Advisory locks help cooperating agents coordinate writes; they do not enforce compliance or guarantee conflict-free parallel editing.

    The installation and boot instructions target Claude Code and Codex with local file read/write access and Bash. Both must open the same project directory. Other agents may need adaptation; chat-only agents without local tools cannot run the full workflow.

    The memory workflow stores Markdown in your local project and does not require a hosted memory service, database or API keys. Your coding agent may send files it reads to its model provider under that provider's own settings and terms.

    The package contains SKILL.md, BUYER_GUIDE.md, the included license, the operations reference, blank memory templates, project boot/protocol templates, and the two Bash helpers for memory linting and write locks. It does not include the maintainer's actual project memory.

    Use BUYER_GUIDE.md from the delivered package to make the complete skill available to your coding agent. Open your target project and ask 'init memory'. Choose the memory language and Git recovery preference, then open the same project with the second agent and ask 'memory status'.

    ShareMemory is scoped to one project directory and does not include remote synchronization or cross-project memory. Both agents need access to the same project files. Git recovery is optional and is enabled only with user consent.

    New in Agents & Orchestration