Skip to content

fix(runtime): provision missing CLIs in Docker SOPs - #1077

Open
crispinhu27 wants to merge 2 commits into
mainfrom
fix/antigravity-workspace-launch
Open

crispinhu27 wants to merge 2 commits into
mainfrom
fix/antigravity-workspace-launch

Conversation

@crispinhu27

Copy link
Copy Markdown
Collaborator

Summary

  • Resolve the selected CLI on the Docker task user's PATH first. Reuse shared runtime installations where available and prepare missing CLIs with the same installer used by conversation workspaces.
  • Serialize installation in each container so parallel SOP nodes can share the installed CLI. Explicit executor paths and ordinary script tasks keep their existing launch arguments.
  • Download the complete Antigravity or Cursor installer over verified HTTPS before executing it. Retry one failed download and pass the sandbox's configured proxy to CLI setup.

Writable Docker sandboxes with the installer prerequisites can provision the supported CLIs. Read-only images can use a preinstalled CLI or mounted toolchain. ZCode uses the supplied official CLI.

Verification

  • Runtime installation, proxy, and retry regression tests with the Go race detector.
  • Disposable Linux arm64 Docker sandbox with a numeric user installed official Antigravity and Pi on demand, reused both on the next invocation, and ran the existing Codex binary.
  • End-to-end Runner SOP with a missing Antigravity CLI installed a test fixture and completed with a synthetic API key.
  • Runner SOP and conversation authentication regressions on native and Docker sandboxes.

Use the sandbox proxy for Docker CLI setup and retry a failed HTTPS download before invoking the official installer.
Reuse the conversation workspace installer after checking the sandbox PATH and shared runtime installations.
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