@ory/goose 1.0.0 → 1.1.0

package/README.md

@@ -94,7 +94,7 @@ Everything the plugin does is observable out of the box:
 Once connected, the deny posture lives on the Ory project: when the observe-mode activity looks right, an admin promotes it to **enforce** in the **Ory Console** (Agent Security). Every session reads that posture live, so nothing has to be reinstalled.
 
 ```bash
-npx -y -p @ory/goose ory-goose permissions   # what the project grants, and the live mode
+npx -y -p @ory/goose ory-goose permissions   # native allowed/blocked state and live mode
 ```
 
 Then a denied tool is actually blocked and Goose shows why.
@@ -119,7 +119,7 @@ npx -y -p @ory/goose ory-goose configure \
 
 **Ory Network or OEL.** Either works. For an Ory Network project the URL is `https://<slug>.projects.oryapis.com`; for a self-hosted **Ory Enterprise License** deployment, point `--project-url` at that deployment's base URL and use the sign-in client id from its Agent Security configuration. Everything downstream — sign-in, checks, delegation — is identical.
 
-**There is nothing else for you to create.** The sign-in client, the permission model, the per-tool grants and blocks, and the observe/enforce posture are all provisioned in the Console by someone with project access. At runtime the plugin only *reads* permissions — it has no write path into your project, which is why installing it needs no workspace privilege. Each Goose session registers its own identity automatically on first use.
+**There is nothing else for you to create.** The sign-in client, permission model, native-tool blocks, MCP grants, and observe/enforce posture are provisioned in the Console by someone with project access. At runtime the plugin only *reads* permissions, so installing it needs no workspace privilege. Each Goose session registers its own identity automatically on first use.
 
 Sign-in runs at the start of every session and never blocks — a declined, skipped, or timed-out login simply leaves that session without a user identity.
 
@@ -129,8 +129,8 @@ Settings are saved to `~/.config/ory-agent-plugins/config.json` and shared acros
 
 ```
 ory-goose install | uninstall        Install (add --project-url to also connect Agent Security) / remove; --global installs for every project
-ory-goose status                     Show configuration, identities, permission coverage, registration, recent activity
-ory-goose permissions <cmd>          status  (read-only; grants + posture live in the Ory Console)
+ory-goose status                     Show configuration, identities, native tool access, registration, recent activity
+ory-goose permissions <cmd>          status  (read-only; blocks + posture live in the Ory Console)
 ory-goose configure <flags>          Connect a project (--project-url) or --disconnect
 ory-goose agent <status|unregister>  Manage Goose's own auto-created identity
 ory-goose local <up|down|status|…>   Run / manage a local Ory in Docker

package/dist/cli/main.js

@@ -175,7 +175,7 @@ Commands:
   uninstall [--global]   Remove the Ory plugin
   configure              Set or view Ory project URL and API key
   agent <cmd>            Manage the agent's OAuth2 (DCR) identity (status, unregister)
-  permissions            Show the live permission mode and per-tool coverage
+  permissions            Show live mode and native allowed/blocked state
   setup [--project-dir]  Write the plugin tree directly (advanced)
   status                 Show plugin status and configuration
   watch [--json] [--lines <count>]

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ory/goose",
-  "version": "1.0.0",
+  "version": "1.1.0",
   "description": "Ory plugin for Goose (Block's open-source agent CLI): scaffolding skills, a local Ory instance, and authentication, authorization, and audit for every tool call",
   "license": "Apache-2.0",
   "homepage": "https://ory.com",
@@ -69,7 +69,7 @@
   ],
   "dependencies": {
     "reova": "^0.7.0",
-    "@ory/argus": "1.0.0"
+    "@ory/argus": "1.1.0"
   },
   "devDependencies": {
     "typescript": "^6.0.2",