1
0
forked from jason/echo
Files
chorus/README-gretchen.md
T
2026-06-26 20:05:47 -05:00

67 lines
2.5 KiB
Markdown

# ECHO Memory — install guide (Gretchen)
This is your personal build of the ECHO Memory plugin: **`echo-memory-1.4.2-gretchen.plugin`**.
Your vault owner name, endpoint, and API key are already **baked in** — you don't need a
config file or to paste a key anywhere. Just install it and go.
- **Owner:** Gretchen Friedrich
- **Endpoint:** `https://imprintapi.mpm.to`
- **Backend:** Obsidian Local REST API (verified reachable + your key authenticates ✅)
---
## Install
### In CoWork (recommended)
1. Open the plugins panel.
2. Upload / add the file **`echo-memory-1.4.2-gretchen.plugin`**.
3. Enable **echo-memory** if it isn't on automatically.
4. Start a new session — the skill loads on its own.
### In Claude Code (desktop / CLI)
1. Save the `.plugin` file somewhere local.
2. Add it through your plugin manager (the `.plugin` file is a standard plugin package).
3. Restart your session so the plugin is picked up.
No `~/.claude/echo-memory/config.json` needed — the baked build carries everything.
---
## Verify it's working
Run either:
- **`/echo-doctor`** — checks Python, your endpoint, that your key authenticates, and
whether the vault is bootstrapped. All green = you're set.
- **`/echo-load`** — loads your memory context for the session.
If the vault hasn't been set up yet, `/echo-doctor` will say the marker is absent — that's
expected on a brand-new vault and just means a one-time bootstrap is needed.
---
## Day-to-day
| You want to… | Command |
|---|---|
| Pull in your context at the start of a session | `/echo-load` |
| Save something durable (fact, decision, preference) | `/echo-save` |
| Recall a topic + its linked notes | `/echo-recall <topic>` |
| File a quick capture for later sorting | `/echo-triage` |
| Reflect on a session and capture takeaways | `/echo-reflect` |
You can also just talk naturally — ask Claude to "remember" something or "what do we know
about X" and it'll route to the right place.
---
## Keep in mind
- **This file contains your vault key.** Don't forward the `.plugin` to anyone else or post
it in a shared channel — it grants access to your vault under your name.
- **Updating / rotating your key:** you can't edit a baked build. If your token changes,
ask Jason for a fresh build, then reinstall.
- **Trouble connecting?** Run `/echo-doctor` first — it pinpoints whether it's the endpoint,
the key, or the vault. If the endpoint is unreachable, confirm Obsidian + the Local REST
API plugin are running on the host serving `imprintapi.mpm.to`.