Skip to main content
Nowledge MemNowledge Mem

WorkBuddy × Nowledge Mem

Connect Tencent WorkBuddy to your shared memory with a WorkBuddy plugin, MCP tools, and automatic local thread sync.

For your agent

Paste this into WorkBuddy:

Read https://mem.nowledge.co/SKILL.md and follow the instructions to install or update Nowledge Mem for WorkBuddy. Verify with nmem status and the Context Bundle or Working Memory check, then search for a known memory inside WorkBuddy. Only verify automatic Thread capture when the full plugin and its hooks are installed. In that case, run a short session and check nmem t list --source workbuddy.

WorkBuddy has a dedicated Nowledge Mem connector. It loads current cross-tool context when a session starts, exposes memory and thread tools through MCP, and captures WorkBuddy's exact local transcripts at lifecycle boundaries.

WorkBuddy embeds a CodeBuddy-compatible plugin engine, but it is not a CodeBuddy session. The connector keeps its WorkBuddy MCP identity, .workbuddy/ config root, context source, and nmem t sync --from workbuddy transcript provenance separate.

Before You Start

  • Nowledge Mem is running locally, or you have a reachable remote Mem server
  • WorkBuddy is installed
  • nmem works on the same machine as WorkBuddy
nmem status

If nmem exists but rejects t sync --from workbuddy or config mcp show --host workbuddy, update the CLI before debugging MCP or session sync:

  • Desktop-bundled CLI: open Mem and run Settings → Preferences → Developer Tools → Install CLI again.
  • PyPI CLI: python3 -m pip install --user --upgrade nmem-cli
  • pipx CLI: pipx upgrade nmem-cli

If WorkBuddy runs on a different machine from the Mem desktop app, install the standalone CLI there first and point it at your Mem server:

python3 -m pip install --user nmem-cli
nmem config client set url https://your-server
nmem config client set api-key your-key

Install The Plugin

In desktop WorkBuddy, open Plugins -> +, paste this marketplace address, find Nowledge Mem in nowledge-community, and click Install:

https://raw.githubusercontent.com/nowledge-co/community/main/.workbuddy-plugin/marketplace.json

Enable the plugin and skill, then reload WorkBuddy. Open Connections/MCP and review Trust for nowledge-mem if prompted. Trust is a user security decision; the agent must not approve it silently. These are separate checks from a successful CLI connection.

Use the following only when your host exposes plugin slash commands:

/plugin marketplace add https://raw.githubusercontent.com/nowledge-co/community/main/.workbuddy-plugin/marketplace.json --name nowledge-community
/plugin install nowledge-mem@nowledge-community

Use the raw WorkBuddy marketplace URL exactly as shown. Current WorkBuddy releases check .codebuddy-plugin before .workbuddy-plugin at a repository root, so /plugin marketplace add nowledge-co/community can select the CodeBuddy package instead.

For an ordinary update, choose Update on the installed plugin card and reload. Only migrate after confirming that an old repository-root installation selected the CodeBuddy package instead:

/plugin marketplace remove nowledge-community
/plugin marketplace add https://raw.githubusercontent.com/nowledge-co/community/main/.workbuddy-plugin/marketplace.json --name nowledge-community
/plugin install nowledge-mem@nowledge-community

Removing the old marketplace clears its enabled entry; the final install restores nowledge-mem from the dedicated WorkBuddy package.

The WorkBuddy marketplace sparse-checks out only nowledge-mem-workbuddy-plugin. It includes:

  • a WorkBuddy plugin manifest and WorkBuddy-specific MCP identity
  • a local MCP server for http://127.0.0.1:14242/mcp with exact-v1 Spaces semantics
  • automatic startup context and prior-work routing
  • a Nowledge Mem skill
  • hooks for Stop, SessionEnd, PreCompact, and SubagentStop
  • a hook runner that uses WorkBuddy's managed Node runtime and resolves desktop or standalone nmem installations
  • quick commands under /nowledge-mem:*

For remote Mem or authenticated localhost, generate a WorkBuddy MCP block:

nmem config mcp show --host workbuddy

In desktop WorkBuddy, add or edit nowledge-mem through Connections/MCP, preserving the generated URL and headers, including x-nmem-space-protocol: exact-v1. Review Trust/enable state afterwards. A manually written ~/.workbuddy/.mcp.json does not by itself prove the desktop UI registered the connector; do not edit the installed plugin cache.

If nothing appears after installation, check that nowledge-community is listed, the plugin and skill are enabled, and MCP is trusted. Use the desktop UI if slash commands only produce chat text. If the marketplace still fails, report the WorkBuddy version, OS and add/install error without credentials.

For a temporary manual setup, install the nowledge-mem skill through Skills and register the generated MCP block through Connections. Enable the skill, review Trust and restart. This provides memory tools and guidance, but does not install the plugin's automatic capture hooks. Use the manual history import below until the full plugin is available.

Thread Sync

WorkBuddy passes session_id and transcript_path to lifecycle hooks. The connector uses those exact fields instead of guessing which transcript changed.

With the full plugin and hooks enabled, the hook enqueues capture:

nmem --json t capture --from workbuddy --session-id <session-id> --transcript-path <transcript_path> --sync --all-projects

That command runs on the WorkBuddy machine. An enqueued acknowledgement means durable queue acceptance, not completed upload. The worker imports the transcript under $WORKBUDDY_CONFIG_DIR/projects or ~/.workbuddy/projects into the configured App or Cloud workspace. Check the resulting Thread in Mem; repeated imports deduplicate messages.

For delegated work, current WorkBuddy releases provide the parent session in session_id, the subagent in agent_id, and the delegated transcript in agent_transcript_path. The connector imports that transcript under the subagent's own ID so its message IDs cannot collide with the parent thread.

Hook failures are non-blocking. If Mem or nmem is temporarily unavailable, WorkBuddy continues normally and the connector writes a diagnostic log for later recovery.

Verify

Start a new WorkBuddy session and ask:

Is Nowledge Mem connected? Read my current context.

Success means WorkBuddy can read context and search memories through its enabled, trusted connector. Test a known memory when possible; an empty-but-successful result is valid for a new workspace. With the full plugin installed, SessionStart should also supply context. A terminal nmem doctor alone does not verify this desktop path.

If you installed the full plugin and its hooks, finish a short exchange and check automatic capture:

nmem t list --source workbuddy -n 5

You should see the recent WorkBuddy thread after the hook has run. If hooks do not appear to run, check:

tail -n 50 ~/.workbuddy/logs/nowledge-mem-hook.log

If you set WORKBUDDY_CONFIG_DIR, check that directory's logs/nowledge-mem-hook.log instead.

For the manual skill-plus-MCP setup, context and memory search confirm the connection. It has no automatic capture hooks; use the manual import commands below if you want to save past sessions.

Import Older Sessions

Preview first:

nmem t sync --from workbuddy --limit 20

Import when the preview looks right:

nmem t sync --from workbuddy --apply

For a custom WorkBuddy config directory:

WORKBUDDY_CONFIG_DIR="$HOME/.my-workbuddy-config" nmem t sync --from workbuddy --apply

Customize Behavior

Use WorkBuddy's own instruction surfaces when available:

  • ~/.workbuddy/CODEBUDDY.md for personal global guidance
  • project CODEBUDDY.md for shared workspace guidance
  • .workbuddy/rules/*.md for structured project rules

Do not edit installed plugin files. Marketplace updates can replace them.

On this page