briq agent home
The image behind briq_run({ recipe: "agent-home" }) on briq: one person's
computer in the cloud, where they sign in to each vendor's agent CLI with the vendor's own flow,
and their agents run on their own plans.
ghcr.io/briq-cloud/agent-home:latest
The briq sandbox (Ubuntu 24.04, Python, Node.js, git, the
usual tools) plus:
| CLI | Command | Sign-in |
|---|
| Claude Code | claude | claude auth login |
| Codex | codex | codex login --device-auth |
| Copilot CLI | copilot | copilot login --device-code |
| Cursor | agent | NO_OPEN_BROWSER=1 agent login |
| Grok Build | grok | grok login --device-auth |
| Mistral Vibe | vibe | vibe --setup |
| Gemini CLI | gemini | a key only (GEMINI_API_KEY), enforced by its system settings: it serves no consumer plan since June 2026 |
Other providers' keys (the GLM, Kimi, MiniMax and Alibaba coding plans, DeepSeek, OpenRouter) run
on Claude Code or Codex as profiles, added on the runner's page.
and ttyd for a terminal page, and agent-home-runner: it drives the CLIs over ACP for apps and
keeps their sessions while nobody is connected (runner/README.md). Every version, as the last build left them:
REFERENCE.md. Inside a home, agent-home-versions prints the same.
How it is built
- Unmodified binaries, each from the vendor's own release channel.
- Pinned per build. A build takes each CLI's current stable release; a date tag
(
2026-10-27) never moves. latest follows the newest build, every Monday and on every change
here, for linux/amd64.
- Self-update off.
DISABLE_AUTOUPDATER and DISABLE_UPDATES (Claude Code),
/etc/codex/config.toml, COPILOT_AUTO_UPDATE=false, GROK_DISABLE_AUTOUPDATER and
/etc/grok/managed_config.toml, /etc/gemini-cli/settings.json. Cursor and Vibe read theirs
from the user's own config. Gemini's usage statistics are off in its system settings.
- Checked downloads. Each one against its publisher's checksum (Claude Code's manifest, the
GitHub release digests, ttyd's
SHA256SUMS, PyPI's); Cursor and Grok publish none, so their
hashes are recorded. Every sha256 and the base image's digest are in REFERENCE.md.
- Provenance. Each pushed image is attested by this repo's build:
gh attestation verify oci://ghcr.io/briq-cloud/agent-home:<tag> --repo briq-cloud/agent-home.
- No browser. A CLI that opens a link (a sign-in page) calls
xdg-open or $BROWSER; here both
are show-url, which shows the link as plain text in a terminal window of its own.
Sign-ins live where each CLI's variable says (CLAUDE_CONFIG_DIR, CODEX_HOME, COPILOT_HOME,
GROK_HOME, VIBE_HOME, XDG_CONFIG_HOME). On briq they are on the home's volume, which is never
forked or backed up.
Run it elsewhere
docker run --rm -it ghcr.io/briq-cloud/agent-home:latest bash
Build it
docker build -t agent-home .
docker run --rm agent-home agent-home-versions
Links
MIT licensed. The briq service is operated by Uplab SAS under its
terms.
Benchmarks
Small ACP benchmarks: free mock checks and explicit, budgeted provider-key experiments.
