docs(orchestration): explain cross-provider workflows (#2062)
This commit is contained in:
+26
-14
@@ -1,14 +1,18 @@
|
||||
---
|
||||
title: Paseo MCP
|
||||
description: Paseo MCP tools injected into agents.
|
||||
nav: Paseo MCP
|
||||
order: 30
|
||||
title: MCP reference
|
||||
description: Reference for the Paseo tools agents use to manage agents, workspaces, terminals, and schedules.
|
||||
nav: MCP reference
|
||||
order: 33
|
||||
category: Orchestration
|
||||
---
|
||||
|
||||
# Paseo MCP
|
||||
# MCP reference
|
||||
|
||||
Paseo can inject these MCP tools into every new agent it launches. Turn on **Inject Paseo tools** in host settings, or set `daemon.mcp.injectIntoAgents` to `true`.
|
||||
This is the complete catalog behind the workflows in [Orchestration](/docs/orchestration) and [Common workflows](/docs/orchestration-workflows). You normally ask for an outcome in natural language and let the agent choose the tools.
|
||||
|
||||
Paseo can inject these tools into every new agent it launches. Open **Settings → your host → Agents** and turn on **Enable Paseo tools**, or set `daemon.mcp.injectIntoAgents` to `true`.
|
||||
|
||||
Depending on the provider, Paseo delivers the catalog through its native tool interface or MCP. The capabilities are the same either way.
|
||||
|
||||
The MCP server itself is controlled by `daemon.mcp.enabled`. Existing agents may need a reload.
|
||||
|
||||
@@ -29,6 +33,15 @@ The MCP server itself is controlled by `daemon.mcp.enabled`. Existing agents may
|
||||
| `get_agent_activity` | Return recent agent timeline entries as a curated summary. |
|
||||
| `set_agent_mode` | Switch an agent's session mode. |
|
||||
|
||||
### Workspaces and worktrees
|
||||
|
||||
| Tool | Function |
|
||||
| ------------------ | ----------------------------------------------------------------------------- |
|
||||
| `rename_workspace` | Change the user-visible name of the current or specified workspace. |
|
||||
| `list_worktrees` | List Paseo-managed git worktrees for a repository. |
|
||||
| `create_worktree` | Create a Paseo-managed git worktree from a branch, base branch, or GitHub PR. |
|
||||
| `archive_worktree` | Delete a Paseo-managed git worktree. |
|
||||
|
||||
### Terminals
|
||||
|
||||
| Tool | Function |
|
||||
@@ -44,10 +57,13 @@ The MCP server itself is controlled by `daemon.mcp.enabled`. Existing agents may
|
||||
| Tool | Function |
|
||||
| ------------------ | ----------------------------------------------------------------- |
|
||||
| `create_schedule` | Create a recurring schedule that runs on an agent or a new agent. |
|
||||
| `create_heartbeat` | Send a recurring prompt back into the current agent. |
|
||||
| `list_schedules` | List schedules managed by the daemon. |
|
||||
| `inspect_schedule` | Inspect a schedule and its run history. |
|
||||
| `pause_schedule` | Pause an active schedule. |
|
||||
| `resume_schedule` | Resume a paused schedule. |
|
||||
| `update_schedule` | Change the cadence, prompt, limits, or other schedule settings. |
|
||||
| `schedule_logs` | Return recent runs and output for a schedule. |
|
||||
| `delete_schedule` | Delete a schedule permanently. |
|
||||
|
||||
### Providers
|
||||
@@ -58,14 +74,6 @@ The MCP server itself is controlled by `daemon.mcp.enabled`. Existing agents may
|
||||
| `list_models` | List models for an agent provider. |
|
||||
| `inspect_provider` | Inspect compact provider capabilities and draft feature settings. |
|
||||
|
||||
### Worktrees
|
||||
|
||||
| Tool | Function |
|
||||
| ------------------ | ----------------------------------------------------------------------------- |
|
||||
| `list_worktrees` | List Paseo-managed git worktrees for a repository. |
|
||||
| `create_worktree` | Create a Paseo-managed git worktree from a branch, base branch, or GitHub PR. |
|
||||
| `archive_worktree` | Delete a Paseo-managed git worktree. |
|
||||
|
||||
### Permissions
|
||||
|
||||
| Tool | Function |
|
||||
@@ -73,6 +81,10 @@ The MCP server itself is controlled by `daemon.mcp.enabled`. Existing agents may
|
||||
| `list_pending_permissions` | Return pending permission requests across agents. |
|
||||
| `respond_to_permission` | Approve or deny a pending permission request. |
|
||||
|
||||
### Browser
|
||||
|
||||
Browser automation is opt-in and adds tools for opening tabs, reading pages, clicking, typing, and taking screenshots. See the [Browser tools reference](/docs/browser-tools).
|
||||
|
||||
### Voice
|
||||
|
||||
| Tool | Function |
|
||||
|
||||
Reference in New Issue
Block a user