From 7bf89d0443acbc26afa8d66b6a8de1ba996fe547 Mon Sep 17 00:00:00 2001 From: christine <40064228+christinetyip@users.noreply.github.com> Date: Thu, 18 Dec 2025 00:11:20 +0100 Subject: [PATCH 1/3] Updated instructions to use the Ensue Skill in Claude --- Dev Mindshare/README.md | 40 ++++++++++++++++++++++++++-------------- 1 file changed, 26 insertions(+), 14 deletions(-) diff --git a/Dev Mindshare/README.md b/Dev Mindshare/README.md index 6ff75bf..f707651 100644 --- a/Dev Mindshare/README.md +++ b/Dev Mindshare/README.md @@ -10,27 +10,42 @@ This repo shows in 3 steps how to wire Ensue as a persistent memory network for - Starter prompts so first-time users know what to say. ## Prerequisites -- Codex CLI or Claude with MCP support installed. +- Codex CLI or Claude Clode. ## Getting Started -### Step 1: Set the API Key and Add the MCP Server +### Step 1: Download instructions for Codex or Claude Code -Set the API key: +- Claude users: download `CLAUDE.md` into your project directory before starting Claude. +- Codex users: download `AGENTS.md` into your project directory before starting Codex. + +### Step 2: Install Skill (Claude) or add the MCP Server (Codex) + +#### For Claude Code users: + +Start Claude Code and install the Skill. ```bash -export ENSUE_API_KEY="lmn_695bff5b5b6d4bfe82ffaf2ee9c1167c" +/plugin marketplace add https://github.com/mutable-state-inc/ensue-skill +/plugin install ensue-memory ``` -Then add the Ensue MCP server: +Then tell Claude Code which API key to use: -Claude: ```bash -claude mcp add --transport http ensue-memory \ - https://www.ensue-network.ai/api/ \ - --header "Authorization: Bearer $ENSUE_API_KEY" +ENSUE_API_KEY is lmn_695bff5b5b6d4bfe82ffaf2ee9c1167c ``` +#### For Codex users: + +Set the API key: + +```bash +export ENSUE_API_KEY="lmn_695bff5b5b6d4bfe82ffaf2ee9c1167c" +``` + +Then add the Ensue MCP server: + Codex: ```bash codex mcp add ensue-memory \ @@ -38,10 +53,7 @@ codex mcp add ensue-memory \ --bearer-token-env-var ENSUE_API_KEY ``` -### Step 2: Download instructions and start Claude/Codex -- Claude users: download `CLAUDE.md` into your project directory before starting Claude. -- Codex users: download `AGENTS.md` into your project directory before starting Codex. -- Open the project in your agent and start; the file is auto-loaded as high-priority instructions. +Start Codex. ### Step 3: Start coding @@ -73,4 +85,4 @@ Hey, load any Ensue memories for this project and give me a one-line status on w ## Next steps / advanced - Get your own `ENSUE_API_KEY` and swap it into the install commands. The included demo key has restricted permissions; your own key lets you update keys, create private-only memories (e.g., personal front-end preferences), and control visibility per prefix. DM me (https://x.com/christinetyip) or submit this form (https://forms.gle/d4Cg5LEP9scs6XJE6) to get your own personal key. I'll probably try to automate this process later, but for now, you can expect a response within 24 hours. -- Package the core flow as a Skill in Claude or Codex if you want a reusable toggle you can carry across repos or share with teammates. Use it to quickly enable/disable Ensue behaviors without renaming files. +- Subscribe to keys from other developers and receive notifications when the key is updated From b51832614f0fc3f8ce18dd41d63549f520f4efa0 Mon Sep 17 00:00:00 2001 From: christine <40064228+christinetyip@users.noreply.github.com> Date: Thu, 18 Dec 2025 00:19:11 +0100 Subject: [PATCH 2/3] Updated example name --- Dev Mindshare/README.md | 9 ++------- 1 file changed, 2 insertions(+), 7 deletions(-) diff --git a/Dev Mindshare/README.md b/Dev Mindshare/README.md index f707651..721b3cf 100644 --- a/Dev Mindshare/README.md +++ b/Dev Mindshare/README.md @@ -1,4 +1,4 @@ -# Dev Mindshare Example +# Coding Style Example This repo shows in 3 steps how to wire Ensue as a persistent memory network for coding agents (Codex, Claude) so you can get a “memory-first” experience and share/see how other developers think about coding (style, infra decisions, patterns). The notes below explain how to set up, run, and what to say to your agent. @@ -66,17 +66,12 @@ Hey, load any Ensue memories for this project and give me a one-line status on w - “What did you save to Ensue for this project? Any general takeaways or feedback for me?” - "Based on the memories on Ensue, how are others thinking about [infra and aws deployments]?" -## What the agent will do (per `dev-mindshare.md`) +## What the agent will do - On session start: load relevant memories (coding style, preferences, mistakes, architecture, todo, tools, experiments). - During work: automatically store preferences, tool choices, mistakes fixed, decisions, and experiments with structured keys (e.g., `personal/coding-style//`), embedding summaries for search. - Use correct visibility prefixes (`personal/`, `friends/`, `coworkers/`) based on context; defaults to `friends/` unless clearly private (then `personal/`), or explicitly team-shared (`coworkers/`). - If Ensue is unavailable, it will mention that memory is disabled and continue stateless. -## Repo contents -- `AGENTS.md` — Auto-applied instructions for Codex users (copied from `dev-mindshare.md`). -- `CLAUDE.md` — Auto-applied instructions for Claude users (copied from `dev-mindshare.md`). -- `README.md` — This overview and quick-start guide. - ## Tips for a smooth first run - Keep your first task small (“audit the API routes” or “add a new React page”) so you can see memories being created. - Ask: “What did you save to Ensue for this project?” after a few prompts to verify memory is working. From 6a38279d5c593c78615d48771438eb9ac7595a68 Mon Sep 17 00:00:00 2001 From: christine <40064228+christinetyip@users.noreply.github.com> Date: Thu, 18 Dec 2025 00:20:32 +0100 Subject: [PATCH 3/3] Simplified the instructions --- Dev Mindshare/README.md | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/Dev Mindshare/README.md b/Dev Mindshare/README.md index 721b3cf..5bc50e3 100644 --- a/Dev Mindshare/README.md +++ b/Dev Mindshare/README.md @@ -63,21 +63,19 @@ Hey, load any Ensue memories for this project and give me a one-line status on w ``` - After a few prompts after you've started coding, ask Claude or Codex the following to verify it's working: + - “What did you save to Ensue for this project? Any general takeaways or feedback for me?” - "Based on the memories on Ensue, how are others thinking about [infra and aws deployments]?" ## What the agent will do + - On session start: load relevant memories (coding style, preferences, mistakes, architecture, todo, tools, experiments). - During work: automatically store preferences, tool choices, mistakes fixed, decisions, and experiments with structured keys (e.g., `personal/coding-style//`), embedding summaries for search. - Use correct visibility prefixes (`personal/`, `friends/`, `coworkers/`) based on context; defaults to `friends/` unless clearly private (then `personal/`), or explicitly team-shared (`coworkers/`). - If Ensue is unavailable, it will mention that memory is disabled and continue stateless. -## Tips for a smooth first run -- Keep your first task small (“audit the API routes” or “add a new React page”) so you can see memories being created. -- Ask: “What did you save to Ensue for this project?” after a few prompts to verify memory is working. -- If you’re collaborating, decide whether project-level memories should live under `coworkers/` (shared) or stay `personal/` (private). - ## Next steps / advanced + - Get your own `ENSUE_API_KEY` and swap it into the install commands. The included demo key has restricted permissions; your own key lets you update keys, create private-only memories (e.g., personal front-end preferences), and control visibility per prefix. DM me (https://x.com/christinetyip) or submit this form (https://forms.gle/d4Cg5LEP9scs6XJE6) to get your own personal key. I'll probably try to automate this process later, but for now, you can expect a response within 24 hours. - Subscribe to keys from other developers and receive notifications when the key is updated