@ory/codex 0.11.0 → 0.12.0

package/README.md

@@ -1,157 +1,101 @@
 # Ory Agent Plugin: Codex
 
-[Ory](https://ory.com) bundled into [Codex](https://github.com/openai/codex): skills that scaffold Ory authentication into your codebase, a local Ory stack you can spin up in one command, and (when pointed at an Ory project) authentication, authorization, and audit for every tool Codex runs.
+Security and developer experience for [Codex](https://github.com/openai/codex), powered by [Ory](https://ory.com).
 
-You don't need an Ory account or any prior Ory experience to start.
+**Security.** Codex runs real actions on your machine — editing files, running shell commands, calling APIs. The plugin gives every session a verifiable identity (you sign in once; Codex and any sub-agents it spawns each get their own), checks every tool call against permissions you control, and records each decision as an audit trace you can ship to your observability stack. It starts in watch mode so nothing is blocked on day one, and if Ory is ever unreachable it steps aside rather than locking you out.
 
-## New to Ory?
+**Developer experience.** A single command installs the plugin and walks you through connecting — choose Ory Network, a local Docker stack, or audit-only, and it wires up the project, sign-in client, login, and permissions for you. It also helps you build Ory into your own app: ask in plain language to scaffold login, registration, and recovery pages, run a local Ory, or manage identities and permissions through the bundled MCP server.
 
-[Ory](https://www.ory.com/docs/) is an open-source identity and access platform — it provides login, registration, sessions, social sign-in, multi-factor auth, and fine-grained permissions, so you don't have to build any of that yourself. Two things make it easy to try with no prior experience:
+## What you'll need
 
-- **Ory Elements** are prebuilt, themeable UI components for the auth pages (login, registration, recovery, settings). The scaffolding skills wire them into your app for you.
-- **The local Ory stack** is a complete Ory running on your laptop in Docker — no account, no signup, no API key. Everything in the Quickstart below works against it, fully offline.
+- [Codex](https://github.com/openai/codex), installed and signed in
+- Node.js **22 or newer**
+- [Docker](https://docs.docker.com/get-docker/) — only if you want to run Ory locally
+- macOS or Linux (Windows works via WSL2)
 
-This plugin does two independent things, and you can use either on its own:
+## Get started
 
-1. **Build auth into your app.** Have Codex scaffold Ory login, registration, social sign-in, and permissions into the project you're working on, backed by the local stack. This is the Quickstart below — it needs nothing but Docker.
-2. **Govern the agent itself.** Authenticate Codex's own session and authorize every tool it runs against Ory Permissions, with a full audit trail. See [Agent security](#agent-security).
-
-If you're just exploring, do the Quickstart first.
-
-## Prerequisites
-
-- [Codex](https://github.com/openai/codex) installed and signed in
-- Node.js **≥ 22**
-- [Docker](https://docs.docker.com/get-docker/) (only needed for the local Ory stack)
-- macOS or Linux. Windows works via WSL2.
-
-## Install
-
-No prior `npm install` required:
+Run one command. It installs the plugin and walks you through connecting:
 
 ```bash
-npx -y -p @ory/codex ory-codex install     # registers the Ory marketplace + plugin with `codex`
-npx -y -p @ory/codex ory-codex uninstall   # removes both
+npx -y -p @ory/codex ory-codex install
 ```
 
-Then confirm everything landed:
+This registers the Ory plugin with Codex (hooks, skills, and a bundled Ory tool server) and then asks how you want to connect — **press Enter for the default**:
+
+- **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 Codex does.
+
+That's it. Confirm everything landed with:
 
 ```bash
 npx -y -p @ory/codex ory-codex status
 ```
 
-`status` is the single source of truth — it prints configuration, user and agent identity, per-tool permission coverage, plugin + skill registration, and a tail of recent debug logs. Unconfigured fields show inline as `(unset)`.
-
-## Quickstart (≈ 3 minutes)
-
-From any project where you'd like Ory authentication, inside Codex:
-
-1. **Start a local Ory instance.** Ask Codex *"start the local Ory stack"* or pick `ory-local-up` from the `/skills` menu.
-
-   A banner prints the seeded test user's email and password. Note them — you'll log in with them in step 3.
-
-2. **Scaffold Ory into your project.** Ask Codex *"add Ory auth to this app"* or pick `ory-auth-setup` from `/skills`.
-
-   Codex installs Ory Elements, wires the SDK, generates the login / registration / recovery / verification / settings pages, and sets up session middleware. It targets the local stack from step 1, so no signup or API key is needed.
-
-3. **Sign in.** Start your app, visit the login page Codex 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 Codex session itself.** *(Optional but recommended.)* Out of the box the plugin only governs your *app*. To also attach an Ory identity to *Codex's* session — so every tool call is attributed to you, not a fallback `session:<id>` subject — opt in to the user-login flow:
+`status` is your one-stop check: what's configured, who's signed in, which tools are covered by permissions, and recent activity. Anything not set up yet shows as `(unset)`.
 
-   ```bash
-   export ORY_USER_LOGIN=true
-   export ORY_OAUTH2_CLIENT_ID=<value printed by `local up`>
-   ```
+> **First launch: trust the Ory hooks.** Codex treats a freshly installed plugin's hooks as untrusted, so your first Codex session asks you to review and trust them. Sign-in and per-tool checks only start running once you do. In the TUI, that first check kicks in on your opening turn.
 
-   User login is off by default. Both exports above are printed in the `local up` banner — copy them straight from there. `ORY_OAUTH2_CLIENT_ID` is required whenever `ORY_USER_LOGIN` is on: it identifies the public OAuth2 client the PKCE browser flow exchanges for a token. With both set, the next Codex 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.
+Re-run install with `--reconfigure` to change your connection later, or `--no-configure` to skip the wizard and connect by hand.
 
-That's the full Ory DX path. Stop here if you're just evaluating the plugin. Continue to [Agent security](#agent-security) when you're ready to enforce.
+## What you get
 
-## What's included
+Once connected, every tool Codex runs is governed by Ory — three things happen automatically:
 
-### Skills for scaffolding Ory into your application
+- **Who's driving.** You sign in once in your browser (a standard secure browser sign-in — no tokens to copy around). Codex itself registers its own identity automatically the first time it runs. The "who acted on whose behalf" trail stays queryable later.
+- **What it's allowed to do.** Before a tool runs, Ory checks whether it's permitted. It starts in **watch mode** — nothing is blocked, you just *see* what would be — so it never gets in your way on day one.
+- **A record of everything.** Every decision (allowed, denied, skipped) is logged as a trace you can send to Jaeger, Honeycomb, Grafana, or just a file.
 
-Codex surfaces the skill catalog in `/skills` and auto-invokes by description. Ask Codex in natural language or invoke a skill directly:
+If Ory is ever unreachable, the plugin gets out of the way and lets Codex keep working — so it can't lock you out. That also means enforcement is only as strong as the permissions you grant.
 
-**Start here — add Ory auth to your app:**
+### See what's happening
 
-- **`ory-auth-setup`** — full project setup. Install the Ory CLI, create an Ory Network project (or use the local one), add Ory Elements, configure the SDK, build the auth pages, wire session middleware.
-- **`ory-login-flow`** — login, registration, recovery, verification, and settings pages with Ory Elements. Next.js App Router and React SPA variants.
-- **`ory-social-login`** — Google, GitHub, Apple, Microsoft, Discord, and other OIDC providers with Jsonnet data mappers.
-- **`ory-local-dev`** — drive the local Ory stack from within Codex to prototype and test without a remote project.
+Everything the plugin does is observable out of the box — no configuration required:
 
-**Going further:**
+- **Status at a glance.** `npx -y -p @ory/codex ory-codex 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 traces.** Every tool call is recorded as an OpenTelemetry-style span. Watch them stream as the agent works:
 
-- **`ory-permissions-onboarding`** — bootstrap permissions for built-in tools, switch between observe and enforce mode, troubleshoot denials.
-- **`ory-build-integration`** — pull the runnable subset of an `ory/integrates` template (webhook / config / http-event) into your own app and wire it to your Ory project — no contribution/registry concerns.
-- **`ory-contribute-integration`** — author a brand-new integration as a contribution to `ory/integrates`, including `registry.entry.yaml`, the `Maintained by:` footer, DCO sign-off, and registry regeneration.
-- **`ory-e2b-sandbox`** — scaffold an [E2B](https://e2b.dev) sandbox template that boots with this plugin preinstalled and registered, so every sandbox session is gated by Ory auth, permissions, and tracing without any per-sandbox setup.
-- **`ory-build-agent`** — drop `@ory/argus` directly into a custom agent you own (Claude Agent SDK, OpenAI Agents SDK, Mastra, Vercel AI SDK, PydanticAI, LangGraph, Mistral AI, or Salesforce Agentforce) so the user is authenticated, every tool call is authorized against Ory Permissions, and the lifecycle emits trace spans.
-- **`ory-temporal-worker`** — scaffold a [Temporal](https://temporal.io) TypeScript worker per the [official local-dev guide](https://docs.temporal.io/develop/typescript/set-up-your-local-typescript), with every Activity gated by an Ory permission check, the worker's agent identity resolved via DCR, and the full lifecycle emitting trace spans.
+  ```bash
+  npx -y -p @ory/codex ory-codex watch
+  ```
 
-### Ory MCP server
+  Spans are also written to `~/.config/ory-agent-plugins/codex/ory-agent-trace.ndjson` (NDJSON, one span per line) — tail that file, or point `OTEL_EXPORTER_OTLP_ENDPOINT` at a collector to ship them straight to Jaeger, Honeycomb, or Grafana.
+- **Debug log.** For a verbose play-by-play, set `ORY_AGENT_DEBUG=true`; structured logs land in `~/.config/ory-agent-plugins/codex/ory-agent-debug.log`.
 
-Bundled and registered automatically. Exposes the Ory CLI and the Ory Network REST API as MCP tools so Codex can manage identities, OAuth2 clients, projects, permissions, and configuration without ever leaving the chat. Useful for seeding test data, verifying a scaffolded integration, or running one-off admin tasks.
+### Ready to enforce?
 
-### Local Ory stack
+When the watch-mode logs look right, turn on blocking with one command (setup already granted you the built-in tools):
 
-From Codex's `/skills` menu:
-
-```
-ory-local-up      # start a local Ory instance in Docker
-ory-local-down    # tear it all down
-ory-temporal-up   # start a local Temporal dev server (for ory-temporal-worker)
+```bash
+npx -y -p @ory/codex ory-codex permissions enforce
 ```
 
-Or via the CLI: `npx -y -p @ory/codex ory-codex local up | down`.
-
-`ory-local-up` runs a complete Ory on your laptop: the Ory APIs (Identities, OAuth2, Permissions) at `http://localhost:4000`, a login UI on `:4455` (not :3000, to avoid Next.js port conflicts), and Jaeger (the trace viewer) on `:16686`. A test user identity is seeded and its credentials are printed for you. Use it to:
+Now a denied tool is actually blocked and Codex shows why. 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 — or just ask Codex in chat, e.g. *"grant me use of the shell tool."*
 
-- **Learn Ory hands-on** without signing up for a hosted project.
-- **Prototype** flows (login, social, MFA, recovery, permissions) against a real Ory backend.
-- **Test** an auth integration end-to-end before pushing anything to a real environment.
-- **Develop** your application against the same identity, OAuth2, and permission surfaces you'll ship with.
+## Also: add login to your own app
 
-## Pointing at a real Ory project
+Beyond securing Codex, the plugin helps you build Ory into whatever you're working on. Ask Codex *"add Ory login to this app"* — or pick `ory-auth-setup` from the `/skills` menu — and it scaffolds the login, registration, recovery, and settings pages (using [Ory Elements](https://github.com/ory/elements)) wired to a local Ory, so no signup or keys are needed. Start that local Ory with the `ory-local-up` skill (it prints a test email + password to sign in with) and tear it down with `ory-local-down`.
 
-The Quickstart uses the local stack. If you have a hosted [Ory Network](https://console.ory.sh) project (Ory's managed cloud), point the plugin at it with a single configure command. **The plugin requires `--oauth2-client-id` whenever `--project-url` is provided** — register the client first (see [Register the user OAuth2 client](#register-the-user-oauth2-client) below), then run:
-
-```bash
-npx -y -p @ory/codex ory-codex configure \
-  --project-url https://<id>.projects.oryapis.com \
-  --oauth2-client-id <public OAuth2 client id>
-```
+Bundled **skills** (ask in plain language, or pick from `/skills`) cover more: `ory-auth-setup`, `ory-login-flow`, `ory-social-login` (Google, GitHub, Apple…), `ory-permissions-onboarding`, and playbooks for wiring Ory into your own agents, E2B sandboxes, or Temporal workers. A built-in **Ory tool server** lets Codex manage identities, projects, and permissions straight from chat.
 
-- **`--project-url`** points the plugin at your project. The **agent identity** (machine credentials for Codex's outgoing Ory API calls) is created automatically on first run via OAuth2 Dynamic Client Registration ([RFC 7591](https://datatracker.ietf.org/doc/html/rfc7591)) against the project's `/oauth2/register` endpoint — no manual step required for that one.
-- **`--oauth2-client-id`** is required because the **user** PKCE browser flow (triggered by `ORY_USER_LOGIN=true`) cannot self-register — you must register a public OAuth2 client ahead of time and supply its id here. The configure command refuses to save a project URL without it, so you don't end up with a silently-broken setup later. See [Register the user OAuth2 client](#register-the-user-oauth2-client) below for the exact CLI / Console steps.
-- **`--api-key ory_pat_...`** is optional — pass it only if you want to override the auto-registered agent identity with a static personal access token (operator override; rarely needed).
+## Configure by hand (CI / advanced)
 
-If you only want audit logging (no auth or permission checks), substitute `--audit-only` — the OAuth2 client id is not required in that mode:
+The guided setup covers most people. For scripted or CI setups, or to point at an existing Ory Network project, connect directly. Settings are saved to `~/.config/ory-agent-plugins/config.json` and shared across all your Ory agent plugins; environment variables win when both are set.
 
 ```bash
-npx -y -p @ory/codex ory-codex configure --audit-only
+npx -y -p @ory/codex ory-codex configure \
+  --project-url https://<slug>.projects.oryapis.com \
+  --oauth2-client-id <sign-in client id> \
+  --user-login
 ```
 
-The same settings can be supplied via environment variables (`ORY_PROJECT_URL`, `ORY_OAUTH2_CLIENT_ID`, `ORY_AGENT_API_KEY`) — env vars take precedence over the config file when both are set, which is what most CI / scripted setups want.
-
-Config is saved to `~/.config/ory-agent-plugins/config.json` and shared across every Ory agent plugin on the machine.
-
-Without configuration the plugin still loads cleanly and runs in **pass-through mode**: skills work, but nothing is blocked. You can stay in pass-through mode indefinitely if you only want the DX features.
-
-### Register the user OAuth2 client
-
-If you plan to turn on `ORY_USER_LOGIN=true` (recommended — it's what attributes every tool call to *you* rather than a fallback `session:<id>` subject), your hosted Ory project needs a **public** OAuth2 client (no client secret) registered ahead of time. The local stack provisions this for you automatically; against a hosted project you have to register it once yourself.
-
-The client must list **all four** loopback ports as redirect URIs:
+Codex'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 guided setup makes it for you, or see below to do it by hand. For logging-only with no checks, use `--audit-only`.
 
-- `http://127.0.0.1:47823/callback`
-- `http://127.0.0.1:47824/callback`
-- `http://127.0.0.1:47825/callback`
-- `http://127.0.0.1:47826/callback`
+<details>
+<summary>Create the sign-in client by hand</summary>
 
-The plugin walks the four ports at runtime so the login can survive any one of them being occupied — Ory rejects the callback if the port it lands on isn't on the registered list, so register all four.
-
-Create the client with the [Ory CLI](https://www.ory.com/docs/guides/cli/installation):
+The guided setup normally does this. To do it yourself, create a **public** OAuth2 client (no secret) listing all four loopback URLs — the plugin tries each in turn at runtime so sign-in survives a busy port, and Ory only accepts a callback on a URL you registered:
 
 ```bash
 ory create oauth2-client --project <project-id> \
@@ -166,104 +110,40 @@ ory create oauth2-client --project <project-id> \
   --redirect-uri http://127.0.0.1:47826/callback
 ```
 
-…or in the [Ory Console](https://console.ory.sh) under *OAuth2* → *Clients* → *Create client* (pick "Public client", set "Authorization Code" + "Refresh Token" grants, scopes `openid offline_access`, paste the four redirect URIs above). Then persist the issued id with the configure command (preferred — survives across sessions):
-
-```bash
-npx -y -p @ory/codex ory-codex configure \
-  --project-url https://<id>.projects.oryapis.com \
-  --oauth2-client-id <client-id from the step above>
-```
-
-…or set it in the environment alongside `ORY_USER_LOGIN`:
-
-```bash
-export ORY_USER_LOGIN=true
-export ORY_OAUTH2_CLIENT_ID=<client-id from the step above>
-```
-
-Headless / CI runs that already hold a session token can skip this entirely by setting `ORY_USER_SESSION_TOKEN` instead — no browser flow runs, so no OAuth2 client is needed.
-
-## Agent security
-
-Once the plugin is pointed at an Ory project (local or hosted), Codex'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 user login is enabled (`ORY_USER_LOGIN=true`, off by default — browser PKCE flow on first session, persisted token thereafter). The Codex 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 plugin checks [Ory Permissions](https://www.ory.com/docs/keto) (Zanzibar-style relations) 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 so *"agent X acting on behalf of user Y"* stays queryable after tokens expire.
-
-The plugin is **fail-open** on its own infrastructure failures (network errors, rate limits, missing config), so enforcement is only as strong as your permission grants — grant explicit `use` on the tools each user should be able to run.
+…or in the [Ory Console](https://console.ory.sh) under *OAuth2* → *Clients* → *Create client* (pick "Public client", set "Authorization Code" + "Refresh Token" grants, scopes `openid offline_access`, paste the four URLs above). Pass the resulting id to `configure --oauth2-client-id`. Running headless with a session token already? Set `ORY_USER_SESSION_TOKEN` and skip the browser step entirely.
 
-### Enable enforcement
+</details>
 
-After install the plugin 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.
+With nothing configured, the plugin still loads and runs in **pass-through mode**: skills, commands, and logging work, but no checks run and nothing is blocked. Perfectly fine if you only want the app-building features.
 
-1. **Turn on user login.** It's off by default. In your shell:
-
-   ```bash
-   export ORY_USER_LOGIN=true
-   export ORY_OAUTH2_CLIENT_ID=<public OAuth2 client id>
-   ```
-
-   The next Codex session opens a browser for PKCE login. Subsequent sessions reuse the persisted token until it expires.
-
-   `ORY_OAUTH2_CLIENT_ID` is required when `ORY_USER_LOGIN` is on: PKCE needs a public OAuth2 client registered with the four loopback redirect URIs (`http://127.0.0.1:47823..47826/callback`) to exchange the authorization code for a token. The local stack provisions one and prints the export in its `local up` banner; for a hosted Ory project see [Register the user OAuth2 client](#register-the-user-oauth2-client) for the exact CLI / Console steps. Headless / CI runs can skip the browser flow entirely by pre-supplying `ORY_USER_SESSION_TOKEN` instead.
-
-2. **Bootstrap permissions for the built-in tools.** One idempotent command grants the current user `use` on every tool Codex ships with (shell, apply_patch, …):
-
-   ```bash
-   npx -y -p @ory/codex ory-codex permissions bootstrap
-   ```
-
-   If a user identity is already cached at install time, the installer runs this for you automatically — re-run after adding tools, switching subjects, or changing the namespace.
-
-3. **Check coverage.** `permissions status` probes every tool in the harness's catalog and prints allowed / denied per tool:
-
-   ```bash
-   npx -y -p @ory/codex ory-codex permissions status
-   ```
-
-   Add permissions for any MCP server tools or custom commands by hand, or via the Ory MCP server from inside Codex (*"grant me use on the shell tool"*).
-
-4. **Promote to enforce.** Once the observe-mode logs look right, switch over:
-
-   ```bash
-   npx -y -p @ory/codex ory-codex permissions enforce
-   ```
-
-   Denies now block the tool call; Codex shows the denial reason and the decision is recorded as a `tool.block` trace span with `blocked: true`. Switch back any time with `permissions observe`.
-
-## CLI reference
+## Commands
 
 ```
-npx -y -p @ory/codex ory-codex install | uninstall
-npx -y -p @ory/codex ory-codex configure                            [--project-url <url> --oauth2-client-id <id>] [--api-key <key>] [--audit-only]
-npx -y -p @ory/codex ory-codex agent <status|unregister>            Manage the agent's OAuth2 identity
-npx -y -p @ory/codex ory-codex permissions <status|bootstrap|observe|enforce>
-npx -y -p @ory/codex ory-codex local <up|down|status|seed|logs|env|configure|reset>
-npx -y -p @ory/codex ory-codex status
+ory-codex install | uninstall        Install/remove; --reconfigure re-runs setup, --no-configure skips it
+ory-codex status                     Show configuration, identities, permission coverage, recent activity
+ory-codex watch                      Tail the live trace stream (OTel spans)
+ory-codex permissions <cmd>          status | bootstrap | observe (watch) | enforce (block)
+ory-codex configure <flags>          Point at a project by hand (--project-url, --oauth2-client-id, --user-login, --audit-only)
+ory-codex agent <status|unregister>  Manage Codex's own auto-created identity
+ory-codex local <up|down|status|…>   Run / manage a local Ory in Docker
 ```
 
-Highlights:
+All prefixed with `npx -y -p @ory/codex`.
 
-- `agent status` — show the current persisted DCR identity for the agent.
-- `permissions observe` / `permissions enforce` — switch between "log denies, allow through" (the install default) and "block denies." `permissions bootstrap` writes `use` permissions for the harness's built-in tools so the promotion path doesn't require hand-writing relations.
-- `configure --audit-only` — kill switch that disables Ory entirely (no auth, no permission checks; only audit logging of tool invocations). For phased rollouts, prefer `permissions observe` over `--audit-only`.
-- `local seed` / `local env` — reseed the test user, or print env vars for pointing other tools at the local stack.
+The local stack runs a complete Ory on your laptop: the Ory APIs at `http://localhost:4000`, a login UI on `:4455` (not :3000, to avoid Next.js port conflicts), the Ory Console on `:4100`, and Jaeger (the trace viewer) on `:16686`.
 
 ## Troubleshooting
 
-- **`ory-local-up` fails.** Make sure Docker is running and ports `4455` (login UI), `4000`, `4100`, and `16686` are free.
-- **PKCE login loops.** Clear persisted state with `npx -y -p @ory/codex ory-codex agent unregister` and retry.
-- **`npx` fetches an old version.** Force a fresh fetch: `npx -y -p @ory/codex@latest ory-codex …`.
-- **`npm install … ENOVERSIONS`.** If your `~/.npmrc` sets `min-release-age`, npm filters out package versions newer than that threshold. Override per-call with `npm_config_min_release_age=0 npx -y -p @ory/codex ory-codex install`.
-- **`codex doctor` reports `ory-mcp-server is not resolvable`.** The bundled MCP server resolves via `npx -y -p @ory/mcp-server` on demand — make sure `npm`/`npx` is on PATH. The first session start fetches the server tarball; subsequent sessions reuse the cache.
-- **Need more signal.** Set `ORY_AGENT_DEBUG=true` and `ORY_AGENT_LOG_FILE=/tmp/ory.log` to capture structured logs.
+- **`local up` fails** — make sure Docker is running and ports `4000`, `4100`, `4455`, and `16686` are free.
+- **Browser sign-in loops** — reset with `ory-codex agent unregister` and try again.
+- **`npx` grabbed an old version** — force the latest: `npx -y -p @ory/codex@latest ory-codex …`.
+- **`npm install … ENOVERSIONS`** — if your `~/.npmrc` sets `min-release-age`, npm hides versions newer than that. Override per-call: `npm_config_min_release_age=0 npx -y -p @ory/codex ory-codex install`.
+- **`codex doctor` says `ory-mcp-server is not resolvable`** — the bundled tool server is fetched on demand via `npx`, so make sure `npm`/`npx` is on your PATH. The first session downloads it; later ones reuse the cache.
+- **Want to see what's happening** — `npx -y -p @ory/codex ory-codex status` for a snapshot, `npx -y -p @ory/codex ory-codex watch` for the live trace stream, or set `ORY_AGENT_DEBUG=true` for a verbose log. Traces and logs live under `~/.config/ory-agent-plugins/codex/` (see [See what's happening](#see-whats-happening)).
 
-## Links
+## Learn more
 
-- [Ory documentation](https://www.ory.com/docs/)
-- [Ory Network console](https://console.ory.sh)
-- [Ory Elements](https://github.com/ory/elements)
+- [Ory documentation](https://www.ory.com/docs/) · [Ory Console](https://console.ory.sh) · [Ory Elements](https://github.com/ory/elements)
 - [Codex documentation](https://github.com/openai/codex)
 
 ## License

package/dist/cli/main.js

@@ -55,14 +55,19 @@ function main() {
     const [command, ...args] = process.argv.slice(2);
     switch (command) {
         case "install":
+            (0, argus_1.beginDeferNextSteps)();
             (0, setup_js_1.install)(args);
-            postInstallPermissions("ory-codex", "codex").then(() => process.exit(0), (err) => {
+            (0, argus_1.runPostInstall)("ory-codex", "codex", args).then(() => process.exit(0), (err) => {
                 console.error(err.message ?? err);
                 process.exit(1);
             });
             break;
         case "uninstall":
             (0, setup_js_1.uninstall)(args);
+            (0, argus_1.clearCredentialsForUninstall)().then(() => process.exit(0), (err) => {
+                console.error(err.message ?? err);
+                process.exit(1);
+            });
             break;
         case "configure":
             (0, argus_1.runConfigureCommand)("ory-codex", args);
@@ -91,6 +96,9 @@ function main() {
                 process.exit(1);
             });
             break;
+        case "watch":
+            (0, argus_1.runWatchCommand)("codex", args);
+            break;
         case "help":
         case "--help":
         case "-h":
@@ -103,12 +111,6 @@ function main() {
             process.exit(1);
     }
 }
-async function postInstallPermissions(binName, harness) {
-    const bootstrapped = await (0, argus_1.maybeAutoBootstrap)(binName, harness);
-    (0, argus_1.printPermissionsOnboardingHelp)(binName, harness, {
-        bootstrappedAutomatically: bootstrapped,
-    });
-}
 async function status() {
     await (0, argus_1.runStatusCommand)("ory-codex", "codex", {
         title: "Codex",
@@ -124,7 +126,7 @@ function help() {
 ory-codex — Ory plugin for Codex
 
 Usage:
-  npx ory-codex <command> [options]
+  npx -y -p @ory/codex ory-codex <command> [options]
 
 Commands:
   install                  Install via \`codex plugin marketplace add\` + \`codex plugin add\`
@@ -136,14 +138,15 @@ Commands:
   local <cmd>              Manage local Ory dev environment
                              (up, down, status, seed, logs, env, configure, reset)
   status                   Show plugin status, config, and recent log lines
+  watch [trace-file]       Tail the trace stream (OTel spans) live
 
 Examples:
-  npx ory-codex install
-  npx ory-codex configure --project-url https://<id>.projects.oryapis.com \\
+  npx -y -p @ory/codex ory-codex install
+  npx -y -p @ory/codex ory-codex configure --project-url https://<slug>.projects.oryapis.com \\
                           --api-key ory_pat_...
-  npx ory-codex permissions status
-  npx ory-codex status
-  npx ory-codex uninstall
+  npx -y -p @ory/codex ory-codex permissions status
+  npx -y -p @ory/codex ory-codex status
+  npx -y -p @ory/codex ory-codex uninstall
 
 Requires the \`codex\` CLI on PATH.
 `);

package/dist/cli/setup.js

@@ -83,6 +83,15 @@ const MARKETPLACE_ROOT = path.join((0, argus_1.getHarnessDataDir)("codex"), "mar
 const PLUGIN_ROOT = path.join(MARKETPLACE_ROOT, "plugins", PLUGIN_NAME);
 /** Hook command that resolves via the npm registry on every invocation. */
 const HOOK_COMMAND = "npx -y -p @ory/codex ory-codex-hook";
+/**
+ * Per-handler timeout (seconds). Codex kills a hook subprocess after this
+ * window (its built-in default is only 5s). SessionStart may run the
+ * interactive user login (PKCE browser flow), which needs a human in the
+ * loop, so it gets a generous window; the tool-lifecycle hooks only make a
+ * permission check, so a shorter window is plenty.
+ */
+const SESSION_START_TIMEOUT_SEC = 300;
+const TOOL_HOOK_TIMEOUT_SEC = 60;
 function readPackageVersion() {
     try {
         const pj = JSON.parse(fs.readFileSync(path.join(PACKAGE_ROOT, "package.json"), "utf-8"));
@@ -129,13 +138,16 @@ function copyMarketplaceSkeleton() {
 }
 /**
  * Patch the plugin manifest with the runtime values that depend on the
- * installed npm package (currently just the version). Keeps the rest of the
- * static manifest untouched.
+ * installed npm package (the version) and re-assert the `hooks` pointer.
+ * Codex only wires up `hooks.json` when the manifest declares it, so we set
+ * it here as well as in the static skeleton to survive skeleton drift. Keeps
+ * the rest of the static manifest untouched.
  */
 function updatePluginManifest() {
     const manifestPath = path.join(PLUGIN_ROOT, ".codex-plugin", "plugin.json");
     const manifest = JSON.parse(fs.readFileSync(manifestPath, "utf-8"));
     manifest.version = PACKAGE_VERSION;
+    manifest.hooks = "./hooks.json";
     fs.writeFileSync(manifestPath, JSON.stringify(manifest, null, 2) + "\n");
 }
 /**
@@ -161,21 +173,39 @@ function renderCommands() {
         fs.writeFileSync(path.join(commandsDir, `${cmd.slug}.md`), (0, argus_1.commandToFrontmatterMarkdown)(cmd));
     }
 }
+/**
+ * A Codex hook event maps to an array of matcher groups, each carrying its
+ * own list of command handlers (the same nested shape Claude Code uses). We
+ * register a single unmatched group so the handler runs for every event
+ * occurrence. Emitting the handler flat (without the wrapping group) parses
+ * as a matcher group with zero handlers, so the hook silently never runs.
+ */
+function hookGroup(timeoutSec) {
+    return [
+        {
+            hooks: [{ type: "command", command: HOOK_COMMAND, timeout: timeoutSec }],
+        },
+    ];
+}
 /**
  * Generate the hooks file. Hook command resolves the bin via `npx`, so the
  * path is stable across npm cache evictions and version bumps.
+ *
+ * Codex only loads this file when `plugin.json` declares `hooks` (see the
+ * marketplace skeleton); it is not auto-discovered by filename. Fresh plugin
+ * hooks are also untrusted until the user reviews them in Codex's hook-trust
+ * UI — see `printNextSteps`.
  */
 function writeHooks() {
     const hooksPath = path.join(PLUGIN_ROOT, "hooks.json");
-    const entry = [{ type: "command", command: HOOK_COMMAND }];
     fs.writeFileSync(hooksPath, JSON.stringify({
         hooks: {
-            SessionStart: entry,
-            PreToolUse: entry,
-            PostToolUse: entry,
-            PermissionRequest: entry,
-            UserPromptSubmit: entry,
-            Stop: entry,
+            SessionStart: hookGroup(SESSION_START_TIMEOUT_SEC),
+            PreToolUse: hookGroup(TOOL_HOOK_TIMEOUT_SEC),
+            PostToolUse: hookGroup(TOOL_HOOK_TIMEOUT_SEC),
+            PermissionRequest: hookGroup(TOOL_HOOK_TIMEOUT_SEC),
+            UserPromptSubmit: hookGroup(TOOL_HOOK_TIMEOUT_SEC),
+            Stop: hookGroup(TOOL_HOOK_TIMEOUT_SEC),
         },
     }, null, 2) + "\n");
 }
@@ -255,11 +285,45 @@ function uninstall(_args) {
     }
 }
 function printNextSteps() {
+    (0, argus_1.nextStepsSink)(({ configured }) => configured ? printConfiguredNextStepsNow() : printNextStepsNow());
+}
+/**
+ * Closing message when the interactive wizard already connected Ory. Drops the
+ * manual "point at a project" steps (they'd contradict what's saved) but keeps
+ * Codex's harness-specific note about trusting freshly installed hooks.
+ */
+function printConfiguredNextStepsNow() {
+    const npx = "npx -y -p @ory/codex ory-codex";
+    console.log("");
+    console.log("Next steps:");
+    console.log("  Start a Codex session — Ory is configured and ready. Codex treats");
+    console.log("  freshly installed plugin hooks as untrusted, so it will prompt you to");
+    console.log("  review and trust the Ory hooks on first launch; the auth gate and");
+    console.log("  per-tool permission checks only run once they're trusted.");
+    console.log("");
+    if ((0, argus_1.resolveConfig)().auditOnly) {
+        console.log("  Audit-only mode: tool calls are traced locally — no checks, nothing blocked.");
+        console.log("");
+        console.log(`  1. See what's been traced:  ${npx} status  (or watch live: ${npx} watch)`);
+        console.log("  2. More detail?             export ORY_AGENT_DEBUG=true");
+    }
+    else {
+        console.log("  It starts in watch mode: every tool call is checked, nothing blocked yet.");
+        console.log("");
+        console.log(`  1. See what Ory is doing:   ${npx} status  (or watch live: ${npx} watch)`);
+        console.log(`  2. Turn on enforcement:     ${npx} permissions enforce`);
+        console.log(`                              (back to watch: ${npx} permissions observe)`);
+        console.log("  3. More detail?             export ORY_AGENT_DEBUG=true");
+    }
+    console.log("");
+    console.log(`To uninstall: ${npx} uninstall`);
+}
+function printNextStepsNow() {
     console.log("");
     console.log("Next steps:");
     console.log("  1. (Optional) Point at an Ory project — without this, the plugin");
     console.log("     runs in pass-through mode (skills work, nothing is blocked):");
-    console.log("       npx ory-codex configure --project-url https://<id>.projects.oryapis.com \\");
+    console.log("       npx -y -p @ory/codex ory-codex configure --project-url https://<slug>.projects.oryapis.com \\");
     console.log("                              --oauth2-client-id <public OAuth2 client id>");
     console.log("     (`--oauth2-client-id` is required when --project-url is set, because the");
     console.log("     user PKCE browser flow needs a pre-registered public client. Add");
@@ -272,9 +336,12 @@ function printNextSteps() {
     console.log("     Without this, Codex runs without a human Ory identity attached to the");
     console.log("     session and permission checks fall back to a session:<id> subject.");
     console.log("");
-    console.log("  4. Start a Codex session — Ory hooks are now wired in.");
+    console.log("  4. Start a Codex session. Codex treats freshly installed plugin");
+    console.log("     hooks as untrusted, so it will prompt you to review and trust");
+    console.log("     the Ory hooks on first launch — the auth gate and per-tool");
+    console.log("     permission checks only run once they're trusted.");
     console.log("");
-    console.log("To uninstall: npx ory-codex uninstall");
+    console.log("To uninstall: npx -y -p @ory/codex ory-codex uninstall");
 }
 // --- Standalone binary entry point (ory-codex-setup) ---
 if (require.main === module) {
@@ -283,7 +350,7 @@ if (require.main === module) {
 ory-codex-setup — Install or remove the Ory plugin for Codex
 
 Usage:
-  npx ory-codex-setup [options]
+  npx -y -p @ory/codex ory-codex-setup [options]
 
 Options:
   --uninstall    Remove the Ory plugin and marketplace
@@ -302,6 +369,12 @@ refreshes Codex's cache copy on the next session.
     const args = process.argv.slice(2);
     if (args.includes("--uninstall")) {
         uninstall(args);
+        // Direct `-setup --uninstall` path: also clear stored Ory credentials.
+        // (The `ory-codex uninstall` command handles this itself.)
+        (0, argus_1.clearCredentialsForUninstall)().then(() => process.exit(0), (err) => {
+            console.error(err.message ?? err);
+            process.exit(1);
+        });
     }
     else {
         install(args);

package/dist/handlers.d.ts

@@ -10,8 +10,8 @@ export interface HandleHookEventDeps {
  * Route a Codex hook event to the appropriate Ory integration.
  *
  * Codex events: SessionStart, PreToolUse, PostToolUse, PermissionRequest,
- * UserPromptSubmit, Stop. Hooks must be enabled via
- * `[features] codex_hooks = true` in `~/.codex/config.toml`.
+ * UserPromptSubmit, Stop. Hooks are declared by the plugin (`hooks` in
+ * plugin.json → hooks.json) and must be trusted by the user before they run.
  */
 export declare function handleHookEvent(input: CodexHookInput, client: OryAgentClient, deps?: HandleHookEventDeps): Promise<CodexHookOutput>;
 /**

package/dist/handlers.js

@@ -7,8 +7,8 @@ const argus_1 = require("@ory/argus");
  * Route a Codex hook event to the appropriate Ory integration.
  *
  * Codex events: SessionStart, PreToolUse, PostToolUse, PermissionRequest,
- * UserPromptSubmit, Stop. Hooks must be enabled via
- * `[features] codex_hooks = true` in `~/.codex/config.toml`.
+ * UserPromptSubmit, Stop. Hooks are declared by the plugin (`hooks` in
+ * plugin.json → hooks.json) and must be trusted by the user before they run.
  */
 async function handleHookEvent(input, client, deps = {}) {
     const event = input.hook_event_name;

package/dist/types.d.ts

@@ -1,8 +1,9 @@
 /**
  * Codex hook event payload delivered on stdin.
  *
- * Codex uses a subprocess hook model (JSON stdin/stdout). Hooks are
- * feature-gated behind `[features] codex_hooks = true` in config.toml.
+ * Codex uses a subprocess hook model (JSON stdin/stdout). Hooks ship in the
+ * plugin (declared via `hooks` in plugin.json); Codex requires the user to
+ * trust freshly installed plugin hooks before they run.
  *
  * Canonical `tool_name` values:
  *   - `"Bash"`

package/marketplace/plugins/ory-codex/.codex-plugin/plugin.json

@@ -19,6 +19,7 @@
     "zanzibar"
   ],
   "skills": "./skills/",
+  "hooks": "./hooks.json",
   "mcpServers": "./.mcp.json",
   "interface": {
     "displayName": "Ory",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ory/codex",
-  "version": "0.11.0",
+  "version": "0.12.0",
   "description": "Ory plugin for Codex: scaffolding skills, a local Ory instance, and authentication, authorization, and audit for every tool call",
   "license": "Apache-2.0",
   "homepage": "https://ory.com",
@@ -66,7 +66,7 @@
     "marketplace"
   ],
   "dependencies": {
-    "@ory/argus": "0.11.0"
+    "@ory/argus": "0.12.0"
   },
   "engines": {
     "node": ">=22"