luxcode

A coding agent in a Luxor sandbox, one command away. Run Claude Code, Codex or any of 26 coding agents in a box of their own: one command makes the box, starts the agent and drops you in. Close the laptop and it keeps working. Pick it up again from your phone. Let it run with approvals off, in a box that is nobody's machine.

lux               # pick an agent (or create one) and jump into it
lux claude        # your Claude Code agent, reachable from claude.ai/code
lux codex         # Codex
lux crush         # or copilot, gemini, qwen, goose, kimi, omp, adal, hermes, openclaw
lux opencode-web  # a web UI instead: opencode-web, open-webui, hermes-web, openclaw-web, durable-pi
lux grok          # a box from a Luxor image: grok, amp, droid, pi, prime-agent, tinyfish, anchor, hotdata

Install (macOS and Linux; needs the Luxor CLI and jq):

curl -fsSL https://luxcode.org/install.sh | sh
tenki login
lux

One bash script. The command is lux; the Luxor CLI it drives is still the tenki command (Luxor is tenki.cloud's new name). The same script is also published as colincode: curl -fsSL https://colincode.org/install.sh | sh installs it as colin, with its config in ~/.config/colincode and COLINCODE_* in place of LUX_*. The command's own name picks the brand; build-site.sh renders the site for either.

The harnesses come from agentcamp (fifteen terminal agents and five web UIs) plus Luxor's eight pre-built images (Grok Build, Amp, Droid, Pi, Prime Agent, TinyFish, Anchor, Hotdata).

Why this exists

The Luxor CLI (still the tenki command; Luxor is tenki.cloud's new name) already has every primitive (create, ssh, resume, exec), and the Luxor base image already ships Claude Code, Codex and opencode. What it lacks is the glue:

• no single command that does create-or-resume → wait → launch the agent → attach
• nothing auto-resumes a paused box — every command just fails against one
• no way to point an agent at a different inference provider without editing config files inside the box

You never create or resume a box by hand. Run any lux command and the box is simply there: made if it does not exist yet, woken if it was paused, waited for if it is still starting. A paused box costs you a few seconds, not an error.

Agents

An agent is a name plus a harness, an inference provider and a model. Each agent gets its own sandbox named after it. lux with no arguments shows your agents in an arrow-key menu, plus "new agent", which walks through:

1. Terminal or web — a terminal agent in tmux that you attach to over ssh, or a web UI served from the box and tunnelled to your browser
2. Harness — one of the terminal agents, Luxor's pre-built images, or the web UIs below
3. Provider — the harness default (its own sign-in or in-app setup), or one of the providers below
4. Model — the provider's recommended coding models, or type an id
5. Size — small 2 vCPU/4 GiB · medium 4/8 (default) · large 8/16 · xlarge 12/32 · xxlarge 16/64
6. Volume — a persistent volume (10/25/50 GiB, or none; Luxor workspaces cap volumes, 50 GiB on ours) mounted at ~/work. The agent starts there. It survives pause, rm and a box resize; the root disk does not.
7. Name — leave empty for the harness name on its default provider (claude, opencode-web, tinyfish), or <provider>-<harness> on a third-party one (nebius-crush, openrouter-opencode-web)

lux <harness> picks your only agent for that harness, offers a menu if you have several, or starts the creation flow if you have none. lux <name> targets a specific agent. Agents live in ~/.config/luxcode/agents/.

Usage

lux                        pick an agent (or create one) and jump into it
lux new [cli|web|harness]  create an agent: terminal or web → harness → provider → model → size → volume → name
lux <harness> [action]     a harness (see Harnesses): your agent for it, or a new one
lux <agent> [action]       a specific agent by name

up        (default)  create or resume the box, start the agent, attach
ssh                  same as up (attach to the running agent)
shell                plain shell in the box
run -- <prompt>      one-shot headless prompt
status               agent, provider, box state
provider             switch inference provider (and model)
model [id]           switch model
size [name]          box size; applies when the box is (re)created
volume [GiB|none]    add or drop the persistent volume at ~/work
url [off]            a public Luxor link: the web UI, or a browser terminal on a terminal agent
                     (anyone with the link gets in — share it like a password); off removes it
auth                 sign in / store or replace the provider key
down | pause         pause the box (auto-resumed next time)
rm | stop | kill     terminate the box; the volume is kept and `lux <name>` brings the agent
                     back on it (rm --purge deletes the volume too)

lux image [build [--full]] the golden image new boxes start from (see Golden image)
lux ls                     list agents and their boxes, and kept volumes
lux volumes                every volume: which agent is on it, kept ones, strays
lux volumes rm <name|id>   delete a volume for good (confirmed by name)
lux pause --all            pause every agent's box
lux rm --all               terminate every box and forget every agent

All three harnesses run inside tmux, so they survive SSH disconnects and sandbox pauses. lux <agent> attaches you to that session every time; detach with Ctrl-b d and the agent keeps running.

여기까지가 README 앞부분입니다. 나머지는 원문에서 읽을 수 있습니다. README 전문 보기 ↗