@ory/continue 1.5.3 → 1.6.0

package/README.md

@@ -103,6 +103,15 @@ npx -y -p @ory/continue ory-cn permissions   # native allowed/blocked state and
 
 Then a denied tool is actually blocked and Continue shows why.
 
+### MCP servers
+
+Continue CLI's `PreToolUse` hook reports an MCP tool under the server's own tool
+name, with no server name and no launch details (`extensions/cli/src/hooks/fireHook.ts`
+and `convertMcpToolToContinueTool` in `extensions/cli/src/tools/index.tsx`).
+The plugin therefore cannot tell an MCP tool from a native one or which server
+it belongs to: every tool, MCP or not, is checked as a native tool under that
+name, and Console MCP server and tool levels do not apply to Continue.
+
 ## Connect to Ory Agent Security
 
 Copy the connection details from the [Ory Console](https://console.ory.sh) under **Agent Security**:
@@ -123,7 +132,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, permission model, native-tool blocks, MCP grants, and observe/enforce posture are provisioned in the Console by someone with project access. At session start the plugin loads or enrolls Continue's Talos runtime credential in the OS credential store; tool paths only read it. Installing needs no workspace privilege.
+**There is nothing else for you to create.** The sign-in client, permission model, native-tool blocks, MCP server access, and observe/enforce posture are provisioned in the Console by someone with project access. At session start the plugin loads or enrolls Continue's Talos runtime credential in the OS credential store; tool paths only read it. Installing needs no workspace privilege.
 
 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.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ory/continue",
-  "version": "1.5.3",
+  "version": "1.6.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.5.3"
+    "@ory/argus": "1.6.0"
   },
   "engines": {
     "node": ">=22"