@ory/continue 1.0.1 → 1.2.0

package/README.md

@@ -98,7 +98,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/continue ory-cn permissions   # what the project grants, and the live mode
+npx -y -p @ory/continue ory-cn permissions   # native allowed/blocked state and live mode
 ```
 
 Then a denied tool is actually blocked and Continue shows why.
@@ -123,7 +123,7 @@ npx -y -p @ory/continue ory-cn 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 Continue 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 Continue 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.
 
@@ -133,8 +133,8 @@ Settings are saved to `~/.config/ory-agent-plugins/config.json` and shared acros
 
 ```
 ory-cn install | uninstall         Install (add --project-url to also connect Agent Security) / remove
-ory-cn status                      Show configuration, identities, permission coverage, recent activity
-ory-cn permissions <cmd>           status  (read-only; grants + posture live in the Ory Console)
+ory-cn status                      Show configuration, identities, native tool access, recent activity
+ory-cn permissions <cmd>           status  (read-only; blocks + posture live in the Ory Console)
 ory-cn configure <flags>           Connect a project (--project-url) or --disconnect
 ory-cn agent <status|unregister>   Manage Continue's own auto-created identity
 ory-cn local <up|down|status|…>    Run / manage a local Ory in Docker

package/dist/cli/main.js

@@ -178,7 +178,7 @@ Commands:
   uninstall              Remove the Ory hooks and skills
   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 hooks directly to .continue/settings.json
   status                 Show plugin status and configuration
   watch [--json] [--lines <count>]

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ory/continue",
-  "version": "1.0.1",
+  "version": "1.2.0",
   "description": "Ory plugin for Continue CLI (cn): scaffolding skills, a local Ory instance, and authentication, authorization, and audit for every tool call",
   "license": "Apache-2.0",
   "homepage": "https://ory.com",
@@ -70,7 +70,7 @@
   ],
   "dependencies": {
     "reova": "^0.7.0",
-    "@ory/argus": "1.0.1"
+    "@ory/argus": "1.2.0"
   },
   "engines": {
     "node": ">=22"