Read configured sandbox process logs by ID - #623
Merged
Conversation
tonywok
force-pushed
the
ts/configured-sandbox-background-logs
branch
from
August 27, 2026 21:02
16bd2e5 to
d85b9a8
Compare
tonywok
force-pushed
the
ts/configured-sandbox-background-logs
branch
from
August 27, 2026 21:06
d85b9a8 to
a9e3724
Compare
kylekthompson
approved these changes
Aug 28, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds support for fetching configured background process logs using the same interface as adhoc sandbox background processes.
Landing this ahead of landing agent support.
AI Summary
Summary
Adds support for reading configured sandbox background-process logs through their existing
logsId.When the sandbox agent returns a
logsId, the CLI:/api/logs/:logsId/download./api/logs/:logsIdwith--follow.Responses without
logsIdcontinue using the existing SSH and file-backed log behavior. If both a log ID and file paths are present, the log ID takes precedence.Testing
go fmt ./...golangci-lint run ./...go test ./...go build ./cmd/rwxAlso tested end to end with a locally compiled CLI
--followoutput