Skip to content
Back to search

memorylake

MarketplaceWorks with Claude CodeGitHub

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.

Checked today

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
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/memorylake-ai--memorylake-harness/badge.svg)](/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
  1. {
  2. "name": "memorylake",
  3. "description": "MemoryLake integrations for coding agents",
  4. "owner": {
  5. "name": "MemoryLake"
  6. },
  7. "plugins": [
  8. {
  9. "name": "memorylake",
  10. "source": "./claude-plugin",
  11. "description": "Cross-device long-term memory for Claude Code, backed by MemoryLake"
  12. }
  13. ]
  14. }
README.md · README · 155 lines · 2 findings marked
  1. <p align="center">
  2. <a href="https://memorylake.ai">
  3. <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%">
  4. </a>
  5. </p>
  6. Client-side harnesses that connect coding agents to
  7. [MemoryLake](https://memorylake.ai) — cross-device long-term memory.
  8. (Two deployments, separate accounts: [memorylake.ai](https://memorylake.ai)
  9. international, [memorylake.cn](https://memorylake.cn) China; the CLI defaults
  10. to the international endpoint.)
  11. | Harness | Client | Status |
  12. | --- | --- | --- |
  13. | [`claude-plugin/`](claude-plugin/) | Claude Code | working — recall on read, sync on write, session status |
  14. | [`codex-plugin/`](codex-plugin/) | Codex | working — recall skill, per-turn memory sync, session status |
  15. | [`dsh-plugin/`](dsh-plugin/) | DeepSeek Harness (dsh) | working — memory tools, prompt guidance, session status; published as `@memorylake/dsh-plugin` |
  16. | [`opencode-plugin/`](opencode-plugin/) | opencode | working — memory tools, prompt guidance, compaction guidance; published as `@memorylake/opencode-plugin` |
  17. | [`qwenpaw-plugin/`](qwenpaw-plugin/) | QwenPaw | working — memory backend plugin: automatic recall, memory tools, Console form, `/memorylake-status`; installs from a zip |
  18. | [`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 |
  19. | [`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 |
  20. | [`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 |
  21. <p align="center">
  22. <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%">
  23. </p>
  24. All harnesses share one identity and data tree (`~/.memorylake/harness/`):
  25. configure once, use from every client.
  26. Every harness drives the [`memorylake` CLI](https://github.com/memorylake-ai/memorylake-cli)
  27. under the hood and fetches it on demand during setup, so none of the installs
  28. below needs a separate download. Put the CLI on your `PATH` to reach the same
  29. memory from a terminal or a script — see [From the terminal](#from-the-terminal).
  30. ## Claude Code
  31. ```
  32. /plugin marketplace add memorylake-ai/memorylake-harness
  33. /plugin install memorylake@memorylake
  34. /memorylake:init
  35. ```
  36. See [`claude-plugin/README.md`](claude-plugin/README.md) for configuration,
  37. privacy notes, and design rationale.
  38. ## Codex
  39. ```
  40. codex plugin marketplace add memorylake-ai/memorylake-harness
  41. codex plugin add memorylake@memorylake
  42. set up memorylake
  43. ```
  44. The last line is asked inside a Codex session, after trusting the hooks via
  45. `/hooks`. See [`codex-plugin/README.md`](codex-plugin/README.md).
  46. ## DeepSeek Harness (dsh)
  47. ```
  48. dsh plugin --profile web add @memorylake/dsh-plugin
  49. dsh web
  50. /memorylake-init
  51. ```
  52. The last line is typed in a session; machines already set up for Claude Code
  53. or Codex can skip it. See [`dsh-plugin/README.md`](dsh-plugin/README.md).
  54. ## opencode
  55. ```
  56. opencode plugin @memorylake/opencode-plugin -g
  57. set up memorylake
  58. ```
  59. The last line is typed in a session; machines already set up for another
  60. harness can skip it. See [`opencode-plugin/README.md`](opencode-plugin/README.md).
  61. ## QwenPaw
  62. ```
  63. qwenpaw plugin install https://github.com/memorylake-ai/memorylake-harness/releases/download/qwenpaw-plugin-v0.2.2/memory-memorylake-0.2.2.zip
  64. ```
  65. Then, per Agent, in the Console: Agent settings → Memory backend → Memory
  66. Lake. On a machine already set up for another harness the form can stay
  67. empty. See [`qwenpaw-plugin/README.md`](qwenpaw-plugin/README.md).
  68. ## QwenWork
  69. In a QwenWork conversation, send:
  70. ```
  71. Install the MemoryLake plugin by following qwenwork-plugin/INSTALL.md in https://github.com/memorylake-ai/memorylake-harness
  72. ```
  73. The agent installs the plugin and runs the setup; machines already set up
  74. for another harness skip the setup. **Agents installing into QwenWork: follow
  75. [`qwenwork-plugin/INSTALL.md`](qwenwork-plugin/INSTALL.md)** -- the plugin is
  76. that directory, not the repository root. See
  77. [`qwenwork-plugin/README.md`](qwenwork-plugin/README.md).
  78. ## WorkBuddy
  79. In WorkBuddy: Skills → Plugins → **+** (add marketplace) →
  80. `memorylake-ai/memorylake-harness`, install **memorylake**, then in a session:
  81. ```
  82. /memorylake:init
  83. ```
  84. Machines already set up for another harness can skip the last step. See
  85. [`workbuddy-plugin/README.md`](workbuddy-plugin/README.md).
  86. WorkBuddy also gets a **connector** for its connector market:
  87. [`workbuddy-connector/`](workbuddy-connector/), awaiting listing. Connecting
  88. it installs the CLI, opens a page to sign in to MemoryLake, and adds skills
  89. for recall, memory and access control. Unlike the plugin it has no hooks, so
  90. nothing is searched or synced automatically: the agent runs the CLI when the
  91. skills tell it to. The two work together. The plugin does the automatic
  92. recall and sync, the connector provides the sign-in from WorkBuddy's
  93. connector list and explicit management of workspaces, files and access, and
  94. its recall skill steps aside when the plugin is installed. Both use the same
  95. CLI login on a machine. See
  96. [`workbuddy-connector/README.md`](workbuddy-connector/README.md).
  97. ## From the terminal
  98. The harnesses log in through the CLI and keep the credentials where the CLI
  99. keeps them (`~/.memorylake/credentials.toml`), so a CLI you install yourself on
  100. a machine already set up for any harness is logged in from the first command:
  101. ```bash
  102. 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
  103. memorylake auth status
  104. memorylake lib upload ./report.pdf
  105. memorylake search "what did we decide about the schema"
  106. ```
  107. Windows: `irm https://raw.githubusercontent.com/memorylake-ai/memorylake-cli/main/scripts/install.ps1 | iex`.
  108. The full command reference — files, facts, databases, conversations, agents,
  109. skills, teams — is in the
  110. [memorylake-cli README](https://github.com/memorylake-ai/memorylake-cli#commands).
  111. ## Beyond coding sessions
  112. The memory the harnesses write to is the same one a team's calls, meetings,
  113. documents and agents can land in.
  114. [memorylake-usecases](https://github.com/memorylake-ai/memorylake-usecases)
  115. has runnable demos of that — sales calls, meetings, a codebase, contract review,
  116. bookkeeping, agent bug replay, Reflexion-style agent memory and more — each a
  117. directory with sample data, a CLI runner that prints every command, a local web
  118. UI and a recorded run. A machine set up for any harness can run them as is: the
  119. demos use the CLI the harness installed and, with `MEMORYLAKE_API_KEY` unset, its
  120. login.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.