Skip to content

fix(tools): route file uploads to whole-file binary streaming - #40

Merged
Horcag merged 1 commit into
perf/vm-operation-throughputfrom
perf/whole-file-upload
Oct 24, 2026
Merged

Horcag merged 1 commit into
perf/vm-operation-throughputfrom
perf/whole-file-upload

Conversation

@Horcag

@Horcag Horcag commented Oct 24, 2026

Copy link
Copy Markdown
Owner

Agents can send local file contents through repeated terminal writes, paying command, approval and receipt overhead for each piece. Direct file uploads to the existing whole-file binary guest_put path, and local PowerShell scripts to guest_exec, in MCP descriptions, source schema help, CLI session help and documentation. Runtime behavior and authorization are unchanged.

Validation: schema snapshot, make quality, full unit/race tests, coverage (85.9%), and independent code/security and architecture review. Live validation of the existing installed transport uploaded 64 MiB in 4.95 seconds and 1 GiB in 40.93 seconds of daemon operation time (48.84 seconds for the complete MCP call); the 64 MiB download matched SHA-256, and both guest fixtures were removed with observed absence. These are measurements of the existing binary path, not a throughput change introduced by this description-only patch.

Updated client binaries passed a real stdio tools/list smoke and CLI help readback. The running daemon and existing sessions were preserved.

@Horcag
Horcag merged commit 3bf7566 into perf/vm-operation-throughput Oct 24, 2026
18 of 19 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant