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

If you previously added the repository root, migrate once:

/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/
• 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

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 connector uses those exact fields instead of guessing which transcript changed.

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.

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 the SessionStart hook provides current context and WorkBuddy can call Nowledge Mem MCP tools. An empty-but-successful memory result is valid for a new Mem workspace.

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 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 · Release notes
• Tencent hook reference: Hooks