Geckobox CLI
Geckobox runs Claude Code, Codex and other CLI agents on your computers and in sandboxes and tracks the jobs in a local dashboard
- 69 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- The agent starts on remote machines and in sandboxes with permission prompts skipped and runs commands on its own
- The Claude Code subscription token is forwarded to the machines where the agent runs and gives access to your account
Install
- Works in
Manual install
npm install -g github:migasrias2/geckoboxThe package installs from the repo. Then openspaces ui opens the dashboard. Sandboxes on macOS 26 need brew install container.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The agent starts on remote machines and in sandboxes with permission prompts skipped and runs commands on its own
- The Claude Code subscription token is forwarded to the machines where the agent runs and gives access to your account
This is third-party code. Review the repository files before installing.
What it does
Geckobox installs as an npm package and its command is `openspaces`. It starts a CLI agent in the background on a computer you pick: this machine, any machine over SSH, a Docker or Podman container, a Cua sandbox or an isolated Linux VM on your Mac. Each agent turn runs headless in its own work folder and the session id is saved, so the next message resumes the same conversation. `openspaces ui` opens a dashboard on `127.0.0.1` behind a random token: bots on the left, the conversation in the middle, the agent computer live on the right. You can take the screen over by clicking and typing for the agent. `openspaces run --on local,mini,docker:ci` runs one job on several computers and shows results side by side. A TypeScript SDK is included: `startThread`, `openThread`, `fanOut`. `openspaces sandbox create dev` makes a sandbox in about twenty seconds: a lightweight VM on Apple's container runtime or a Docker or Podman container, with the agent running as an unprivileged user. Adapters exist for `claude-code`, `codex`, `gemini`, `opencode` and `shell`; `claude-code` and `shell` are tested live.
Who it is for. Developers with a Mac mini, a VPS or several laptops who want to send Claude Code jobs to different machines and watch them from one screen.
Good fit when
- A long job should run on a Mac mini in the next room while the laptop is closed
- The same test suite has to run on three machines with the results compared
- The agent needs an isolated sandbox where it can do anything inside and nothing outside
- You want a live view of the agent browser screen and the option to take control
- You need a TypeScript script that starts agents through `startThread` and waits for the result
Not a fit when
- The agent must not be Claude Code: the codex, gemini and opencode adapters follow the docs and are not tested live
- Machines cannot be opened over SSH or containers: Geckobox has no relay
- The job needs a confirmation at every step: in a sandbox the agent runs with permission prompts skipped
- You need a cloud service with support and an account: Geckobox is local
Example request
Add the computer mini over SSH to openspaces and start Claude Code on it with the job of upgrading dependencies and running testsLimitations
- Of the five adapters, `claude-code` and `shell` are tested live; the rest follow CLI docs and await fixes.
- In a sandbox the agent runs with permission prompts skipped: inside the box it can do anything, outside nothing.
- Claude Code login is forwarded to a sandbox as `CLAUDE_CODE_OAUTH_TOKEN` or `ANTHROPIC_API_KEY`: the token comes from your shell or the macOS Keychain and travels over stdin.
- Isolated VMs on a Mac need macOS 26 and Apple `container`; other systems need Docker or Podman.
How to disable. `openspaces close <id>` stops a thread and deletes its work folder. Sandboxes are removed with the `openspaces sandbox` commands, the package with `npm uninstall -g openspaces`, and the token in the Keychain is cleared through `openspaces secrets`.
FAQ
How do I install Geckobox?
Run `npm install -g github:migasrias2/geckobox`: the package installs straight from the repository. Then `openspaces ui` opens the dashboard.
Is an account required?
No. Geckobox reaches your computers directly with no relay, so there are no meters or account. The agent still needs its own login.
Which computers can I connect?
This machine, any machine over SSH, a Docker or Podman container and a Cua sandbox. Geckobox creates sandboxes on your Mac itself.
How is it protected from other websites?
The dashboard listens only on `127.0.0.1`, needs the random token from the link and rejects other hosts, so other websites cannot drive it.
How do I run one job on several machines?
With `openspaces run --on local,mini,docker:ci "job"`: it starts the job everywhere at once and shows results side by side.
Discussion
No questions or reviews yet.
Related
CLI toolsgroundcrew hands Linear and Jira tasks to local Claude Code, Codex and Cursor agents, each in its own worktree and sandbox
A CLI that keeps Claude Code agents running around the clock in PTY sessions, steered from Telegram, a dashboard and cron.
A self-hosted control plane for running several agents: task dispatch, run review, spend tracking, connected via MCP, CLI or REST
Connects Claude Code, Cursor, Codex or OpenCode to Telegram, Slack and Discord: teammates message a bot, an agent replies
Orchestrator for Claude Code, Codex and Gemini CLI: YAML workflows that loop until your own quality gates pass
A Rust CLI for macOS: an agent reads any app's interface through the accessibility tree and clicks, types and scrolls by element refs, with no screenshots
README in short
The README compares the project with the paid Cua Spaces service and walks a tour: the job, computers, live view, taking over control and running everywhere. Install, a ten-line SDK, sandboxes, how threads work, the agent list and CLI commands with options follow.