boxlite-ai/boxlite

What is missing After a sequence of git operations, an agent has to decide what to do next: are there uncommitted changes, what branch is this, how far ahead or behind the remote. The only way to find out is r = await box.exec("git", "status", "--porcelain") and then parse the text. That is the failure mode this surface exists to remove: an agent writing regexes against human-readable output, taking a wrong branch when the parse is wrong. Filenames with spaces or newlines break it outright. The problem compounds with the write side. A clone or push that failed can fail quietly, and with no cheap structured way to check the resulting state, the agent carries on as if it had succeeded. Write operations without matching read operations leave the whole namespace unverifiable. There is no git surface on the SDK at all: sdks/node/src/ holds copy.rs, exec.rs, network.rs, volumes.rs and no git.rs. Proposed usage 1. Structured status st = await box.git.status("/workspace/repo") if st.file_statu

What is missing Committing and pushing work back to a remote is the closing move of any coding agent running in a sandbox, and there is no API for it. Callers assemble git add / git commit / git push through box.exec() themselves, and the push has to repeat the whole -c http.extraHeader="Authorization: Bearer <BOXLITE_SECRET:gh>" incantation that the clone already used, because the credential is not persisted anywhere. Any mistake in that string surfaces as raw git stderr with no typed error to branch on. There is no git surface to hide it behind: sdks/node/src/ holds copy.rs, exec.rs, network.rs, volumes.rs and no git.rs. Committing also gives the caller nothing back. To learn what was committed, they have to exec("git", "rev-parse", "HEAD") and parse the output. Proposed usage 1. Stage, commit, push — no credential re-assembly await box.git.add("/workspace/repo", ["."]) sha = await box.git.commit("/workspace/repo", "fix: handle empty payload") await box.git.push("/workspace/repo",

What is missing Cloning a private repository inside a box requires knowing an obscure git option, and the obvious way of doing it fails silently. BoxLite secrets are a placeholder-substitution model: the box sees <BOXLITE_SECRET:{name}> (src/cli/src/commands/serve/mod.rs:1234) and the real value is substituted on the way out. Substitution applies to headers, not to URLs. So the first thing almost everyone writes — git clone https://user:[email protected]/org/private-repo.git — does not work, and does not obviously say why. The documented correct form is git -c http.extraHeader="Authorization: Bearer <BOXLITE_SECRET:gh>" clone https://... http.extraHeader is not a widely known option, and nothing steers a caller towards it. There is no git surface on the SDK to hide this: sdks/node/src/ holds copy.rs, exec.rs, network.rs, volumes.rs and no git.rs, so the only entry point is box.exec() with a hand-assembled command line. Proposed usage 1. Clone a private repository with a secret, no h

What is missing A fresh box carries no git identity, so the first commit after a developer has already done all the real work fails: *** Please tell me who you are. Run git config --global user.email "[email protected]" ... fatal: unable to auto-detect email address There is no box.git namespace to configure it through. The SDKs expose box.exec() and box.copy_in() / box.copy_out() and nothing else for this — sdks/node/src/ holds copy.rs, exec.rs, network.rs, volumes.rs, with no git.rs, and the Python package has no git module either. So identity has to be hand-carried with exec("git", "config", ...), and nothing tells the caller it is a required step. This issue lands the box.git namespace. It is the smallest member of the git surface, so it is the one that settles the shape: where the handle hangs off Box, how the repository path is passed, how git failures map to typed errors, and how the hand-written Python sync_api mirror wraps it. The sibling issues for clone, commit/push and s

Environment OS / architecture: macOS Apple Silicon; Linux x86_64 / ARM64 (KVM) BoxLite: main @ 783609f (workspace v0.10.0) Steps to reproduce Start a box: boxlite run -d alpine:latest sleep 300 Exec a binary that does not exist: boxlite exec <box_id> -- /nonexistent/binary Observe the error class over REST (boxlite serve / SDK REST path): the request surfaces internal error (code=1) with HTTP 500. Expected: the canonical table (src/shared/src/errors.rs) maps this to ExecutionError — HTTP 422 with execution_failed — so SDKs can act on the type. Actual: internal error: spawn_failed → HTTP 500. Reproduced on 783609f (2026-09-10) CLI rebuilt from the 783609f tree (make cli; the Rust sources are identical to origin/main), then boxlite serve --port 8100 against a real VM: $ curl -X POST localhost:8100/v1/boxes/{box_id}/exec \ -d '{"command":"/nonexistent/binary","args":[],"timeout_seconds":30}' HTTP 500 {"error":{"message":"internal error: spawn_failed: internal error: build fa