Nowledge Mem — Bub Plugin

Bring your cross-tool knowledge into Bub, and share what you learn in Bub with every other tool.

Bub records every session through its tape system. This plugin connects Bub to your personal knowledge graph in Nowledge Mem — so decisions from Claude Code, preferences from Cursor, and insights from ChatGPT are all searchable inside Bub. And what you learn in Bub flows back to every other tool.

Install

pip install nowledge-mem-bub

Prerequisite: nmem CLI must be in your PATH:

pip install nmem-cli    # or: pipx install nmem-cli
# Arch Linux: yay -S nmem-cli  # or: paru -S nmem-cli
nmem status             # verify connection

Verify

uv run bub hooks        # should list nowledge_mem for system_prompt, build_prompt, save_state
uv run bub run "what was I working on this week?"

If you have existing knowledge in Nowledge Mem, the agent should find it through mem.search.

Tools

All tools work as Bub comma commands too: ,mem.search query=...

Bundled skill: The nowledge-mem skill teaches the agent when and how to use these tools effectively.

Bounded thread reads

Search memories or threads first, then choose the specific conversation and message range needed. Call mem.thread or nmem --json t show at most once per question, using a small message limit (for example 8) and a content limit of 1200 where supported. A known target range may use a nonzero offset once.

Never loop over offsets to reconstruct a conversation. Do not raise --content-limit to compensate for a slow or incomplete read. Small output limits do not guarantee cheap server-side work on every deployed backend. If a read is slow, incomplete, fails or times out, stop, report the evidence gap, and refine the search rather than retrying pages. A later explicit user request for another range is a new bounded read; a routine “continue” is not permission to drain the thread.

Configuration

No config needed for local use. The plugin reads ~/.nowledge-mem/config.json and environment variables automatically.

Customize without editing the plugin

Bub does not currently expose a dedicated user-owned instruction file through this package.

• Use Bub's own runtime prompt or configuration surface if you need extra behavior guidance.
• Keep connection and lane behavior in shared config or env vars.
• Do not patch the installed Bub plugin files directly.

Remote Access

// ~/.nowledge-mem/config.json
{
  "apiUrl": "https://your-server",
  "apiKey": "your-key"
}

Or use environment variables (NMEM_API_URL, NMEM_API_KEY), which override the config file.

Two Modes

Most users should start with the default.

If one Bub process naturally belongs to one project or agent lane, set NMEM_SPACE="Research Agent" before launch. All CLI-backed Context Bundle, search, save, and thread commands will then stay in that lane. Legacy NMEM_SPACE_ID still works for older setups.

Bub is process-scoped today: if you run multiple Bub agents that need different memory lanes, give each process its own NMEM_SPACE (or keep them on Default). Shared spaces, default retrieval, and agent guidance still come from Mem's shared /spaces profile.

Troubleshooting

nmem not found: Install with pip install nmem-cli or pipx install nmem-cli.

Plugin not loading: Run uv run bub hooks and check that nowledge_mem appears in the hook list.

Server not running: Start the Nowledge Mem desktop app, or run nmem status for diagnostics.

Links

• Documentation
• Discord
• GitHub

Made with care by Nowledge Labs