workspace_open
Open or reattach to an isolated workspace on a chosen fleet or image. Call explicitly to pick a fleet, image, or guarded fleet; exec, read_file, and write_file attach to it automatically.
Instructions
Open (or reattach to) your isolated workspace on a fleet. exec, read_file and write_file use it automatically, and open one on an unguarded default fleet when none exists, so call this explicitly only to pick a fleet or image, or for a guarded fleet. On a guarded fleet you must first ask the user and get their explicit agreement; only then set confirm to the fleet name.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "workspace_open"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| fleet | No | Fleet name. Omit to use the default. | |
| image | No | Image from the fleet allowlist. Omit for the fleet default. | |
| labels | No | Runner labels the workspace must land on. | |
| confirm | No | Guarded fleets only: the fleet name, set only after the user explicitly agreed. Never set it on your own. | |
| context | No | Context name. Omit to use the default. | |
| credentials | No | Host-mode fleets: narrow the session to these credential names (a subset of those the runner holds). Omit to use all. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| where | Yes | ||
| reused | Yes | ||
| workspace | Yes | ||
| session_source | Yes |