@ory/gemini-cli 0.6.1 → 0.7.0

package/README.md

@@ -19,14 +19,18 @@ In your shell:
 gemini extensions install https://github.com/ory/gemini-cli-extension
 ```
 
-That's it — skills, TOML slash commands, hooks, and the Ory MCP server are now registered.
+Then confirm everything landed:
+
+```bash
+npx -y -p @ory/gemini-cli ory-gemini status
+```
+
+`status` is the single source of truth — it prints configuration, user and agent identity, per-tool permission coverage, extension + skill registration, and a tail of recent debug logs. Unconfigured fields show inline as `(unset)`.
 
 <details>
 <summary>Alternative install paths</summary>
 
 ```bash
-# Direct installer; renders a fresh extension manifest and invokes
-# `gemini extensions install` for you. No prior npm install required.
 npx -y @ory/gemini-cli install
 npx -y @ory/gemini-cli uninstall
 ```
@@ -53,13 +57,13 @@ From any project where you'd like Ory authentication, inside Gemini CLI:
 
 3. **Sign in.** Start your app, visit the login page Gemini added, and sign in with the seeded credentials. You now have a real Ory session backed by a real Ory stack — locally, offline, with zero configuration.
 
-4. **Turn on Ory login for the Gemini session itself.** *(Optional but recommended.)* Out of the box the extension only governs your *app*. To also attach an Ory identity to *Gemini's* session — so every tool call is attributed to you, not a fallback `session:<id>` subject — set:
+4. **Turn on Ory login for the Gemini session itself.** *(Optional but recommended.)* Out of the box the extension only governs your *app*. To also attach an Ory identity to *Gemini's* session — so every tool call is attributed to you, not a fallback `session:<id>` subject — opt in to the user-login flow:
 
    ```bash
-   export ORY_AUTH_GATE=1
+   export ORY_USER_LOGIN=1
    ```
 
-   Then restart Gemini CLI. On next session start, Gemini opens an Ory login in your browser; sign in with the same seeded credentials from step 1. This is what makes `permissions enforce` (see [Agent security](#agent-security)) deny on the right identity later.
+   User login is off by default. With it on, the next Gemini session opens an Ory login in your browser; sign in with the same seeded credentials from step 1, and the token is reused on subsequent sessions until it expires. This is what makes `permissions enforce` (see [Agent security](#agent-security)) deny on the right identity later.
 
 That's the full Ory DX path. Stop here if you're just evaluating the extension. Continue to [Agent security](#agent-security) when you're ready to enforce.
 
@@ -114,7 +118,7 @@ Without configuration the extension still loads cleanly and runs in **pass-throu
 
 Once the extension is pointed at an Ory project (local or hosted), Gemini's session and every tool call can be governed by Ory.
 
-- **Authentication.** Two identities. The human at the keyboard (the **user**) authenticates interactively via Ory Identities when `ORY_AUTH_GATE=1` is set. The Gemini process (the **agent**) gets its own OAuth2 identity, self-registered via [Dynamic Client Registration (RFC 7591)](https://datatracker.ietf.org/doc/html/rfc7591) on first run.
+- **Authentication.** Two identities. The human at the keyboard (the **user**) authenticates interactively via Ory Identities when user login is enabled (`ORY_USER_LOGIN=1`, off by default — browser PKCE flow on first session, persisted token thereafter). The Gemini process (the **agent**) gets its own OAuth2 identity, self-registered via [Dynamic Client Registration (RFC 7591)](https://datatracker.ietf.org/doc/html/rfc7591) on first run.
 - **Authorization.** Before any tool runs, the extension checks [Ory Permissions](https://www.ory.com/docs/keto) (Zanzibar-style relation tuples) against the user's subject and blocks the call on `deny`. MCP tool calls additionally get a server-level check.
 - **Audit.** Every decision (allow, deny, fallback) is recorded as a structured trace span: NDJSON file output and/or OTLP/HTTP export to Jaeger, Honeycomb, Grafana, and similar collectors. The user → agent delegation is written to Ory as a relation tuple so *"agent X acting on behalf of user Y"* stays queryable after tokens expire.
 
@@ -124,10 +128,10 @@ The extension is **fail-open** on its own infrastructure failures (network error
 
 After install the extension runs in **observe mode**: every tool call is checked against Ory Permissions, but a deny is recorded as a `permission.observe_deny` audit span and the tool runs anyway. This lets you see what *would* be blocked before turning on hard blocking.
 
-1. **Turn on the user gate.** In your shell:
+1. **Turn on user login.** It's off by default. In your shell:
 
    ```bash
-   export ORY_AUTH_GATE=1
+   export ORY_USER_LOGIN=1
    ```
 
    The next Gemini session opens a browser for PKCE login. Subsequent sessions reuse the persisted token until it expires.

package/dist/cli/main.js

@@ -186,7 +186,7 @@ function printQuickstart() {
     console.log("Quickstart:");
     console.log("  1. Inside Gemini, run /ory:local-up to start a local Ory stack.");
     console.log("  2. Ask Gemini \"add Ory auth to this app\" to scaffold login/signup.");
-    console.log("  3. Set ORY_AUTH_GATE=1 when you're ready for the PKCE login gate.");
+    console.log("  3. Set ORY_USER_LOGIN=1 to enable the interactive PKCE browser login.");
 }
 async function status() {
     await (0, argus_1.runStatusCommand)("ory-gemini", "gemini-cli", {

package/dist/handlers.d.ts

@@ -1,8 +1,8 @@
 import { OryAgentClient, ensureUserAuthenticated, ensureAgentIdentity } from "@ory/argus";
 import type { GeminiHookInput, GeminiHookOutput } from "./types.js";
 export interface HandleHookEventDeps {
-    /** Test injection point for the user auth gate. */
-    authGate?: typeof ensureUserAuthenticated;
+    /** Test injection point for the user login flow. */
+    userLogin?: typeof ensureUserAuthenticated;
     /** Test injection point for the agent identity gate. */
     agentGate?: typeof ensureAgentIdentity;
 }

package/dist/handlers.js

@@ -55,7 +55,7 @@ async function handleSessionStart(input, client, deps) {
     client.tracer.record("session.start", "ok", {
         attributes: { source: input.source },
     });
-    const userGate = deps.authGate ?? argus_1.ensureUserAuthenticated;
+    const userGate = deps.userLogin ?? argus_1.ensureUserAuthenticated;
     const decision = await userGate(client, {
         binName: "ory-gemini",
         harness: "gemini-cli",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ory/gemini-cli",
-  "version": "0.6.1",
+  "version": "0.7.0",
   "description": "Ory extension for Gemini CLI: scaffolding skills, a local Ory instance, and authentication, authorization, and audit for every tool call",
   "license": "Apache-2.0",
   "homepage": "https://ory.com",
@@ -68,7 +68,7 @@
     "gemini-extension"
   ],
   "dependencies": {
-    "@ory/argus": "0.6.1"
+    "@ory/argus": "0.7.0"
   },
   "engines": {
     "node": ">=22"