pasear
Control Paseo agents from Claude, ChatGPT, Gemini, and Grok web chat.
该插件的概览尚未翻译为你的语言,因此以英文显示。
pasear lets web chat control the Paseo agents on your own host through an authenticated MCP server. Start tasks, send follow-up messages, check progress, read conversations and work activity, summarize results, or stop a run. Close or archive agents to tidy the list, or delete a single agent's Paseo record and timeline. Cleanup runs immediately on request, without a second confirmation inside the tool, and does not remove workspace files or revert edits. Supported provider sessions can be recovered, or their history handed to a new agent. Short repeatable waits can watch one or several agents. When an agent needs approval or an answer, the chat can show the request and forward your explicit approval, denial, offered action, selected options, or free-text answer. Unsupported question forms stay in Paseo.
The Paseo screen has connections and logs tabs. Start the MCP listener when needed, manage chat connections, and approve access to selected projects, workspaces, or individual agents. Each host has its own listener, settings, and approvals. Switching hosts in Paseo does not redirect an existing chat connection. The interface is in English; listing screenshots use sample data.
Requires Paseo daemon and app 0.11.2 or later, npm for dependency preparation, and a local paseo CLI for stopping runs, native session import and agent deletion. The CLI and daemon were checked at 0.15.0 on Linux; other operating systems have not been verified. Provide a public HTTPS address through your reverse proxy, load balancer, or Tailscale Funnel. Forward all paths to the listener, including OAuth discovery and authorization. Both the domain root and /mcp accept MCP requests. The default listener is 0.0.0.0:8787; loopback access is available in advanced settings. After a plugin reload, start the listener again.
Connections use OAuth, dynamic client registration, and S256 PKCE. Enter the connection key in the OAuth browser window, then approve the request and allowed targets in Paseo. Access changes and revocation apply without reconnecting. Project or workspace access includes future children; access to individual agents does not permit creating new agents. These limits govern MCP operations, while the coding provider controls its execution sandbox. Native session recovery requires whole-host access and retained provider data. Close follows Paseo's archive behavior; close/archive require whole-host access because they may cascade to child agents. Single-agent deletion respects the connection's allowed targets and does not guarantee erasure of provider-native history. History handoff starts a separate session and does not restore files or branches.
Requested messages and history are sent to the connected web chat; task prompts and handoff context go to the selected coding provider. Work activity omits raw tool input/output and reasoning. Approval requests expose the relevant command/path/plan context and questions to the chat; these can contain sensitive task data. Responses cannot change connection access or arbitrary permission rules. Stale and repeated responses are checked against the pending request. OAuth state stays on the daemon host. Traffic recording is enabled by default, with local retention of 7 days up to 50 MiB. The logs tab supports paging, filtering, export, deletion, and disabling collection. OAuth routes and headers are excluded, and known credentials are redacted; arbitrary secrets in task text may remain. Disabling collection preserves existing logs. Log access is limited to authenticated Paseo management.
Official registration guides for Claude, ChatGPT, Gemini, and Grok were checked on 2026-11-05. The user confirmed Claude OAuth connection and completed live verification of GPT (Codex), Gemini, and Grok on 2026-11-06. Availability depends on the service, account, region, and workspace policy. Like other Paseo plugins, pasear runs as trusted local code.
Paseo has an app-side message queue, but no public API to control it. pasear does not currently support queuing; support is planned when a public API becomes available. For follow-ups after completion, the active chat can wait until the agent is idle and then send the instruction. This is not a durable or atomic queue.


