pasear

Control your Paseo agents from Claude, ChatGPT, Gemini, or Grok web chat. Start tasks, send follow-ups, check progress, and summarize results.

Korean · Detailed guide

Install

Requires Paseo daemon and app 0.11.2+, plugins enabled, npm, and the local paseo CLI.

Environment checked 2026-11-05: Paseo CLI/daemon 0.15.0, Node.js 24.21.0, npm 11.19.0. Language, library versions and verification details.

paseo plugin add tkfka1/pasear

Or find pasear in Paseo's plugin directory. Registry installs use the reviewed release and can lag behind GitHub. To install GitHub release v0.14.0 directly:

paseo plugin add git:tkfka1/pasear --ref v0.14.0

Update an existing installation with paseo plugin update paseo-mcp-plugin. For a direct Git installation, use paseo plugin update paseo-mcp-plugin --ref v0.14.0 to select this release. After updating, start the MCP server again; saved settings and approved connections are retained.

Open pasear in the Paseo sidebar, then choose one connection method below.

Related MCP server: AKIMCP

Option 1 · External proxy

1. Route a public HTTPS domain, such as https://mcp.example.com, to the Paseo host's HTTP port 8787 using your load balancer or reverse proxy.

2. In pasear, use 0.0.0.0:8787 when the proxy is on another machine, or 127.0.0.1:8787 when it is on the same host.

3. Enter the HTTPS domain in the public MCP URL field, then save and start the server.

Forward all paths to the listener, including /, /mcp, /oauth/*, /.well-known/*, /authorize, /register, /token, and /revoke. Preserve paths and the Authorization header.

Option 2 · Tailscale Funnel

On the Paseo host, install and sign in to Tailscale, then run:

tailscale funnel --bg http://127.0.0.1:8787

Complete the Funnel enablement steps if prompted. Copy the displayed https://<machine>.<tailnet>.ts.net URL into pasear's public MCP URL field, select 127.0.0.1:8787 in advanced settings, then save and start the server.

Funnel exposes the service publicly over HTTPS; Tailscale Serve alone is private to your tailnet. See the official Funnel guide.

Connect your chat

Open your chat service in a browser and add a custom MCP connection:

Official setup guides for all four services checked 2026-11-05. GPT (Codex), Gemini, and Grok: live verification completed by the user on 2026-11-06. See the verification details.

1. Enter the same public HTTPS URL with the name pasear. A domain-only URL works; /mcp also works. Use OAuth with automatic client registration (DCR); leave client ID, client secret and custom request headers unset.

2. Enter pasear's connection key in the OAuth browser window.

3. In pasear's connections tab, verify the code and callback URL, select allowed projects, workspaces, or agents, and approve.

4. Enable pasear in chat (Claude: + → Connectors; ChatGPT: install the plugin and select @pasear; Gemini: select the app or use @pasear), then ask: “Show my current tasks” or “Tell the login agent to run tests and summarize the result.”

Menus and availability depend on your account, region and workspace policy. If the menu is missing, see the linked official guide. Each Paseo host needs its own public URL and approval. After a plugin reload, start the server again.

Wait for results

Ask “Tell the login agent to run tests, wait until it finishes, then summarize the result.” The chat can call wait_for_agent repeatedly without asking you to check progress manually:

{"agentId":"<agent ID>","timeoutSeconds":15,"pollIntervalSeconds":2}

Each call uses at most 20 seconds of polling/summary time (default 15), reserving time for a final message read. It stops at idle, closed, error, or a pending permission request. The response includes the observed state, lastMessageSummary (an excerpt of up to 1,000 characters for the chat to summarize), and timedOut. On timeout, the chat should call again with the same ID; permission requests can be answered in chat through respond_to_agent or in Paseo. Idle does not prove success, and the excerpt may be from a previous turn or unavailable.

To watch several tasks, pass agentIds instead of agentId (up to 10). The first finish/permission observed in a polling round is returned; ties use input order. Continue with remainingAgentIds to collect the others. Repeated tool calls depend on the chat client continuing the conversation; this does not send background notifications. Tool details

When a task asks for approval or an answer, the chat shows the pending request and choices. Say “Approve that”, “Deny it”, “Choose the second option”, or give a text answer. respond_to_agent forwards your explicit decision, including multi-select answers when supported, then the chat can resume waiting. Request IDs and fingerprints are handled by the chat. Unsupported or oversized forms stay in Paseo. Response details

Send now or after completion

send_agent_prompt already supports both public modes: behavior="steer" (default) forwards to the active turn when supported, falling back to interrupting/replacing it; behavior="interrupt" interrupts/replaces it directly. Idle agents start a new turn. Neither mode waits for the current task to finish.

Paseo's app has a message queue, but no public API to control it is available yet. pasear does not currently support message queuing; support is planned once a public API is available.

For now, for “when this finishes, run tests”, the chat can repeat wait_for_agent until idle, check the outcome, then call send_agent_prompt. Handle permission/error/closed separately. This requires an active chat and is not a durable or atomic enqueue operation; another sender may start a turn between calls. Exact provider delivery timing has not been measured. Verified behavior and limits

Clean up agents

Say “Close the login agent”, “Archive that task”, or “Delete that agent and its Paseo history”. Each tool takes only agentId (an ID or exact unique title) and executes immediately, without another confirmation step:

Close/archive require whole-host access because Paseo may cascade the operation to descendants, including children invisible to scoped connections. Scoped connections can still delete an allowed agent or use the existing cancel_agent to stop its run. No access rules are broadened. Cleanup does not remove workspace files/branches or revert edits; deletion does not guarantee erasure of provider-native history. Recovery and implementation details

The logs tab provides paged traffic logs and an option to disable collection. Logs default to on and retain up to 7 days / 50 MiB; known credentials are redacted, but task text can contain sensitive data.

MIT