@tangle-network/sandbox-cli 0.4.1 → 0.5.1

package/hub-reference.md

@@ -65,9 +65,9 @@ Anywhere a command takes a connection (`--connection`, `connections revoke`,
 `agent --connection`), you may pass a raw connection id (`hubconn_...`) or a
 human reference instead:
 
-- `<provider>` — e.g. `github`, resolves when you hold exactly one connection
+- `<provider>`, for example `github`, resolves when you hold exactly one connection
   for that provider.
-- `<provider>:<account>` — e.g. `gmail:alice@example.com`, disambiguates when
+- `<provider>:<account>`, for example `gmail:alice@example.com`, disambiguates when
   you hold several connections for one provider (matches `accountDisplay` or
   `displayName`).
 
@@ -75,7 +75,7 @@ A reference resolves against `tangle hub connections`; revoked connections are
 skipped. If it matches no connection, or more than one, the CLI fails loud and
 lists the candidates so you can pass an id or `provider:account`. Raw ids never
 contact the hub for resolution. The `agent --connection` head is followed by
-`:capabilities`, so it accepts a provider or an id but not `provider:account` —
+`:capabilities`, so it accepts a provider or an id but not `provider:account`;
 use an id when a provider is ambiguous there.
 
 ### OAuth Connect
@@ -306,23 +306,23 @@ tangle hub permissions set --connection hubconn_github_a1 --action github.issues
 
 ### Granting connections to an agent
 
-`tangle agent prompt`/`tangle agent task` expose granted hub connections to the
-agent as MCP tools with `--connection <spec>` (repeatable). Three modes, from
-least to most privilege:
+`tangle agent prompt` exposes granted hub connections to the agent as MCP tools
+with `--connection <spec>` (repeatable). Three modes, from least to most
+privilege:
 
 The spec head is a connection id or a provider name (see
 [Connection references](#connection-references)).
 
 ```bash
 # Least privilege (recommended): the agent sees exactly these tool paths.
-tangle agent task sbx_123 "triage issues" \
+tangle agent prompt sbx_123 "triage issues" \
   --connection github:github.issues.search,github.issues.create
 
 # All capabilities of one connection (by id when a provider is ambiguous).
-tangle agent task sbx_123 "triage issues" --connection hubconn_github_a1:*
+tangle agent prompt sbx_123 "triage issues" --connection hubconn_github_a1:*
 
 # All capabilities of every connected provider (broadest).
-tangle agent task sbx_123 "do the thing" --connection '*:*'
+tangle agent prompt sbx_123 "do the thing" --connection '*:*'
 ```
 
 A grant controls what the agent can **see**. Each call is still policy-gated
@@ -337,11 +337,12 @@ actions still prompt. The grant is persistent and scoped to the named
 connections only.
 
 ```bash
-tangle agent task sbx_123 "file the weekly report" \
+tangle agent prompt sbx_123 "file the weekly report" \
   --connection github:* --allow-writes
 ```
 
-Revert the bulk grant at any time — it deletes only the rows `--allow-writes`
+Revert the bulk grant at any time.
+It deletes only the rows `--allow-writes`
 created, leaving manual `permissions set` decisions intact:
 
 ```bash

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tangle-network/sandbox-cli",
-  "version": "0.4.1",
+  "version": "0.5.1",
   "description": "CLI for Tangle Sandbox operations",
   "type": "module",
   "bin": {
@@ -15,17 +15,17 @@
     "hub-reference.md"
   ],
   "dependencies": {
-    "@tangle-network/agent-core": "0.4.19",
+    "@tangle-network/agent-core": "0.4.22",
     "@tangle-network/agent-eval": "0.125.0",
-    "@tangle-network/agent-interface": "0.32.0",
+    "@tangle-network/agent-interface": "0.34.0",
     "@tangle-network/agent-runtime": "0.103.1",
     "chalk": "^5.4.1",
     "commander": "12.1.0",
     "dotenv": "17.2.3",
     "ora": "^9.4.0",
     "ws": "^8.20.0",
-    "@tangle-network/hub-sdk": "0.3.0",
-    "@tangle-network/sandbox": "0.12.1"
+    "@tangle-network/sandbox": "0.15.0",
+    "@tangle-network/hub-sdk": "0.3.0"
   },
   "devDependencies": {
     "@types/node": "25.6.0",