Update Composio example for the tools repo move

The tools repo moved to LuxorLabs/tenki-composio-tools (old TenkiCloud
URLs redirect); update the links. Drop the workspaceId plumbing from
verify.mjs/agent.mjs/README -- the workspace is inferred from the API
key, workspaceId is optional in the published 0.1.0 typings, and the
unreleased 0.2.0 removes the option entirely. Pins unchanged (0.2.0 is
not on npm yet); CI skip stays (needs COMPOSIO_API_KEY).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

Author: opencolin

README.md

@@ -102,7 +102,7 @@ First-party packages you can install directly in your own project:
 
 | Integration | Install | What it does |
 | --- | --- | --- |
-| [Composio tools](https://github.com/TenkiCloud/composio-tools) | `npm install @tenkicloud/composio-tools` | Create, execute, snapshot, and terminate tools for Composio agents |
+| [Composio tools](https://github.com/LuxorLabs/tenki-composio-tools) | `npm install @tenkicloud/composio-tools` | Create, execute, snapshot, and terminate tools for Composio agents |
 | [Covalent executor](https://github.com/TenkiCloud/covalent-tenki-plugin) | `pip install covalent-tenki-plugin` | Runs Covalent workflow tasks in Tenki microVMs |
 | [GitHub Actions](https://github.com/TenkiCloud/actions) | `uses: TenkiCloud/actions/setup-cli@v1` | Installs the Tenki CLI and builds sandbox templates in CI |
 | [Go SDK](https://github.com/TenkiCloud/tenki-sdk-go) | `go get github.com/TenkiCloud/tenki-sdk-go/sandbox` | Go client for the Tenki Sandbox API |

examples/composio-tenki/README.md

@@ -1,6 +1,6 @@
 # Composio agent on Tenki
 
-Give any [Composio](https://composio.dev) agent disposable Tenki microVMs. The official [`@tenkicloud/composio-tools`](https://github.com/TenkiCloud/composio-tools) package registers a **Tenki custom toolkit** — the agent gets `CREATE_SANDBOX`, `EXEC_COMMAND`, `LIST_SANDBOXES`, `GET_SANDBOX`, `CREATE_SNAPSHOT`, and `TERMINATE_SANDBOX`, all running in-process against the Tenki SDK. No extra backend.
+Give any [Composio](https://composio.dev) agent disposable Tenki microVMs. The official [`@tenkicloud/composio-tools`](https://github.com/LuxorLabs/tenki-composio-tools) package registers a **Tenki custom toolkit** — the agent gets `CREATE_SANDBOX`, `EXEC_COMMAND`, `LIST_SANDBOXES`, `GET_SANDBOX`, `CREATE_SNAPSHOT`, and `TERMINATE_SANDBOX`, all running in-process against the Tenki SDK. No extra backend.
 
 ## The integration (the whole thing)
 
@@ -15,7 +15,7 @@ const session = await composio.sessions.create("default", {
 // the agent can now call LOCAL_TENKI_CREATE_SANDBOX, LOCAL_TENKI_EXEC_COMMAND, …
 ```
 
-`tenkiToolkit()` reads `TENKI_API_KEY` from the environment (or takes `authToken`/`workspaceId` options). Custom toolkits are **session-scoped**: tool calls run through `session.execute(slug, args)`, and definitions come from `session.customTools()`.
+`tenkiToolkit()` reads `TENKI_API_KEY` from the environment (or takes an `authToken` option); the workspace is inferred from the key. Custom toolkits are **session-scoped**: tool calls run through `session.execute(slug, args)`, and definitions come from `session.customTools()`.
 
 ## Two files
 

examples/composio-tenki/agent.mjs

@@ -27,7 +27,6 @@ const cfg = (key) => {
 
 const MODEL = process.env.ANTHROPIC_MODEL ?? "claude-sonnet-5";
 const authToken = process.env.TENKI_AUTH_TOKEN || process.env.TENKI_API_KEY || cfg("auth_token");
-const workspaceId = process.env.TENKI_WORKSPACE_ID || cfg("current_workspace_id") || undefined;
 
 for (const [name, value] of [
 	["COMPOSIO_API_KEY", process.env.COMPOSIO_API_KEY],
@@ -44,7 +43,7 @@ const composio = new Composio({ apiKey: process.env.COMPOSIO_API_KEY });
 const anthropic = new Anthropic();
 
 const session = await composio.sessions.create("default", {
-	experimental: { customToolkits: [tenkiToolkit({ authToken, workspaceId })] },
+	experimental: { customToolkits: [tenkiToolkit({ authToken })] },
 });
 
 // Anthropic tool defs come straight from the session's custom-tool registry.

examples/composio-tenki/verify.mjs

@@ -24,7 +24,6 @@ const cfg = (key) => {
 
 const composioKey = process.env.COMPOSIO_API_KEY;
 const authToken = process.env.TENKI_AUTH_TOKEN || process.env.TENKI_API_KEY || cfg("auth_token");
-const workspaceId = process.env.TENKI_WORKSPACE_ID || cfg("current_workspace_id") || undefined;
 
 if (!composioKey) {
 	console.error("No COMPOSIO_API_KEY. Get one at https://app.composio.dev.");
@@ -37,7 +36,7 @@ if (!authToken) {
 
 const composio = new Composio({ apiKey: composioKey });
 const session = await composio.sessions.create("default", {
-	experimental: { customToolkits: [tenkiToolkit({ authToken, workspaceId })] },
+	experimental: { customToolkits: [tenkiToolkit({ authToken })] },
 });
 
 /** Execute one LOCAL_TENKI_* tool and assert Composio + the tool itself both succeeded. */