Paseo
Connect Nowledge Mem to the AI tools that Paseo launches, then give durable Paseo agent roles their own Mem identity.
Paseo runs coding agents such as Claude Code, Codex, Copilot, OpenCode, and Pi on your own machine.
Nowledge Mem should connect to those launched AI tools. Paseo is the orchestration layer: it decides which worker runs, while the launched tool owns MCP, hooks, and transcript files.
Paseo's own MCP tools are for orchestration, such as creating agents or worktrees. Keep using them if you like. They do not replace the Nowledge Mem connector inside the launched AI tool, and they do not automatically capture every transcript for Mem.
What You Need
- Nowledge Mem is running on the machine where Paseo starts agents.
- The AI tools Paseo launches are already connected to Mem, such as Codex, Claude Code, OpenCode, or Pi.
- You know which Paseo agents are durable roles, not one-off tasks.
First Useful Setup
Connect the launched AI tool first. For example, if Paseo starts Codex, install and verify the Codex connector. If it starts Pi, install and verify the Pi package.
If a Paseo agent represents a stable role, create one Mem AI Identity:
nmem agents upsert cindy \
--name "Cindy" \
--default-space onboarding \
--instructions "Help with onboarding. Explain one step at a time."Then pass the identity into that launched child runtime:
NMEM_AGENT_ID=cindyLeave NMEM_AGENT_ID unset for one-off advisors, short-lived implementation agents, and generic provider presets. Those can still use Mem through the child tool connector; they just do not need a named identity.
Keep Source App Honest
Do not label every child session as paseo.
Use the launched AI tool as source_app:
- Paseo starts Codex:
source_app=codex - Paseo starts Claude Code:
source_app=claude-code - Paseo starts OpenCode:
source_app=opencode - Paseo starts Pi:
source_app=pi
This keeps thread filters, icons, and capture paths correct. The Mem AI Identity is the worker's long-term role; the source app is the tool that actually produced the transcript.
What Syncs
Supported child-tool sessions sync in two ways.
While You Work
Automatic new-thread capture comes from the connector installed in the launched AI tool.
If Paseo starts Codex, install the Codex connector. If Paseo starts Claude Code, install the Claude Code connector. If Paseo starts OpenCode or Pi, install those packages. Paseo can run those tools, but Paseo itself does not provide a Mem hook that fires after every child turn.
Backfill Older Paseo Agents
Older Paseo-managed sessions can be imported from Paseo's local agent registry:
nmem t sync --from paseo --all-projects --applyThat command reads Paseo's agent records, finds supported child sessions, and imports the real child transcript. Imported threads keep the child source, such as codex, claude-code, opencode, or pi; they are not labeled as paseo.
The import is safe to rerun. Paseo-guided sync uses the same child thread id as direct child-tool sync, so a Codex session imported through Paseo still lands on the same codex-* thread instead of creating a second paseo-* copy.
Paseo's terminal activity, schedules, and chat rooms are separate. Nowledge Mem can import them directly only if Paseo later exposes message-level transcript export, API, or hook data for those surfaces.
What Success Looks Like
Inside the AI tool launched by Paseo, run:
nmem --json context --source-app codexUse the matching source app for the launched tool. If the child runtime received NMEM_AGENT_ID=cindy, the Context Bundle should show Cindy's identity and default space.
From a normal terminal, pass the identity explicitly:
nmem --json context --agent-id cindy --source-app codex