feat(cli): manage workspace scripts (#1992)
* feat(cli): manage workspace scripts * docs: document workspace script management --------- Co-authored-by: Mohamed Boudra <boudra.moha@gmail.com>
This commit is contained in:
co-authored by
Mohamed Boudra
parent
21597bdc1b
commit
21404fbdec
+13
-1
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: MCP reference
|
||||
description: Reference for the Paseo tools agents use to manage agents, workspaces, terminals, and schedules.
|
||||
description: Reference for the Paseo tools agents use to manage agents, workspaces, scripts, terminals, and schedules.
|
||||
nav: MCP reference
|
||||
order: 33
|
||||
category: Orchestration
|
||||
@@ -55,6 +55,18 @@ MCP does not expose an agent-detach tool. Detaching is a manual user action in t
|
||||
|
||||
For worktree isolation, `create_workspace` accepts the same useful choices as the app: branch off from a base, check out an existing branch, or check out a pull request. The worktree remains an implementation detail of the workspace lifecycle.
|
||||
|
||||
### Workspace scripts
|
||||
|
||||
These tools manage scripts configured in a workspace's `paseo.json`. Each requires an explicit `workspaceId`; start and stop also require the configured `scriptName`.
|
||||
|
||||
| Tool | Function |
|
||||
| ------------------------ | --------------------------------------------------------------------------------------- |
|
||||
| `list_workspace_scripts` | List configured scripts with lifecycle, terminal, port, proxy URL, and health metadata. |
|
||||
| `start_workspace_script` | Start a configured script through Paseo's managed launcher. |
|
||||
| `stop_workspace_script` | Stop a running script through its supervised terminal. |
|
||||
|
||||
See [Git worktrees](/docs/worktrees#scripts-and-services) for `paseo.json` configuration.
|
||||
|
||||
### Terminals
|
||||
|
||||
| Tool | Function |
|
||||
|
||||
Reference in New Issue
Block a user