@ory/claude-code 0.11.1 → 0.12.0

package/README.md

@@ -1,168 +1,99 @@
 # Ory Agent Plugin: Claude Code
 
-[Ory](https://ory.com) bundled into [Claude Code](https://docs.anthropic.com/en/docs/claude-code): skills and slash commands 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 Claude runs.
+Security and developer experience for [Claude Code](https://docs.anthropic.com/en/docs/claude-code), powered by [Ory](https://ory.com).
 
-You don't need an Ory account or any prior Ory experience to start.
+**Security.** Claude 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; Claude 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.
+- [Claude Code](https://docs.anthropic.com/en/docs/claude-code), 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 Claude 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 Claude'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
-
-- [Claude Code](https://docs.anthropic.com/en/docs/claude-code) 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
-
-Inside Claude Code:
-
-```
-/plugin marketplace add ory/claude-plugins
-/plugin install ory-agent-plugin@ory
-```
-
-Then confirm everything landed:
+Run one command. It installs the plugin and walks you through connecting:
 
 ```bash
-npx -y -p @ory/claude-code ory-claude status
+npx -y -p @ory/claude-code ory-claude install
 ```
 
-`status` is the single source of truth — it prints configuration, user and agent identity, per-tool permission coverage, hook + skill registration, and a tail of recent debug logs. Unconfigured fields show inline as `(unset)`.
+You'll be asked how you want to connect — **press Enter for the default**:
 
-<details>
-<summary>Alternative install path (no Claude Code session required)</summary>
+- **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 Claude does.
+
+That's it. Confirm everything landed with:
 
 ```bash
-npx -y -p @ory/claude-code ory-claude install            # current project
-npx -y -p @ory/claude-code ory-claude install --global   # all projects (user scope)
-npx -y -p @ory/claude-code ory-claude uninstall
+npx -y -p @ory/claude-code ory-claude status
 ```
 
-The installer requires the `claude` CLI on `PATH`.
-
-</details>
-
-## Quickstart
-
-From any project where you'd like Ory authentication, inside Claude Code:
+`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)`.
 
-1. **Start a local Ory instance.** *(~1 min. Requires Docker running.)* Ask Claude *"start the local Ory stack"* or run the slash command:
+> Prefer to install from inside Claude Code? Run `/plugin marketplace add ory/claude-plugins` then `/plugin install ory-agent-plugin@ory`. That registers the plugin but skips the guided setup — run `ory-claude install` (or `configure`) in a terminal afterwards to connect. Re-run install with `--reconfigure` to change your connection later, or `--no-configure` to skip the wizard.
 
-   ```
-   /ory-agent-plugin:local-up
-   ```
+## What you get
 
-   A banner prints the seeded test user's email and password. Note them — you'll log in with them in step 3.
+Once connected, every tool Claude runs is governed by Ory — three things happen automatically:
 
-2. **Scaffold Ory into your project.** *(~5–10 min, depending on your project.)* Ask Claude *"add Ory auth to this app"*. The `ory-auth-setup` skill takes over: it 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.
+- **Who's driving.** You sign in once in your browser; Claude (and any sub-agents it spawns) each get their own identity. No tokens to copy around, and 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.
 
-3. **Sign in.** Start your app, visit the login page Claude 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.
+If Ory is ever unreachable, the plugin gets out of the way and lets Claude keep working — so it can't lock you out.
 
-4. **Turn on Ory login for the Claude session itself.** *(Optional but recommended.)* Out of the box the plugin only governs your *app*. To also attach an Ory identity to *Claude's* session — so every tool call is attributed to you, not a fallback `session:<id>` subject — opt in to the user-login flow:
+### See what's happening
 
-   ```bash
-   export ORY_USER_LOGIN=true
-   export ORY_OAUTH2_CLIENT_ID=<value printed by `local up`>
-   ```
+Everything the plugin does is observable out of the box — no configuration required:
 
-   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 Claude 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.
+- **Status at a glance.** `npx -y -p @ory/claude-code ory-claude 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:
 
-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.
+  ```bash
+  npx -y -p @ory/claude-code ory-claude watch
+  ```
 
-## What's included
+  Spans are also written to `~/.config/ory-agent-plugins/claude-code/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/claude-code/ory-agent-debug.log`.
 
-### Skills for scaffolding Ory into your application
+### Ready to enforce?
 
-Each skill is a vetted, end-to-end playbook. Skills are model-invoked — ask Claude in natural language and the matching skill takes over. New to Ory? Start with the first group.
+When the watch-mode logs look right, turn on blocking with one command (setup already granted you the built-in tools):
 
-**Start here — add Ory auth to your app:**
-
-- **`ory-auth-setup`** *(e.g. "set up Ory auth in this project")* — 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`** *(e.g. "add login and registration pages with Ory Elements")* — login, registration, recovery, verification, and settings pages with Ory Elements. Next.js App Router and React SPA variants.
-- **`ory-social-login`** *(e.g. "add Google sign-in via Ory")* — Google, GitHub, Apple, Microsoft, Discord, and other OIDC providers with Jsonnet data mappers.
-- **`ory-local-dev`** *(e.g. "run the local Ory stack")* — drive the local Ory stack from within Claude to prototype and test without a remote project.
-
-**Going further:**
-
-- **`ory-permissions-onboarding`** *(e.g. "grant me use on the Bash tool")* — walk through writing the Ory Permissions that let the plugin enforce per-tool access.
-- **`ory-build-integration`** *(e.g. "wire an Ory webhook into my app")* — pull the runnable subset of an `ory/integrates` template (webhook / config / http-event) into the user's own app and wire it to their Ory project — no contribution/registry concerns.
-- **`ory-contribute-integration`** *(e.g. "contribute a new Ory 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`** *(e.g. "create my e2b sandbox with ory agent security")* — 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`** *(e.g. "wire Ory into my own 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`** *(e.g. "wire Ory into my 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.
-
-### Ory MCP server
-
-Bundled and registered automatically. Exposes the Ory CLI and the Ory Network REST API as MCP tools so Claude 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.
-
-### Local Ory stack
-
-```
-/ory-agent-plugin:local-up      # start a local Ory instance in Docker
-/ory-agent-plugin:local-down    # tear it all down
-/ory-agent-plugin:temporal-up   # start a local Temporal dev server (for ory-temporal-worker)
+```bash
+npx -y -p @ory/claude-code ory-claude permissions enforce
 ```
 
-`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 Claude 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 Claude in chat, e.g. *"grant me use of the Bash 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 Claude, the plugin helps you build Ory into whatever you're working on. Ask Claude *"add Ory login to this app"* and it scaffolds the login, registration, recovery, and settings pages (using [Ory Elements](https://github.com/ory/elements)) wired to a local Ory — no signup or keys needed. Start that local Ory with `/ory-agent-plugin:local-up` (it prints a test email + password to sign in with) and tear it down with `/ory-agent-plugin: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:
+Bundled **skills** (just ask in plain language) 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 MCP server** lets Claude manage identities, projects, and permissions straight from chat.
 
-```bash
-npx -y -p @ory/claude-code ory-claude configure \
-  --project-url https://<id>.projects.oryapis.com \
-  --oauth2-client-id <public OAuth2 client id>
-```
-
-- **`--project-url`** points the plugin at your project. The **agent identity** (machine credentials for Claude'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, configure 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/claude-code ory-claude configure --audit-only
+npx -y -p @ory/claude-code ory-claude configure \
+  --project-url https://<slug>.projects.oryapis.com \
+  --oauth2-client-id <login 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 any configuration the plugin still loads cleanly and runs in **pass-through mode**: skills, slash commands, and audit logging work, but no permission checks run, so nothing is ever blocked. You can stay in pass-through mode indefinitely if you only want the DX features.
-
-### Register the user OAuth2 client
+Claude'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`.
 
-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:
-
-- `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`
-
-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.
+<details>
+<summary>Create the sign-in client by hand</summary>
 
-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 so sign-in survives a busy port:
 
 ```bash
 ory create oauth2-client --project <project-id> \
@@ -177,103 +108,37 @@ 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/claude-code ory-claude 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), Claude'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 Claude 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. Sub-agents launched by the `Task` tool each receive their own typed identity.
-- **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 (and agent → subagent) delegation chain is written to Ory as relations 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.
+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
-
-With an Ory project configured, the plugin runs in **observe mode** by default: every tool call is checked against Ory Permissions, 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. (Without a project configured, the plugin is in pass-through mode — no checks run at all.)
-
-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 Claude 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 Claude ships with (Read, Write, Bash, …):
-
-   ```bash
-   npx -y -p @ory/claude-code ory-claude 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/claude-code ory-claude permissions status
-   ```
-
-   Add permissions for any MCP server tools or custom commands by hand, or via the Ory MCP server from inside Claude (*"grant me use on the Bash tool"*).
-
-4. **Promote to enforce.** Once the observe-mode logs look right, switch over:
-
-   ```bash
-   npx -y -p @ory/claude-code ory-claude permissions enforce
-   ```
+</details>
 
-   Denies now block the tool call; Claude 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`.
+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.
 
-## CLI reference
+## Commands
 
 ```
-npx -y -p @ory/claude-code ory-claude install | uninstall              [--global]
-npx -y -p @ory/claude-code ory-claude configure                         [--project-url <url> --oauth2-client-id <id>] [--api-key <key>] [--audit-only]
-npx -y -p @ory/claude-code ory-claude agent <status|unregister>         Manage the agent's OAuth2 identity
-npx -y -p @ory/claude-code ory-claude permissions <status|bootstrap|observe|enforce>
-npx -y -p @ory/claude-code ory-claude local <up|down|status|seed|logs|env|configure|reset>
-npx -y -p @ory/claude-code ory-claude status
+ory-claude install | uninstall        Install/remove; --reconfigure re-runs setup, --no-configure skips it
+ory-claude status                     Show configuration, identities, permission coverage, recent activity
+ory-claude watch                      Tail the live trace stream (OTel spans)
+ory-claude permissions <cmd>          status | bootstrap | observe (watch) | enforce (block)
+ory-claude configure <flags>          Point at a project by hand (--project-url, --oauth2-client-id, --user-login, --audit-only)
+ory-claude agent <status|unregister>  Manage Claude's own auto-created identity
+ory-claude local <up|down|status|…>   Run / manage a local Ory in Docker
 ```
 
-Highlights:
-
-- `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.
+All prefixed with `npx -y -p @ory/claude-code`.
 
 ## Troubleshooting
 
-- **`/ory-agent-plugin: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/claude-code ory-claude agent unregister` and retry.
-- **`npx` fetches an old version.** Force a fresh fetch: `npx -y -p @ory/claude-code@latest ory-claude …`.
-- **Hooks pinned to an old plugin version.** After a plugin upgrade, run `/plugin marketplace update ory` inside Claude Code (or re-run the npx installer) so the hook commands and MCP server pick up the new release.
-- **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-claude agent unregister` and try again.
+- **`npx` grabbed an old version** — force the latest: `npx -y -p @ory/claude-code@latest ory-claude …`.
+- **Hooks stuck on an old version** — run `/plugin marketplace update ory` inside Claude Code, or re-run the installer.
+- **Want to see what's happening** — `npx -y -p @ory/claude-code ory-claude status` for a snapshot, `npx -y -p @ory/claude-code ory-claude 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/claude-code/` (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)
 - [Claude Code documentation](https://docs.anthropic.com/en/docs/claude-code)
 
 ## License

package/dist/cli/main.js

@@ -54,14 +54,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-claude", "claude-code").then(() => process.exit(0), (err) => {
+            (0, argus_1.runPostInstall)("ory-claude", "claude-code", 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-claude", args);
@@ -90,6 +95,9 @@ function main() {
                 process.exit(1);
             });
             break;
+        case "watch":
+            (0, argus_1.runWatchCommand)("claude-code", args);
+            break;
         case "help":
         case "--help":
         case "-h":
@@ -102,12 +110,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-claude", "claude-code", {
         title: "Claude Code",
@@ -133,7 +135,7 @@ ory-claude — Ory plugin for Claude Code
 
 Usage:
   npx @ory/claude-code <command> [options]
-  npx ory-claude <command> [options]
+  npx -y -p @ory/claude-code ory-claude <command> [options]
 
 Commands:
   install [--global]   Install Ory plugin via claude CLI marketplace
@@ -142,15 +144,16 @@ Commands:
   agent <cmd>          Manage the agent's OAuth2 (DCR) identity (status, unregister)
   permissions <cmd>    Manage permission mode and tool permissions (status, bootstrap, observe, enforce)
   status               Show plugin status and configuration
+  watch [trace-file]   Tail the trace stream (OTel spans) live
   local <cmd>          Manage local Ory dev environment (up, down, status, seed, ...)
 
 Examples:
   npx @ory/claude-code install            # Install remotely (no prior npm install needed)
   npx @ory/claude-code install --global   # Install globally (user scope)
-  npx ory-claude install                                # Install from local/global npm installation
-  npx ory-claude configure --project-url https://your-project.projects.oryapis.com --api-key ory_pat_...
-  npx ory-claude status                                 # Check configuration
-  npx ory-claude uninstall                              # Remove plugin
+  npx -y -p @ory/claude-code ory-claude install                                # Install from local/global npm installation
+  npx -y -p @ory/claude-code ory-claude configure --project-url https://your-project.projects.oryapis.com --api-key ory_pat_...
+  npx -y -p @ory/claude-code ory-claude status                                 # Check configuration
+  npx -y -p @ory/claude-code ory-claude uninstall                              # Remove plugin
 `);
 }
 main();

package/dist/cli/setup.js

@@ -246,10 +246,10 @@ function install(args) {
         installFromProductionMarketplace(scope);
     }
     (0, argus_1.printNextSteps)("Claude Code", fromSource
-        ? "npx ory-claude uninstall --from-source"
+        ? "npx -y -p @ory/claude-code ory-claude uninstall --from-source"
         : isRemoteContext()
             ? "npx @ory/claude-code uninstall"
-            : "npx ory-claude uninstall");
+            : "npx -y -p @ory/claude-code ory-claude uninstall", { binName: "ory-claude", harness: "claude-code" });
 }
 /**
  * Default production install path: register the `ory/claude-plugins` GitHub
@@ -401,7 +401,7 @@ if (require.main === module) {
 ory-claude-setup — Install or remove the Ory plugin for Claude Code
 
 Usage:
-  npx ory-claude-setup [options]
+  npx -y -p @ory/claude-code ory-claude-setup [options]
 
 Options:
   --global       Install to user scope (default: project scope)
@@ -418,6 +418,12 @@ install from the local monorepo checkout instead (used by the dev launcher).
     const args = process.argv.slice(2);
     if (args.includes("--uninstall")) {
         uninstall(args);
+        // Direct `-setup --uninstall` path: also clear stored Ory credentials.
+        // (The `ory-claude 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/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ory/claude-code",
-  "version": "0.11.1",
+  "version": "0.12.0",
   "description": "Ory plugin for Claude Code: scaffolding skills, a local Ory instance, and authentication, authorization, and audit for every tool call",
   "license": "Apache-2.0",
   "homepage": "https://github.com/ory/claude-plugins/tree/master/plugins/ory-agent-plugin",
@@ -75,7 +75,7 @@
     "!dist/**/*.tsbuildinfo"
   ],
   "dependencies": {
-    "@ory/argus": "0.11.1"
+    "@ory/argus": "0.12.0"
   },
   "engines": {
     "node": ">=22"