Skip to content

Add sandboxwire framing for the sandbox protocols - #335

Merged
SaladDay merged 1 commit into
feature/agent-outside-sandboxfrom
aos/sandboxwire
Sep 30, 2026
Merged

SaladDay merged 1 commit into
feature/agent-outside-sandboxfrom
aos/sandboxwire

Conversation

@SaladDay

@SaladDay SaladDay commented Sep 30, 2026 •

Copy link
Copy Markdown
Collaborator

Adds internal/sandboxwire: the 16-byte frame header, strict primitive encoder/decoder (zero-invalid enums, presence bytes, bounded counts, trailing-byte rejection) and the vocabulary shared by the File, Process and Link protocols (ID, Effect).

Part of the agent-outside-sandbox M1 work on feature/agent-outside-sandbox. No protocol uses it yet; the File, Process and Link lanes build on it.

Checks: go test ./internal/sandboxwire, go vet, gofmt, FuzzDecoder 30 s, GOOS=darwin/windows builds.


View with [code]smith Autofix with [code]smith
Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.

@SaladDay
SaladDay merged commit 91e5ca1 into feature/agent-outside-sandbox Sep 30, 2026
1 check passed
The File, Process and Link protocols share one 16-byte frame header,
a primitive encoder and decoder that validates lengths and counts
before allocating, tag classification, and the ID and Effect values
more than one protocol uses. Each protocol's protocol.go owns its own
messages.
@SaladDay
SaladDay deleted the aos/sandboxwire branch October 7, 2026 05:24
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