@ory/amp 1.0.1 → 1.2.0

package/README.md

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

package/dist/cli/main.js

@@ -189,7 +189,7 @@ Commands:
   uninstall [--project-dir <path>] Remove the Ory delegate, plugin, and skills
   configure                        Set or view Ory project URL and API key
   agent <status|unregister>        Manage the agent's OAuth2 (DCR) identity
-  permissions                      Show the live permission mode and per-tool coverage
+  permissions                      Show live mode and native allowed/blocked state
   setup [--project-dir <path>]     Write config directly (fallback)
   status [--project-dir <path>]    Show plugin configuration and status
   watch [--json] [--lines <count>] Follow the live activity/debug log

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ory/amp",
-  "version": "1.0.1",
+  "version": "1.2.0",
   "description": "Ory plugin for Amp (Sourcegraph's coding agent): a permission delegate that authorizes every tool call plus an in-process plugin for session auth and activity auditing",
   "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"
   },
   "devDependencies": {
     "typescript": "^6.0.2",