Repository navigation
put the sandbox backends in a package of their own, with the protocol to run one as a service - #187
Merged
Merged
Conversation
… to run one as a service @proxy/backends holds what backends/sandbox held in the api, so that the internal repo can import it through its submodule: the contract, the conformance tests, the temp-dir backend, now with its root given, a client for a backend run as a service elsewhere (remote.ts) and what puts any backend behind that protocol (serve.ts). The protocol is in @proxy/contracts/sandbox: one route per method, a bearer token, errors as the api's kinds. The conformance tests run the temp-dir backend through server and client too. The api picks its backend from SANDBOX_BACKEND: off, remote with the service's address and token, or dev, the temp-dir backend, which only a development server takes. bun install also brought the lockfile's entry for the desktop package up to its package.json, which #176 changed without it.
hkonsti
force-pushed
the
hkonsti/sandbox-backends
branch
from
November 4, 2026 23:12
f9bf743 to
a03c77d
Compare
…nly what every backend does agentOS ends a command's background processes with the command, so the conformance test that left one running across a sleep asked for more than the contract promises; the contract says so now, and the test is gone.
…mised agentOS answers an aborted command with none of its output, so the conformance test no longer asks for what a stopped command wrote; the contract says it is kept where the backend can.
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.
@proxy/backendstakes over whatbackends/sandboxheld in the api (#185), so that the internal repo can import it through its submodule and run hosted Personal Agent Proxy's sandbox service on the same contract and tests:backend.ts,conformance.tsandtemp-dir.tsas before, the temp-dir backend now taking its root directory.@proxy/contracts/sandbox: the protocol, one route per method of the contract, a bearer token, errors as the api's kinds with their statuses.remote.ts: a backend reached over that protocol. What the service says went wrong comes back as the api's kind; a service out of reach is a provider out of reach.serve.ts: any backend behind the protocol, as a request handler forBun.serve. The conformance tests run the temp-dir backend through server and client as well.The api reads
SANDBOX_BACKENDasoff,remote(withSANDBOX_SERVICE_URLandSANDBOX_SERVICE_TOKEN) ordev(the temp-dir backend, which only a development server takes, since it runs commands on the machine with no isolation). Nothing consumes the chosen backend yet; the Sandboxes integration is next. The image, the Blueprint's build filter and compose carry the new package and variables.bun installalso brought the lockfile's entry for the desktop package up to itspackage.json, which #176 changed without it; the frozen install evidently doesn't flag workspace manifests.