You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Chat uploads resolve by uploads/<name> for reads, sandbox mounts, and image references (never listings or writes); an unresolved reference image fails the call instead of rendering without it; copilot session-sandbox calls are priced like Function-block sandboxes and report the raw cost beside the billed one; CLI docs regenerated
Copy file name to clipboardExpand all lines: apps/docs/content/docs/cli/blocks.mdx
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -39,6 +39,8 @@ sim blocks list [options]
39
39
|`--category <value>`| No | Restrict to one toolbar category. Accepted values: `blocks`, `tools`, `triggers`. |
40
40
|`--capability <value>`| No | Restrict to blocks that can start a workflow — the `triggers` category, blocks declaring `triggerAllowed`, and blocks with trigger-mode fields. Accepted values: `trigger`. |
41
41
|`--source <value>`| No | Restrict to shipped blocks or to this workspace’s deployed custom blocks. Accepted values: `builtin`, `custom`. |
42
+
|`--include-sunset`| No | Include `legacy` and `deprecated` blocks. Off by default: a sunset block keeps executing where it is already placed, but it is not offered for new authoring. Each returned entry carries `sunset.replacedBy`, the block to build with instead. |
43
+
|`--no-include-sunset`| No | Send --include-sunset as false. |
42
44
|`--sort-by <value>`| No | Field used to sort the result. Sorting by `name` is case-sensitive and follows the storage collation, so do not rely on a case-insensitive order. Accepted values: `id`, `name`, `category`. |
Copy file name to clipboardExpand all lines: apps/docs/content/docs/cli/logs.mdx
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -51,6 +51,8 @@ sim logs stats [options]
51
51
|`--folder <value...>`| No | Folder path as shown in the app; the leading / is optional (space-separated, or @path / @- with one value per line; @@value for a literal leading @). |
52
52
|`--trigger <value...>`| No | Comma-separated trigger types to include. An empty entry is rejected. The vocabulary is open, so an unrecognized member selects no runs; the literal `all` disables this filter. (space-separated, or @path / @- with one value per line; @@value for a literal leading @). |
53
53
|`--level <value>`| No | Severity level to include. Accepted values: `info`, `error`. |
54
+
|`--include-handled-errors`| No | Whether runs with a handled block error are counted as `handledErrorRuns`, and whether `level=error` also selects them. Off by default: counting them scans each run’s stored trace. |
55
+
|`--no-include-handled-errors`| No | Send --include-handled-errors as false. |
54
56
|`--start-date <value>`| No | Only include runs started at or after this UTC ISO 8601 timestamp, e.g. `2026-08-06T00:00:00Z`. A date without a time, or a timestamp carrying a UTC offset instead of `Z`, is rejected, as is year `0000`, which names no storable instant. |
55
57
|`--end-date <value>`| No | Only include runs started at or before this UTC ISO 8601 timestamp, e.g. `2026-08-06T00:00:00Z`. A date without a time, or a timestamp carrying a UTC offset instead of `Z`, is rejected, as is year `0000`, which names no storable instant. |
56
58
|`--segment-count <value>`| No | Number of equal time buckets to divide the window into, from 1 to 500. It is the ceiling on how many buckets a series carries: with `includeEmpty=true` exactly this many are returned, otherwise only the buckets holding at least one run. Buckets are never narrower than one minute, so on a short window the series extends past the end of the window rather than being compressed, and the trailing buckets are empty. |
@@ -84,6 +86,8 @@ sim logs list [options]
84
86
|`--include-trace-spans`| No | Include trace spans in JSON or YAML output (implies full detail). |
85
87
|`--include-final-output`| No | Include final output in JSON or YAML output (implies full detail). |
86
88
|`--limit <n>`| No | Maximum items to return (0 for everything). Defaults to `100`. |
89
+
|`--include-handled-errors`| No | Whether `level=error` also selects runs that finished at `info` after a block error was recovered by an error path. Off by default: such a run succeeded, so it is an error only to a caller auditing error handling. Every row reports `hasHandledErrors` whether or not this is set. Job runs carry no block trace, so the flag never widens that branch. |
90
+
|`--no-include-handled-errors`| No | Send --include-handled-errors as false. |
87
91
|`--status <value>`| No | Comma-separated execution statuses to include, from `pending`\|`running`\|`paused`\|`redacting`\|`completed`\|`failed`\|`cancelled`. An empty entry is rejected. ANDed with `level`, which reports severity rather than lifecycle. |
88
92
|`--workflow-name <value>`| No | Case-insensitive substring match against the run's workflow name. Runs whose workflow has been deleted match nothing, because the name is no longer joinable. |
89
93
|`--include-job-runs`| No | Whether Chat and Sim-agent job runs join the sequence alongside workflow runs. Job runs report `kind: "job"`, carry no `workflow` summary, and never carry a cost ledger. They are dropped entirely — not partially matched — whenever a filter they cannot answer is set: by workflow, workflow name, folder, model, or status. A filter therefore never means two different things across the union. Accepted only when sorting by `startedAt`: job runs record cost as a document and no comparable status, so they cannot participate in the other orderings. |
Copy file name to clipboardExpand all lines: apps/docs/content/docs/cli/reference.mdx
+8-2Lines changed: 8 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -310,6 +310,8 @@ sim blocks list [options]
310
310
|`--category <value>`| No | Restrict to one toolbar category. Accepted values: `blocks`, `tools`, `triggers`. |
311
311
|`--capability <value>`| No | Restrict to blocks that can start a workflow — the `triggers` category, blocks declaring `triggerAllowed`, and blocks with trigger-mode fields. Accepted values: `trigger`. |
312
312
|`--source <value>`| No | Restrict to shipped blocks or to this workspace’s deployed custom blocks. Accepted values: `builtin`, `custom`. |
313
+
|`--include-sunset`| No | Include `legacy` and `deprecated` blocks. Off by default: a sunset block keeps executing where it is already placed, but it is not offered for new authoring. Each returned entry carries `sunset.replacedBy`, the block to build with instead. |
314
+
|`--no-include-sunset`| No | Send --include-sunset as false. |
313
315
|`--sort-by <value>`| No | Field used to sort the result. Sorting by `name` is case-sensitive and follows the storage collation, so do not rely on a case-insensitive order. Accepted values: `id`, `name`, `category`. |
|`fileId`| Yes | File identifier, or the file’s VFS path: `files/<folder>/<name>`, or `uploads/<name>` for a Chat upload. |
1001
1003
1002
1004
</CommandTable>
1003
1005
@@ -2441,6 +2443,8 @@ sim logs stats [options]
2441
2443
|`--folder <value...>`| No | Folder path as shown in the app; the leading / is optional (space-separated, or @path / @- with one value per line; @@value for a literal leading @). |
2442
2444
|`--trigger <value...>`| No | Comma-separated trigger types to include. An empty entry is rejected. The vocabulary is open, so an unrecognized member selects no runs; the literal `all` disables this filter. (space-separated, or @path / @- with one value per line; @@value for a literal leading @). |
2443
2445
|`--level <value>`| No | Severity level to include. Accepted values: `info`, `error`. |
2446
+
|`--include-handled-errors`| No | Whether runs with a handled block error are counted as `handledErrorRuns`, and whether `level=error` also selects them. Off by default: counting them scans each run’s stored trace. |
2447
+
|`--no-include-handled-errors`| No | Send --include-handled-errors as false. |
2444
2448
|`--start-date <value>`| No | Only include runs started at or after this UTC ISO 8601 timestamp, e.g. `2026-08-06T00:00:00Z`. A date without a time, or a timestamp carrying a UTC offset instead of `Z`, is rejected, as is year `0000`, which names no storable instant. |
2445
2449
|`--end-date <value>`| No | Only include runs started at or before this UTC ISO 8601 timestamp, e.g. `2026-08-06T00:00:00Z`. A date without a time, or a timestamp carrying a UTC offset instead of `Z`, is rejected, as is year `0000`, which names no storable instant. |
2446
2450
|`--segment-count <value>`| No | Number of equal time buckets to divide the window into, from 1 to 500. It is the ceiling on how many buckets a series carries: with `includeEmpty=true` exactly this many are returned, otherwise only the buckets holding at least one run. Buckets are never narrower than one minute, so on a short window the series extends past the end of the window rather than being compressed, and the trailing buckets are empty. |
@@ -2476,6 +2480,8 @@ sim logs list [options]
2476
2480
|`--include-trace-spans`| No | Include trace spans in JSON or YAML output (implies full detail). |
2477
2481
|`--include-final-output`| No | Include final output in JSON or YAML output (implies full detail). |
2478
2482
|`--limit <n>`| No | Maximum items to return (0 for everything). Defaults to `100`. |
2483
+
|`--include-handled-errors`| No | Whether `level=error` also selects runs that finished at `info` after a block error was recovered by an error path. Off by default: such a run succeeded, so it is an error only to a caller auditing error handling. Every row reports `hasHandledErrors` whether or not this is set. Job runs carry no block trace, so the flag never widens that branch. |
2484
+
|`--no-include-handled-errors`| No | Send --include-handled-errors as false. |
2479
2485
|`--status <value>`| No | Comma-separated execution statuses to include, from `pending`\|`running`\|`paused`\|`redacting`\|`completed`\|`failed`\|`cancelled`. An empty entry is rejected. ANDed with `level`, which reports severity rather than lifecycle. |
2480
2486
|`--workflow-name <value>`| No | Case-insensitive substring match against the run's workflow name. Runs whose workflow has been deleted match nothing, because the name is no longer joinable. |
2481
2487
|`--include-job-runs`| No | Whether Chat and Sim-agent job runs join the sequence alongside workflow runs. Job runs report `kind: "job"`, carry no `workflow` summary, and never carry a cost ledger. They are dropped entirely — not partially matched — whenever a filter they cannot answer is set: by workflow, workflow name, folder, model, or status. A filter therefore never means two different things across the union. Accepted only when sorting by `startedAt`: job runs record cost as a document and no comparable status, so they cannot participate in the other orderings. |
Copy file name to clipboardExpand all lines: apps/docs/openapi-v2-files-audit.json
+9-5Lines changed: 9 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -728,20 +728,19 @@
728
728
"get": {
729
729
"operationId": "readFileText",
730
730
"summary": "Read File Text",
731
-
"description": "Return a file's text content, parsed out of the stored bytes. This reads the file; it writes nothing — `POST /api/v2/files/{fileId}/unzip` is the endpoint that unzips an archive into the workspace. Answers `400` for a type no parser supports, naming the raw-bytes download as the escape hatch, and `413` for a file above the extraction ceiling. A generated document is extracted from its compiled artifact rather than its generation source, so one still compiling answers `409` and is worth retrying. **`degraded: true` means text extraction did not fully succeed and the returned text may be incomplete or synthesized from the file's raw bytes. Do not treat it as authoritative content.** The legacy `.doc` and `.ppt` parsers deliberately return best-effort content rather than failing, so this flag — not an error status — is how a partial extraction is reported. `truncated` separately reports that a parser limit stopped extraction early.",
731
+
"description": "Return a file's text content, parsed out of the stored bytes. `{fileId}` is the file's id or its VFS path (`files/<folder>/<name>`; `uploads/<name>` for a Chat upload, which no listing shows), and the response echoes the canonical `path` that was read. This reads the file; it writes nothing — `POST /api/v2/files/{fileId}/unzip` is the endpoint that unzips an archive into the workspace. Answers `400` for a type no parser supports, naming the raw-bytes download as the escape hatch, and `413` for a file above the extraction ceiling. A generated document is extracted from its compiled artifact rather than its generation source, so one still compiling answers `409` and is worth retrying. **`degraded: true` means text extraction did not fully succeed and the returned text may be incomplete or synthesized from the file's raw bytes. Do not treat it as authoritative content.** The legacy `.doc` and `.ppt` parsers deliberately return best-effort content rather than failing, so this flag — not an error status — is how a partial extraction is reported. `truncated` separately reports that a parser limit stopped extraction early.",
732
732
"tags": ["Files"],
733
733
"parameters": [
734
734
{
735
735
"name": "fileId",
736
736
"in": "path",
737
737
"required": true,
738
-
"description": "File identifier.",
738
+
"description": "File identifier, or the file’s VFS path: `files/<folder>/<name>`, or `uploads/<name>` for a Chat upload.",
739
739
"schema": {
740
740
"type": "string",
741
741
"minLength": 1,
742
-
"maxLength": 128,
743
-
"pattern": "^[A-Za-z0-9_-]+$",
744
-
"description": "File identifier."
742
+
"maxLength": 4096,
743
+
"description": "File identifier, or the file’s VFS path: `files/<folder>/<name>`, or `uploads/<name>` for a Chat upload."
745
744
}
746
745
},
747
746
{
@@ -3357,6 +3356,10 @@
3357
3356
"type": "string",
3358
3357
"description": "File name, including its extension."
3359
3358
},
3359
+
"path": {
3360
+
"type": "string",
3361
+
"description": "Canonical VFS path of the file that was read: `files/…`, or `uploads/<name>` for a Chat upload."
3362
+
},
3360
3363
"type": {
3361
3364
"type": "string",
3362
3365
"description": "Stored MIME type of the source file."
0 commit comments