memorylake
MemoryLake integrations for coding agents
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Check it deeper on your machine
It has changed since its scan on 18 Nov 2026.
As a Claude Code plugin, install it and then ask Claude Code:
/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/memorylake-ai/memorylake-harness with scanskillsafety
Or from a terminal, clone it and run it:
git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/memorylake-ai/memorylake-harness'
It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.
Badge for your README
Markdown
[](/listings/memorylake-ai--memorylake-harness)HTML
<a href="/listings/memorylake-ai--memorylake-harness"><img src="/api/listings/memorylake-ai--memorylake-harness/badge.svg" alt="findsafeskills safety rating" /></a>Install
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
.claude-plugin/marketplace.json · Manifest · 14 lines
- {
- "name": "memorylake",
- "description": "MemoryLake integrations for coding agents",
- "owner": {
- "name": "MemoryLake"
- },
- "plugins": [
- {
- "name": "memorylake",
- "source": "./claude-plugin",
- "description": "Cross-device long-term memory for Claude Code, backed by MemoryLake"
- }
- ]
- }
README.md · README · 155 lines · 2 findings marked
- <p align="center">
- <a href="https://memorylake.ai">
- <img src=".github/assets/readme-hero.png" alt="MemoryLake Harness — Plug long-term memory into your agents. Works with Claude Code, Codex, DeepSeek Harness, opencode, QwenPaw, QwenWork and WorkBuddy" width="100%">
- </a>
- </p>
- Client-side harnesses that connect coding agents to
- [MemoryLake](https://memorylake.ai) — cross-device long-term memory.
- (Two deployments, separate accounts: [memorylake.ai](https://memorylake.ai)
- international, [memorylake.cn](https://memorylake.cn) China; the CLI defaults
- to the international endpoint.)
- | Harness | Client | Status |
- | --- | --- | --- |
- | [`claude-plugin/`](claude-plugin/) | Claude Code | working — recall on read, sync on write, session status |
- | [`codex-plugin/`](codex-plugin/) | Codex | working — recall skill, per-turn memory sync, session status |
- | [`dsh-plugin/`](dsh-plugin/) | DeepSeek Harness (dsh) | working — memory tools, prompt guidance, session status; published as `@memorylake/dsh-plugin` |
- | [`opencode-plugin/`](opencode-plugin/) | opencode | working — memory tools, prompt guidance, compaction guidance; published as `@memorylake/opencode-plugin` |
- | [`qwenpaw-plugin/`](qwenpaw-plugin/) | QwenPaw | working — memory backend plugin: automatic recall, memory tools, Console form, `/memorylake-status`; installs from a zip |
- | [`qwenwork-plugin/`](qwenwork-plugin/) | QwenWork | working — search-first reminder every turn, per-turn conversation sync, session status; the QwenWork agent installs it from this repo |
- | [`workbuddy-plugin/`](workbuddy-plugin/) | WorkBuddy | working — search-first recall every turn (reminder + gate), per-turn conversation sync, session status; installs from this repo as a plugin marketplace |
- | [`workbuddy-connector/`](workbuddy-connector/) | WorkBuddy | built, awaiting listing — CLI + Skill connector for WorkBuddy's connector market: sign-in page, CLI install and upgrade, skills for recall, memory and access; recall is up to the agent |
- <p align="center">
- <img src=".github/assets/readme-agents.png" alt="All your agents flow into one MemoryLake: Claude Code, Codex, DeepSeek Harness, opencode, QwenPaw, QwenWork and WorkBuddy around a single MemoryLake" width="100%">
- </p>
- All harnesses share one identity and data tree (`~/.memorylake/harness/`):
- configure once, use from every client.
- Every harness drives the [`memorylake` CLI](https://github.com/memorylake-ai/memorylake-cli)
- under the hood and fetches it on demand during setup, so none of the installs
- below needs a separate download. Put the CLI on your `PATH` to reach the same
- memory from a terminal or a script — see [From the terminal](#from-the-terminal).
- ## Claude Code
- ```
- /plugin marketplace add memorylake-ai/memorylake-harness
- /plugin install memorylake@memorylake
- /memorylake:init
- ```
- See [`claude-plugin/README.md`](claude-plugin/README.md) for configuration,
- privacy notes, and design rationale.
- ## Codex
- ```
- codex plugin marketplace add memorylake-ai/memorylake-harness
- codex plugin add memorylake@memorylake
- set up memorylake
- ```
- The last line is asked inside a Codex session, after trusting the hooks via
- `/hooks`. See [`codex-plugin/README.md`](codex-plugin/README.md).
- ## DeepSeek Harness (dsh)
- ```
- dsh plugin --profile web add @memorylake/dsh-plugin
- dsh web
- /memorylake-init
- ```
- The last line is typed in a session; machines already set up for Claude Code
- or Codex can skip it. See [`dsh-plugin/README.md`](dsh-plugin/README.md).
- ## opencode
- ```
- opencode plugin @memorylake/opencode-plugin -g
- set up memorylake
- ```
- The last line is typed in a session; machines already set up for another
- harness can skip it. See [`opencode-plugin/README.md`](opencode-plugin/README.md).
- ## QwenPaw
- ```
- qwenpaw plugin install https://github.com/memorylake-ai/memorylake-harness/releases/download/qwenpaw-plugin-v0.2.2/memory-memorylake-0.2.2.zip
- ```
- Then, per Agent, in the Console: Agent settings → Memory backend → Memory
- Lake. On a machine already set up for another harness the form can stay
- empty. See [`qwenpaw-plugin/README.md`](qwenpaw-plugin/README.md).
- ## QwenWork
- In a QwenWork conversation, send:
- ```
- Install the MemoryLake plugin by following qwenwork-plugin/INSTALL.md in https://github.com/memorylake-ai/memorylake-harness
- ```
- The agent installs the plugin and runs the setup; machines already set up
- for another harness skip the setup. **Agents installing into QwenWork: follow
- [`qwenwork-plugin/INSTALL.md`](qwenwork-plugin/INSTALL.md)** -- the plugin is
- that directory, not the repository root. See
- [`qwenwork-plugin/README.md`](qwenwork-plugin/README.md).
- ## WorkBuddy
- In WorkBuddy: Skills → Plugins → **+** (add marketplace) →
- `memorylake-ai/memorylake-harness`, install **memorylake**, then in a session:
- ```
- /memorylake:init
- ```
- Machines already set up for another harness can skip the last step. See
- [`workbuddy-plugin/README.md`](workbuddy-plugin/README.md).
- WorkBuddy also gets a **connector** for its connector market:
- [`workbuddy-connector/`](workbuddy-connector/), awaiting listing. Connecting
- it installs the CLI, opens a page to sign in to MemoryLake, and adds skills
- for recall, memory and access control. Unlike the plugin it has no hooks, so
- nothing is searched or synced automatically: the agent runs the CLI when the
- skills tell it to. The two work together. The plugin does the automatic
- recall and sync, the connector provides the sign-in from WorkBuddy's
- connector list and explicit management of workspaces, files and access, and
- its recall skill steps aside when the plugin is installed. Both use the same
- CLI login on a machine. See
- [`workbuddy-connector/README.md`](workbuddy-connector/README.md).
- ## From the terminal
- The harnesses log in through the CLI and keep the credentials where the CLI
- keeps them (`~/.memorylake/credentials.toml`), so a CLI you install yourself on
- a machine already set up for any harness is logged in from the first command:
- ```bash
- curl -fsSL https://raw.githubusercontent.com/memorylake-ai/memorylake-cli/main/scripts/install.sh | sh
- Note: Pipes a downloaded script directly into a shell (curl | sh / wget | bash)
- Line 134 on GitHub
- memorylake auth status
- memorylake lib upload ./report.pdf
- memorylake search "what did we decide about the schema"
- ```
- Windows: `irm https://raw.githubusercontent.com/memorylake-ai/memorylake-cli/main/scripts/install.ps1 | iex`.
- Note: Runs a downloaded PowerShell script (iex / Invoke-Expression)
- Line 140 on GitHub
- The full command reference — files, facts, databases, conversations, agents,
- skills, teams — is in the
- [memorylake-cli README](https://github.com/memorylake-ai/memorylake-cli#commands).
- ## Beyond coding sessions
- The memory the harnesses write to is the same one a team's calls, meetings,
- documents and agents can land in.
- [memorylake-usecases](https://github.com/memorylake-ai/memorylake-usecases)
- has runnable demos of that — sales calls, meetings, a codebase, contract review,
- bookkeeping, agent bug replay, Reflexion-style agent memory and more — each a
- directory with sample data, a CLI runner that prints every command, a local web
- UI and a recorded run. A machine set up for any harness can run them as is: the
- demos use the CLI the harness installed and, with `MEMORYLAKE_API_KEY` unset, its
- login.
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.