WorkBuddy × Nowledge Mem

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 run a short session and confirm the thread appears with nmem t list --source workbuddy.

WorkBuddy can use Nowledge Mem through the CodeBuddy-compatible plugin system. The plugin gives WorkBuddy startup context, Mem MCP tools, quick commands, and lifecycle hooks that sync WorkBuddy's local transcript into Mem Threads.

CodeBuddy's release notes document that WorkBuddy uses an independent .workbuddy/ configuration directory, separated from CodeBuddy's .codebuddy/. The Nowledge Mem connector treats WorkBuddy as its own source: nmem t sync --from workbuddy.

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 bundled 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

Add the Nowledge community marketplace, then install the plugin:

/plugin marketplace add nowledge-co/community
/plugin install nowledge-mem@nowledge-community

The marketplace is backed by community/.workbuddy-plugin/marketplace.json. The shared plugin includes:

• a WorkBuddy plugin manifest
• a local MCP server for http://127.0.0.1:14242/mcp/
• startup guidance and a Nowledge Mem skill
• hooks for Stop, SessionEnd, PreCompact, and SubagentStop
• quick commands under /nowledge-mem:*

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

nmem config mcp show --host workbuddy

Paste the generated nowledge-mem server into ~/.workbuddy/.mcp.json, $WORKBUDDY_CONFIG_DIR/.mcp.json, or a project .mcp.json.

Thread Sync

WorkBuddy passes session_id and transcript_path to lifecycle hooks. The Nowledge Mem plugin uses those fields instead of guessing where the latest transcript is.

After install, the hook runs:

nmem --json t sync --from workbuddy --session-id <session-id> --session-dir <transcript_path> --all-projects --apply

That command runs on the WorkBuddy machine, reads the local transcript under $WORKBUDDY_CONFIG_DIR/projects or ~/.workbuddy/projects, and uploads normalized messages to your local or remote Mem server. It is safe to rerun; Mem deduplicates repeated imports.

Verify

Start a new WorkBuddy session and ask:

Is Nowledge Mem connected? Read my current context.

Success means WorkBuddy can call the Nowledge Mem MCP tools and return Context Bundle, Working Memory, or an empty-but-successful memory result.

Then finish a short exchange and check:

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.

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 or ~/.workbuddy/MEMORY.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.

Related

• Connectors overview
• CodeBuddy guide
• Threads
• WorkBuddy: Product page
• CodeBuddy docs: Plugin Reference · Hooks Reference · MCP