Skip to main content
Connectors
Orchestrator

Paseo

Multi-agent orchestration setup: connect the AI tool Paseo launches, import supported child-session history, then give durable Paseo agent roles a Mem AI Identity.

Start with the setup prompt or connection guide. Open the guide for detailed steps.

Agent shortcut

Ask your agent to set it up

Copy the setup prompt. Your agent will open this guide, use the recommended path, and verify the setup.

How Paseo Connects

Paseo launches Claude Code, Codex, Copilot, OpenCode, or Pi agents on your own machine. Nowledge Mem connects at that launched AI tool layer.

That means the Codex connector still owns Codex thread capture, the Claude Code connector still owns Claude Code capture, the Pi package still owns Pi capture, and the OMP plugin still owns OMP capture. Paseo decides which worker runs; the child tool decides which new activity Mem can capture automatically.

For older sessions, Mem can read Paseo's local agent registry and import supported child transcripts:

Command
nmem t sync --from paseo --all-projects --apply

Imported threads keep the real child source and child thread id, such as codex, claude-code, opencode, pi, or omp. You can rerun the command safely; it deduplicates against the same child thread instead of creating a second paseo copy.

Minimal Setup

Connect each AI tool Paseo launches. If a Paseo agent is a durable role, pass a Mem AI Identity into that child runtime:

Command
NMEM_AGENT_ID=cindy

Leave NMEM_AGENT_ID unset for one-off agents, ad-hoc advisors, or generic provider presets.

Keep source_app as the launched AI tool, such as codex, claude-code, opencode, or pi. Do not label every child session as paseo.

Paseo's terminal activity, schedules, and chat rooms are separate. Mem can import those directly only after Paseo exposes message-level transcript export, API, or hook data for those surfaces.

More Orchestrator Connectors