Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 18 additions & 0 deletions api/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -94,6 +94,24 @@ Other package-format-compatible runtimes (Go, Rust, Java, GCC) can be installed

Execute code in a sandboxed environment.

When a persisted input file is removed during execution, a complete artifact
scan reports its relative path in `deleted_files`. Callers can use this
explicit list to remove stale file references from their next session request.
The field is omitted when no persisted inputs were removed or when artifact
scanning is incomplete, so truncation or unreadable paths cannot be mistaken
for deletions.

When supported output files are omitted because the response reaches its file
count limit, nesting or path limits, file-size limit, or a filesystem entry
cannot be read, the response includes `artifact_truncation`. Its `reasons`
object counts detected omissions by cause, `skipped_count` reports the total
detected omissions, and `skipped` contains up to 20 relative paths so callers
can match an expected output. Intentional filters such as unsupported file
extensions, hidden runtime directories, and unchanged session files do not
produce this marker when they can be classified within the bounded scan. A
depth-capped subtree that exceeds the metadata probe budget is reported
conservatively rather than allowing post-execution traversal to run unbounded.

### `GET /api/v2/runtimes`

List available language runtimes.
Expand Down
Loading