Kimi Work × Nowledge Mem

Read https://mem.nowledge.co/SKILL.md and follow the instructions to install or update Nowledge Mem for Kimi Work. Verify with nmem status and the Context Bundle or Working Memory check, then summarize what changed.

Kimi Work can use Nowledge Mem through the Kimi Work connector. It installs a session-start skill and local MCP declaration into Kimi Work's embedded Kimi Code runtime, which is separate from any Kimi Code CLI you installed yourself.

Kimi Work does not expose lifecycle hooks today. That means Mem can give Kimi Work context and memory tools, but conversation import is explicit: preview and run nmem t sync --from kimi-work --apply when you want Kimi Work history in Mem Threads.

Before You Start

• Nowledge Mem is running locally, or you have a reachable remote Mem server
• Kimi Work Desktop is installed
• nmem 0.9.23 or newer works on the same machine as Kimi Work

nmem status
nmem --version

If Kimi Work runs on a different machine from the desktop app, install the standalone CLI there first:

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

Install The Connector

Get the community checkout if you do not already have it:

git clone --depth 1 https://github.com/nowledge-co/community.git ~/.cache/nowledge-community

Install into Kimi Work's embedded runtime:

python3 ~/.cache/nowledge-community/nowledge-mem-kimi-work-connector/scripts/install_kimi_work_plugin.py

The installer uses KIMI_WORK_HOME when set. Otherwise it uses the default macOS Kimi Work runtime path:

~/Library/Application Support/kimi-desktop/daimon-share/daimon/runtime/kimi-code/home

Restart Kimi Work after installing.

Remote Mem Or Authenticated Localhost

The connector bundles a local MCP server for the desktop app at http://127.0.0.1:14242/mcp/.

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

nmem config mcp show --host kimi-work

Paste the generated nowledge-mem server into $KIMI_WORK_HOME/mcp.json, or into the default runtime path shown above plus /mcp.json.

Restart Kimi Work after changing MCP config.

Verify

Start a new Kimi Work session and ask:

Is Nowledge Mem connected? Read my current context.

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

Import Kimi Work Sessions

Preview first:

nmem t sync --from kimi-work --limit 20

Import when the preview looks right:

nmem t sync --from kimi-work --apply
nmem t list --source kimi-work -n 5

This works for local Mem and remote Mem because the nmem CLI reads Kimi Work's local transcript files and uploads normalized thread messages to your configured Mem server. It is safe to rerun; Mem uses stable thread and message IDs to deduplicate repeated imports.

If Kimi Work stores sessions somewhere else, pass the runtime sessions folder explicitly:

nmem t sync --from kimi-work --session-dir "/path/to/kimi-work/home/sessions" --apply

Kimi Work vs Kimi Code

Kimi Code CLI and Kimi Work share the same underlying Kimi Code session format, but they do not share the same home directory.

• Use Kimi Code when you run the terminal or IDE coding agent. It supports a hook installer for automatic local thread sync.
• Use this Kimi Work guide for Kimi Work Desktop. It has MCP and startup guidance, but no lifecycle hook, so thread import is explicit.

Related

• Connectors overview
• Import existing conversations
• Kimi Code