warpmetal 0.8.10 → 0.8.11

package/README.md

@@ -386,10 +386,12 @@ ssh -t <alias> claude
 ssh <alias> claude -p '<task>'
 ssh -t <alias> agent
 ssh <alias> agent -p '<task>'
+ssh -t <alias> gemini
+ssh <alias> gemini -p '<task>'
 ```
 
-Install and authenticate Codex, Claude Code, or Cursor CLI inside the
-sandbox first. Provider credentials are sandbox-owned and remain in its
+Install and authenticate Codex, Claude Code, Cursor CLI, or Gemini CLI inside
+the sandbox first. Provider credentials are sandbox-owned and remain in its
 persistent home; WarpMetal does not install these tools, perform their login,
 or receive their credentials.
 
@@ -434,6 +436,14 @@ weaken sandbox forwarding controls to make the IDE connect. Use the supported
 [headless mode](https://cursor.com/docs/cli/headless) with
 `ssh <alias> agent -p '<task>'` instead.
 
+Use the official Gemini CLI [installation guide](https://geminicli.com/docs/get-started/installation/)
+before running `ssh -t <alias> gemini`, or use its documented
+[headless mode](https://geminicli.com/docs/cli/headless/) with
+`ssh <alias> gemini -p '<task>'`. Gemini's optional Docker or Podman sandbox is
+normally unavailable inside the WarpMetal sandbox because no host
+container-engine socket is exposed; run Gemini directly inside the existing
+outer sandbox and choose its approvals yourself.
+
 On the first install in a server trust epoch, JSON output includes
 `hostKeyTrust.state: "trusted_first_use"` and the safe Ed25519 fingerprint.
 Later installs report `"matched"`. First-use trust protects continuity after

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "warpmetal",
-  "version": "0.8.10",
+  "version": "0.8.11",
   "description": "Agent-safe CLI and skill for purchasing, renewing, and managing WarpMetal VPS servers",
   "type": "module",
   "bin": {

package/skills/warpmetal/SKILL.md

@@ -322,8 +322,10 @@ ssh <alias>
 
 The local alias preserves the forced gateway: it cannot open a host shell and
 does not relax forwarding denial. Provider authentication and credentials stay
-inside the sandbox. After an authenticated profile refresh, update the alias
-only with the explicit second confirmation:
+inside the sandbox. Install and authenticate Codex, Claude Code, Cursor CLI, or
+Gemini CLI inside the sandbox; use the entry points and compatibility guidance
+in [references/runtime.md](references/runtime.md). After an authenticated
+profile refresh, update the alias only with the explicit second confirmation:
 
 ```sh
 warpmetal sandbox access refresh \

package/skills/warpmetal/references/cli-reference.md

@@ -300,8 +300,14 @@ ssh -t <alias> claude
 ssh <alias> claude -p '<task>'
 ssh -t <alias> agent
 ssh <alias> agent -p '<task>'
+ssh -t <alias> gemini
+ssh <alias> gemini -p '<task>'
 ```
 
+Install and authenticate Codex, Claude Code, Cursor CLI, or Gemini CLI inside
+the sandbox first. WarpMetal does not install, authenticate, configure, or
+receive credentials for those tools.
+
 [Codex Desktop](https://learn.chatgpt.com/docs/remote-connections) reads
 the concrete alias from `~/.ssh/config` and starts Codex through the sandbox
 login shell, so Codex must be installed and on that login-shell `PATH`. The
@@ -310,6 +316,13 @@ not compatible with this boundary. Keep forwarding denied and use the
 [Cursor CLI](https://cursor.com/docs/cli/overview) interactive or
 [headless](https://cursor.com/docs/cli/headless) commands shown above.
 
+Install Gemini CLI from its official [installation guide](https://geminicli.com/docs/get-started/installation/)
+and use its documented [headless mode](https://geminicli.com/docs/cli/headless/)
+for `gemini -p`. Gemini's optional Docker or Podman sandbox is normally
+unavailable inside the WarpMetal sandbox because no host container-engine
+socket is exposed; run Gemini directly inside the existing outer sandbox and
+choose its approvals yourself.
+
 ## Skill installation and state
 
 ```sh

package/skills/warpmetal/references/runtime.md

@@ -294,11 +294,14 @@ ssh -t <alias> claude
 ssh <alias> claude -p '<task>'
 ssh -t <alias> agent
 ssh <alias> agent -p '<task>'
+ssh -t <alias> gemini
+ssh <alias> gemini -p '<task>'
 ```
 
-Provider authentication and credentials are sandbox-owned and persist only in
-the sandbox home. WarpMetal does not install, authenticate, configure, or
-receive credentials for Codex, Claude Code, or Cursor CLI.
+Install and authenticate Codex, Claude Code, Cursor CLI, or Gemini CLI inside
+the sandbox first. Provider authentication and credentials are sandbox-owned
+and persist only in the sandbox home. WarpMetal does not install, authenticate,
+configure, or receive credentials for those tools.
 
 [Codex Desktop](https://learn.chatgpt.com/docs/remote-connections)
 discovers a concrete alias through `~/.ssh/config`, requires ordinary
@@ -314,6 +317,14 @@ restricted alias. Do not relax forwarding controls. Use the official
 [headless mode](https://cursor.com/docs/cli/headless) with
 `ssh <alias> agent -p '<task>'` instead.
 
+Follow Gemini CLI's official [installation guide](https://geminicli.com/docs/get-started/installation/),
+then use `ssh -t <alias> gemini` interactively or its documented
+[headless mode](https://geminicli.com/docs/cli/headless/) with
+`ssh <alias> gemini -p '<task>'`. Gemini's optional Docker or Podman sandbox is
+normally unavailable inside the WarpMetal sandbox because no host
+container-engine socket is exposed; run Gemini directly inside the existing
+outer sandbox and choose its approvals yourself.
+
 Connect without an owner management credential:
 
 ```sh

package/src/cli.js

@@ -165,6 +165,12 @@ Sandbox SSH aliases:
     ssh <alias> claude -p "<prompt>"
     ssh -t <alias> agent
     ssh <alias> agent -p "<prompt>"
+    ssh -t <alias> gemini
+    ssh <alias> gemini -p "<prompt>"
+
+  Install and authenticate Codex, Claude Code, Cursor CLI, or Gemini CLI inside
+  the sandbox first. WarpMetal does not install, authenticate, configure, or
+  receive credentials for those tools.
 
   Codex Desktop discovers the concrete alias through ~/.ssh/config and opens
   the sandbox login shell, so Codex must be available on the login-shell PATH.
@@ -172,10 +178,17 @@ Sandbox SSH aliases:
   a host shell, and do not relax isolation: ClearAllForwardings yes keeps all
   forwarding disabled.
 
+  Gemini's optional Docker or Podman sandbox is normally unavailable inside
+  the WarpMetal sandbox because no host container-engine socket is exposed;
+  run Gemini directly inside the existing outer sandbox and choose its
+  approvals yourself.
+
   Compatibility references:
     https://learn.chatgpt.com/docs/remote-connections
     https://cursor.com/docs/cli/overview
     https://cursor.com/docs/cli/headless
+    https://geminicli.com/docs/get-started/installation/
+    https://geminicli.com/docs/cli/headless/
 
 Credential environment variables:
   WARPMETAL_OWNER_TOKEN  Recovery/bootstrap credential for one explicit command