@ory/pi 0.13.9 → 0.14.0

package/README.md

@@ -27,12 +27,14 @@ Then run one command. It installs the plugin and walks you through connecting:
 npx -y -p @ory/pi ory-pi install
 ```
 
-The installer drops a tiny loader at `<project>/.pi/extensions/ory.js` so Pi discovers the plugin, adds the Ory skills under `<project>/.pi/skills`, and then asks how you want to connect — **press Enter for the default**:
+The installer drops a tiny loader at `<project>/.pi/extensions/ory.js` so Pi discovers the plugin, adds the Ory skills under `<project>/.pi/skills`, and then opens a guided setup **in your browser** where you pick how to connect — the default takes just a click:
 
 - **Ory Network** *(default)* — sign in, or create a free account, in your browser. The project, keys, permissions, and login are all set up for you. Nothing to configure by hand.
 - **Local** — run a complete Ory on your laptop with Docker. No account, no signup, no keys. Great for trying it out.
 - **Audit-only** — skip Ory entirely and just log what Pi does.
 
+> No browser available (CI, SSH, headless)? The same walkthrough runs right in your terminal instead — or force it with `--no-web`.
+
 That's it. Confirm everything landed with:
 
 ```bash
@@ -73,6 +75,7 @@ If Ory is ever unreachable, the plugin gets out of the way and lets Pi keep work
 Everything the plugin does is observable out of the box — no configuration required:
 
 - **Status at a glance.** `npx -y -p @ory/pi ory-pi status` shows what's configured, who's signed in, how many built-in tools your permissions cover, and the most recent tool-call activity.
+- **Live dashboard.** `npx -y -p @ory/pi ory-pi dashboard` opens the same picture in your browser — configuration, identities, permission coverage, Ory service health, and the latest tool-call activity, all refreshing live. From there you can flip **enforcement** on or off, toggle **user login**, and use **Change stack** to reconnect to a different Ory — no CLI required.
 - **Live traces.** Every tool call is recorded as an OpenTelemetry-style span. Watch them stream as the agent works:
 
   ```bash
@@ -90,7 +93,7 @@ When the watch-mode logs look right, turn on blocking with one command (setup al
 npx -y -p @ory/pi ory-pi permissions enforce
 ```
 
-Now a denied tool is actually blocked and Pi shows why (the plugin returns `{ block: true, reason }` on Pi's `tool_call` event). Go back to watch mode anytime with `permissions observe`. Use `permissions status` to see what's covered and `permissions bootstrap` to (re-)grant the built-in tools.
+Now a denied tool is actually blocked and Pi shows why (the plugin returns `{ block: true, reason }` on Pi's `tool_call` event). Go back to watch mode anytime with `permissions observe`. Prefer clicking? The dashboard has the same **Enforce** switch — flip it on, or back to watch mode, without touching the CLI. Use `permissions status` to see what's covered and `permissions bootstrap` to (re-)grant the built-in tools.
 
 ## Also: add login to your own app
 
@@ -105,22 +108,22 @@ The guided setup covers most people. For scripted or CI setups, or to point at a
 ```bash
 npx -y -p @ory/pi ory-pi configure \
   --project-url https://<slug>.projects.oryapis.com \
-  --oauth2-client-id <sign-in client id> \
-  --user-login
+  --oauth2-client-id <sign-in client id>
 ```
 
-Pi's own identity registers itself automatically on first run — nothing to create. The `--oauth2-client-id` is the one piece browser sign-in needs — the public sign-in client, registered with the four loopback URLs `http://127.0.0.1:47823..47826/callback`; the guided setup makes it for you. For logging-only with no checks, use `--audit-only`. The equivalent env vars are `ORY_PROJECT_URL`, `ORY_OAUTH2_CLIENT_ID`, and `ORY_USER_LOGIN`.
+Pi's own identity registers itself automatically on first run — nothing to create. The `--oauth2-client-id` is the one piece browser sign-in needs — the public sign-in client, registered with the four loopback URLs `http://127.0.0.1:47823..47826/callback`; the guided setup makes it for you. For logging-only with no checks, use `--audit-only`. The interactive user login runs every session (always on, non-blocking) and only needs `ORY_OAUTH2_CLIENT_ID` to complete the browser flow. The equivalent env vars are `ORY_PROJECT_URL` and `ORY_OAUTH2_CLIENT_ID`.
 
 With nothing configured, the plugin still loads and runs in **pass-through mode**: skills and logging work, but no checks run and nothing is blocked. Perfectly fine if you only want the app-building features.
 
 ## Commands
 
 ```
-ory-pi install | uninstall        Install/remove; --reconfigure re-runs setup, --no-configure skips it, --global for all projects
+ory-pi install | uninstall        Install/remove; --reconfigure re-runs setup, --no-web forces the terminal wizard, --no-configure skips it
 ory-pi status                     Show configuration, identities, permission coverage, recent activity
+ory-pi dashboard                  Open the live browser dashboard (status + service health + Change stack)
 ory-pi watch                      Tail the live trace stream (OTel spans)
 ory-pi permissions <cmd>          status | bootstrap | observe (watch) | enforce (block)
-ory-pi configure <flags>          Point at a project by hand (--project-url, --oauth2-client-id, --user-login, --audit-only)
+ory-pi configure <flags>          Point at a project by hand (--project-url, --oauth2-client-id, --audit-only)
 ory-pi agent <status|unregister>  Manage Pi's own auto-created identity
 ```
 

package/dist/cli/main.js

@@ -97,6 +97,12 @@ function main() {
         case "watch":
             (0, argus_1.runWatchCommand)("pi", args);
             break;
+        case "dashboard":
+            (0, argus_1.runDashboardCommand)("ory-pi", "pi", args).then((code) => process.exit(code), (err) => {
+                console.error(err.message ?? err);
+                process.exit(1);
+            });
+            break;
         case "version":
         case "--version":
         case "-v":
@@ -182,6 +188,7 @@ Commands:
   local <cmd>                      Manage local Ory dev environment
                                    (up, down, status, seed, logs, env, configure, reset)
   status [--project-dir <path>]    Show plugin configuration and status
+  dashboard            Open the Ory Agent dashboard (system health + configuration)
   watch [trace-file]               Watch live trace output
   version                          Show version and the ory-agent-plugins build commit
 

package/dist/plugin.d.ts

@@ -4,8 +4,9 @@
  * Pi loads a default-exported factory `(pi) => void | Promise<void>` from a
  * TypeScript extension module (via jiti) and awaits it before startup
  * continues. We treat the factory body as the session-start hook: it runs the
- * user gate (advisory — there is no block channel for the session itself), the
- * agent gate, and writes the user→agent delegation tuple.
+ * user gate (which runs every session and never blocks — enforcement is
+ * governed solely by permissionMode at tool-call time), the agent gate, and
+ * writes the user→agent delegation tuple.
  *
  * The blocking permission decision lives in the `tool_call` hook, which CAN
  * block by returning `{ block: true, reason }` (like OpenClaw's

package/dist/plugin.js

@@ -5,8 +5,9 @@
  * Pi loads a default-exported factory `(pi) => void | Promise<void>` from a
  * TypeScript extension module (via jiti) and awaits it before startup
  * continues. We treat the factory body as the session-start hook: it runs the
- * user gate (advisory — there is no block channel for the session itself), the
- * agent gate, and writes the user→agent delegation tuple.
+ * user gate (which runs every session and never blocks — enforcement is
+ * governed solely by permissionMode at tool-call time), the agent gate, and
+ * writes the user→agent delegation tuple.
  *
  * The blocking permission decision lives in the `tool_call` hook, which CAN
  * block by returning `{ block: true, reason }` (like OpenClaw's
@@ -54,16 +55,14 @@ async function runSessionStart(client, deps) {
     client.logger.info("lifecycle.session_start", { harness: "pi" });
     client.tracer.setContext({ traceId: (0, argus_1.deriveTraceId)("pi"), sessionId: "pi" });
     client.tracer.record("session.start", "ok", { attributes: {} });
-    // Run the user login. Pi's factory body has no return-value channel to
-    // block the session, so allowBlock is false — the flow emits the user.auth
-    // audit span, refreshes tokens, and may prompt when interactive, but never
-    // prevents the session from starting. When ORY_USER_LOGIN is unset it is a
-    // no-op (mode === "disabled") and we fall through to legacy verification.
+    // Run the user login. It runs every session and never blocks the session
+    // from starting — the flow emits the user.auth audit span, refreshes tokens,
+    // and may prompt when interactive. Enforcement is governed solely by
+    // permissionMode at tool-call time.
     const userGate = deps.userLogin ?? argus_1.ensureUserAuthenticated;
-    const decision = await userGate(client, {
+    await userGate(client, {
         binName: "ory-pi",
         harness: "pi",
-        allowBlock: false,
     });
     // Resolve the agent identity (machine credentials). Never blocks; attaches
     // the agent's bearer token to outgoing Ory API calls.
@@ -72,74 +71,6 @@ async function runSessionStart(client, deps) {
     // Once both principals are populated, write the user→agent delegation tuple.
     // Written at most once per install + fail-open: audit-trail data only.
     await (0, argus_1.writeUserDelegatesAgent)(client);
-    if (decision.mode !== "disabled") {
-        return;
-    }
-    const resolved = (0, argus_1.resolveConfig)();
-    if (resolved.auditOnly) {
-        client.logger.info("config.audit_only", {
-            message: "Audit-only mode enabled. Auth and permission checks are disabled.",
-        });
-        return;
-    }
-    if (!resolved.projectUrl) {
-        client.logger.warn("config.not_configured", {
-            message: "Ory plugin is not configured. Auth and permission checks are disabled. " +
-                "Run 'npx ory-pi configure' to connect to an Ory project.",
-        });
-        return;
-    }
-    const sessionToken = process.env.ORY_SESSION_TOKEN;
-    const oauth2Token = process.env.ORY_OAUTH2_TOKEN;
-    if (sessionToken) {
-        await verifySessionToken(client, sessionToken);
-        return;
-    }
-    if (oauth2Token) {
-        await verifyOAuth2Token(client, oauth2Token);
-        return;
-    }
-    client.logger.warn("session.no_credentials", {
-        message: "Neither ORY_SESSION_TOKEN nor ORY_OAUTH2_TOKEN is set. " +
-            "Skipping authentication.",
-    });
-}
-async function verifySessionToken(client, token) {
-    try {
-        const session = await client.verifySession(token);
-        if (!session.active) {
-            client.logger.warn("session.inactive", {
-                message: "Ory session is not active. Re-authenticate to enable auth checks.",
-            });
-        }
-    }
-    catch (err) {
-        client.logger.warn("session.verify_failed", {
-            code: isOryError(err) ? err.code : "unknown",
-            message: err instanceof Error ? err.message : String(err),
-        });
-    }
-}
-async function verifyOAuth2Token(client, token) {
-    try {
-        const tokenInfo = await client.introspectToken(token);
-        if (!tokenInfo.active) {
-            client.logger.warn("oauth2.token_inactive", {
-                message: "Ory OAuth2 token is not active. Obtain a new token to enable auth checks.",
-            });
-            return;
-        }
-        client.logger.info("oauth2.session_authenticated", {
-            clientId: tokenInfo.clientId,
-            subject: tokenInfo.subject,
-        });
-    }
-    catch (err) {
-        client.logger.warn("oauth2.introspect_failed", {
-            code: isOryError(err) ? err.code : "unknown",
-            message: err instanceof Error ? err.message : String(err),
-        });
-    }
 }
 // ─── tool_call (pre-execution, blocking) ───────────────────────────
 function createToolCallHandler(client) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ory/pi",
-  "version": "0.13.9",
+  "version": "0.14.0",
   "description": "Ory plugin for Pi (the minimal coding agent): scaffolding skills, a local Ory instance, and authentication, authorization, and audit for every tool call",
   "license": "Apache-2.0",
   "homepage": "https://ory.com",
@@ -73,7 +73,7 @@
   ],
   "dependencies": {
     "reo-census": "^1.2.8",
-    "@ory/argus": "0.13.9"
+    "@ory/argus": "0.14.0"
   },
   "devDependencies": {
     "typescript": "^6.0.2",