@andreprado/agentkit 0.1.0 → 0.2.0

package/src/templates/skills/agentkit-improve/SKILL.md

@@ -1,96 +1,17 @@
 ---
 name: agentkit-improve
-description: Use when improving an AgentKit Agent Capsule from hosted or local production evidence, including collected traces, generated regression evals, local replay, channel failures, or post-deploy behavior fixes.
+description: Improve a capsule using local conversation traces, regression evals, and isolated replay.
 ---
 
-# AgentKit Improve
+# Improve Locally
 
-Use this when production or local conversation evidence should drive a fix.
-
-## Boundary
-
-AgentKit Cloud exports evidence. The local coding agent edits the capsule, writes evals, runs replay, and deploys. Do not expect hosted AgentKit Cloud to change source files.
-
-## Workflow
-
-1. Collect evidence:
-
-```sh
-npm run agentkit -- improve collect --deploy --since 24h
-```
-
-Hosted conversation reads require a deploy access token even when a deploy manifest says `access.mode: "public"`. If collection fails with auth, refresh the local token:
-
-```sh
-npm run agentkit -- access token create agentkit-chat-ui --out .agentkit/chat-access-token.json
-```
-
-For one known conversation:
-
-```sh
-npm run agentkit -- improve collect --deploy --conversation-id <conversation-id>
-```
-
-2. Read the generated report:
-
-```txt
-.agentkit/improve/<run>/report.json
-.agentkit/improve/<run>/traces/
-```
-
-3. Before patching, identify the smallest testable lesson from each relevant trace:
-
-- Did the agent miss a required field?
-- Did it expose raw tool output, a full schedule, an internal id, or a technical error?
-- Did it write externally without confirmation?
-- Did it use the wrong timezone, duration, business hour, or availability assumption?
-- Did a tool error or provider limit produce a bad client response?
-
-4. Generate regression evals:
+Read `docs/guides/improve-local.md` and `docs/guides/replay-local-traces.md` from the installed docs root.
 
 ```sh
+npm run agentkit -- improve collect --since 24h
 npm run agentkit -- improve evals .agentkit/improve/<run>
-```
-
-5. Review or rewrite generated evals so they assert the behavior, not brittle transcript wording. If the bug involved a tool call, assert the persisted tool call input or absence of the unsafe call.
-
-6. Patch the capsule. Likely files:
-
-```txt
-prompts/instructions.md
-agentkit.config.ts
-tools/
-knowledge/
-evals/
-```
-
-7. Verify:
-
-```sh
-npm run typecheck
-npm run agentkit -- inspect
-npm run eval
 npm run agentkit -- replay .agentkit/improve/<run> --against local
+npm run eval
 ```
 
-8. Deploy only after local evals and replay pass:
-
-```sh
-npm run agentkit -- deploy --smoke "hello"
-```
-
-## Rules
-
-- Keep `.agentkit/improve/` out of commits.
-- Review generated evals before committing them.
-- AgentKit redacts common email, phone, bearer token, and key patterns in generated eval text, but you must still remove or generalize domain-specific client PII.
-- If a tool writes externally, deletes, charges money, sends email, or touches real customer systems, make the tool branch on `ctx.runtime.environment === "eval"`.
-- Do not paste secret values into reports, prompts, evals, or Knowledge files.
-- Do not try to read the hosted database directly. Use authenticated AgentKit CLI/API routes only.
-- If replay uses a real provider instead of `test/fake`, say that in the final response.
-
-## References
-
-- `references/trace-packets.md`
-- `references/replay-side-effects.md`
-- `templates/regression.eval.md`
+Use the failing trace to make a focused change to prompts, tools, schema, or config. Keep regression checks and fixture external writes in eval mode. Review bundles for secrets and customer data before sharing; files remain local.

package/src/templates/skills/agentkit-improve/references/trace-packets.md

@@ -11,7 +11,7 @@
 
 Use `report.json` for a quick index and `traces/<trace_id>.json` for the full conversation trace.
 
-The bundle can contain hosted or local traces. Treat both as sensitive source material. Do not commit `.agentkit/improve/`.
+The bundle can contain local traces. Treat both as sensitive source material. Do not commit `.agentkit/improve/`.
 
 Generated evals belong in:
 

package/src/templates/skills/agentkit-provider/SKILL.md

@@ -13,7 +13,6 @@ Do not choose a real provider automatically. Ask the owner which provider to use
 
 ## ChatGPT / Codex
 
-When the owner chooses their Codex subscription, follow `docs/guides/use-provider.md` (resolve it from `agentkit docs path`). Run `agentkit provider login openai-codex` in an interactive terminal and configure `provider: { name: "openai-codex", model: "gpt-5.4" }`. Use `agentkit provider status openai-codex` to check local login status. No provider API key is needed; preserve unrelated tool/service secrets. This creates an AgentKit OAuth session outside the capsule, without reading the Codex app's cache. Chat, dev, and eval renew the session through Pi. This login is local-only: choose an API-key provider with managed secrets for deploys.
 
 ## Workflow (API-Key Providers)
 

package/src/templates/skills/agentkit-security/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: agentkit-security
-description: Use before or during AgentKit work involving secrets, external APIs, tools, evals from real data, public access, hosted deploys, or messaging channels.
+description: Use before or during AgentKit work involving secrets, external APIs, tools, evals from real data, public access, or messaging channels.
 ---
 
 # AgentKit Security
@@ -34,7 +34,6 @@ skills/
 
 - `.env.schema` stores secret names only.
 - Ignored `.env` stores local development values only.
-- Hosted production uses managed secrets.
 - Tools receive only secrets listed in that tool's `secrets` field.
 - Prefer `ctx.secrets` over direct `process.env` reads in tools.
 - Add `permissions` for external capabilities.
@@ -44,7 +43,6 @@ skills/
 - Remove client PII before writing evals.
 - Keep `.agentkit/improve/` bundles out of commits and review generated regression evals before committing.
 - Guard replay/eval mode inside external write tools with `ctx.runtime.environment === "eval"`.
-- Treat hosted deploy URLs as addresses, not access control. Hosted chat, conversation reads, and trace reads require a deploy access token even if a config says `access.mode: "public"`.
 
 ## Checks
 

package/src/templates/skills/agentkit-tools/SKILL.md

@@ -17,7 +17,7 @@ When the owner asks to use TypeSafe/Jev for a capsule capability, follow `docs/g
    - End read-only permissions with `:read`.
    - Non-read permissions are operator-only: chat, channels, and evals cannot execute them automatically.
 4. Register the tool in `agentkit.config.ts`.
-5. Keep secret names in `.env.schema`; values stay in ignored `.env` or hosted managed secrets.
+5. Keep secret names in `.env.schema`; values stay in ignored `.env`.
 6. Use `ctx.clock` for date-sensitive tool logic instead of calling `new Date()` directly.
 7. Verify destructive or external side effects through a reviewed direct `agentkit tool` invocation; evals should assert that automatic execution is blocked.
 8. Add deterministic fixtures, fake branches, or direct tool inputs for important success and failure paths.

package/src/templates/skills/agentkit-tools/examples/database-write.tool.md

@@ -7,7 +7,7 @@ import { defineTool } from "@andreprado/agentkit";
 
 export const saveNote = defineTool({
   name: "save_note",
-  description: "Saves a note in the AgentKit-managed database.",
+  description: "Saves a note in the AgentKit-local database.",
   inputSchema: {
     type: "object",
     properties: {
@@ -32,4 +32,3 @@ export const saveNote = defineTool({
   },
 });
 ```
-

package/src/templates/skills/agentkit-troubleshooting/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: agentkit-troubleshooting
-description: Use when an AgentKit command, local chat, tool, eval, Knowledge sync, channel, or deploy fails and the coding agent needs to diagnose from CLI output and route to the right narrow skill or docs guide.
+description: Use when an AgentKit command, local chat, tool, eval, Knowledge sync, channel, fails and the coding agent needs to diagnose from CLI output and route to the right narrow skill or docs guide.
 ---
 
 # AgentKit Troubleshooting
@@ -11,7 +11,7 @@ Use this when something fails.
 
 1. Read the exact error code and message.
 2. Run the narrow inspect command before guessing.
-3. Route to a task skill when the failure points to config, tools, database, provider, evals, deploy, Knowledge, or channels.
+3. Route to a task skill when the failure points to config, tools, database, provider, evals, Knowledge, or channels.
 4. Load `llms-full.txt` only when the narrow skill and guide do not explain the behavior.
 5. If the failure appears to be an AgentKit bug, missing docs, or unclear recovery path, create a local feedback draft after diagnosis.
 
@@ -37,11 +37,6 @@ For tool issues:
 npm run agentkit -- tool <tool_name> --input '<json>'
 ```
 
-For deploy issues:
-
-```sh
-npm run agentkit -- deploy doctor
-```
 
 For AgentKit product feedback:
 
@@ -52,7 +47,7 @@ npm run agentkit -- feedback create --about last-run --kind bug --summary "short
 For production behavior issues:
 
 ```sh
-npm run agentkit -- improve collect --deploy --since 24h
+npm run agentkit -- improve collect --since 24h
 npm run agentkit -- improve evals .agentkit/improve/<run>
 npm run agentkit -- replay .agentkit/improve/<run> --against local
 ```
@@ -64,13 +59,12 @@ npm run agentkit -- replay .agentkit/improve/<run> --against local
 - provider not chosen: stay on `test/fake` or ask the owner;
 - schema missing: run `db migrate` and check `schema.sql`;
 - tool validation failed: check `inputSchema` and `outputSchema`;
-- channel secret missing: set hosted managed secret, not source files;
+- channel secret missing: set local secret, not source files;
 - production behavior drift: collect an improve bundle and convert it to regression evals before patching;
 - local AgentKit skills are stale: run `npm run agentkit -- skills sync`.
 
 ## Feedback Rules
 
 - `feedback create` writes a local draft only; it does not send anything.
-- Review the draft before `feedback send`.
-- Sending requires `agentkit login --token agk_user_...`.
+- Review the draft before sharing it manually.
 - Do not paste `.env` values, provider keys, cookies, client PII, or full private transcripts into feedback.

package/src/templates/support.ts

@@ -1,63 +1,11 @@
 import type { AgentTemplate } from ".";
+import { commonTemplateFiles } from "./common";
 
 export const supportTemplate: AgentTemplate = {
   name: "support",
   files(projectName: string, context = {}) {
     return [
-      {
-        path: "package.json",
-        contents: `${JSON.stringify(
-          {
-            name: projectName,
-            private: true,
-            type: "module",
-            scripts: {
-              agentkit: "agentkit",
-              dev: "agentkit dev",
-              chat: "agentkit chat",
-              eval: "agentkit eval run",
-              typecheck: "tsc --noEmit",
-            },
-            dependencies: {
-              "@andreprado/agentkit": context.agentkitDependency ?? "workspace:*",
-            },
-            devDependencies: {
-              "@types/node": "^24.12.4",
-              typescript: "^5.9.3",
-            },
-          },
-          null,
-          2,
-        )}
-`,
-      },
-      {
-        path: "tsconfig.json",
-        contents: `${JSON.stringify(
-          {
-            compilerOptions: {
-              target: "ES2022",
-              module: "ESNext",
-              moduleResolution: "Bundler",
-              strict: true,
-              skipLibCheck: true,
-              noEmit: true,
-              types: ["node"],
-            },
-            include: ["**/*.ts"],
-          },
-          null,
-          2,
-        )}
-`,
-      },
-      {
-        path: ".gitignore",
-        contents: `.env
-.agentkit/
-node_modules/
-`,
-      },
+      ...commonTemplateFiles(projectName, context),
       {
         path: ".env.schema",
         contents: `# Optional: add real provider keys after switching away from test/fake.
@@ -74,7 +22,7 @@ import { lookupOrder } from "./tools/lookup-order";
 
 export default defineAgent({
   name: "${projectName}",
-  runtime: "edge",
+  runtime: "local",
   provider: {
     name: "test",
     model: "fake",
@@ -89,7 +37,7 @@ export default defineAgent({
     driver: "agentkit",
     path: ".agentkit/agentkit.db",
     database: {
-      driver: "turso",
+      driver: "sqlite",
       schema: "./schema.sql",
     },
   },
@@ -220,7 +168,7 @@ Do not only edit prompts. For every meaningful requirement in the owner's reques
 - schema/migration plus tool for durable records;
 - eval for privacy, confirmation, required fields, date/time behavior, business rules, and regressions;
 - fixture, seed data, fake branch, or direct tool check for integrations and failure paths;
-- deploy/readiness check for hosted secrets, channels, integrations, or production access.
+- local config and secret checks for channels and external tools.
 
 If a rule protects privacy, money, bookings, external writes, customer data, business hours, or safety, it must have an eval or deterministic check before you call the capsule done. If a real conversation exposes a bug, convert it into the smallest regression eval before or alongside the fix.
 
@@ -243,20 +191,9 @@ If a rule protects privacy, money, bookings, external writes, customer data, bus
 ## Testing With A UI
 
 - Local UI: run \`npm run dev\`, open the printed \`Chat:\` URL, and tell the owner the exact URL.
-- Hosted UI: after \`npm run agentkit -- deploy\`, run \`npm run agentkit -- chat-ui --deploy\`, open the printed \`Chat:\` URL, and tell the owner it is connected to the hosted deploy.
 - \`test/fake\` is deterministic. It is useful for scaffold checks, direct tool checks, and fake-provider evals, but it does not validate natural conversation quality.
 - Before claiming real conversation behavior is tested, ask the owner which provider to use: OpenRouter, OpenAI, Anthropic, OpenCode Zen, OpenCode Go, or another supported provider. Do not choose for them.
 
-## Hosted Deploy
-
-- Local scaffold, chat, eval, dev, inspect, tool, and build commands are token-free.
-- Hosted deploy requires an invited AgentKit Cloud alpha token. If no token is stored yet, ask the owner for one and run \`npm run agentkit -- login --token <token>\`.
-- Put production secret values into managed secrets with \`npm run agentkit -- secret set <NAME> --from-local-env\`, \`--from-env\`, or \`--stdin\`, not into committed files or shell history.
-- Deploy with \`npm run agentkit -- deploy\`, then check \`npm run agentkit -- deploy status\`.
-- Hosted deploy writes the local chat/UI deploy access token to \`.agentkit/chat-access-token.json\`. Create extra client-facing tokens with \`npm run agentkit -- access token create <name> --out <path>\` when a separate website or app needs its own credential.
-- Use \`npm run agentkit -- deploy --smoke "hello"\` or \`npm run agentkit -- deploy smoke --message "hello"\` for an official hosted chat smoke check.
-- Do not run operator/admin commands from a user capsule.
-
 ## Files
 
 - \`agentkit.config.ts\`: agent contract and tool registry.
@@ -334,16 +271,9 @@ npm run dev
 
 Open the printed \`Chat:\` URL and tell the owner the exact URL.
 
-Hosted deploy UI:
-
-\`\`\`sh
-npm run agentkit -- deploy
-npm run agentkit -- chat-ui --deploy
-\`\`\`
 
-Open the printed \`Chat:\` URL and tell the owner this local UI is connected to the hosted deploy.
 
-Before claiming real conversation behavior has been tested, ask the owner which provider to use: OpenRouter, OpenAI, Anthropic, OpenCode Zen, OpenCode Go, or another supported provider. Do not choose for them. After they choose, update \`agentkit.config.ts\`, \`.env.schema\`, local secrets, hosted secrets if deploying, then rerun chat/UI checks.
+Before claiming real conversation behavior has been tested, ask the owner which provider to use: OpenRouter, OpenAI, Anthropic, OpenCode Zen, OpenCode Go, or another supported provider. Do not choose for them. After they choose, update \`agentkit.config.ts\`, \`.env.schema\`, local secrets, then rerun chat/UI checks.
 
 If you add a tool, also run a fake-provider tool smoke test:
 
@@ -366,26 +296,12 @@ Tools that need agent-owned tables should use canonical \`ctx.db\` from the tool
 The recommended dual-storage pattern is:
 
 1. Add tables to \`schema.sql\`.
-2. Keep \`storage.driver: "agentkit"\` for deploy-ready capsules.
+2. Keep \`storage.driver: "agentkit"\` for local capsules.
 3. Run \`npm run agentkit -- tool ...\` or \`npm run chat ...\` locally. AgentKit applies \`schema.sql\` to local development storage.
 4. Use \`npm run agentkit -- db migrate\`, \`db reset --yes\`, \`db seed\`, and \`db shell\` for local database setup and inspection.
-5. Run \`npm run agentkit -- deploy\`. AgentKit migrates/provisions hosted storage internally.
 
 \`schema.sql\` is an idempotent bootstrap file. Use \`CREATE TABLE IF NOT EXISTS\`, \`CREATE INDEX IF NOT EXISTS\`, and safe additive changes. Use ordered \`migrations/*.sql\` for production-shaped schema evolution; \`npm run agentkit -- db migrate\` applies unapplied local migrations before \`schema.sql\`.
 
-## Hosted Deploy
-
-This capsule is deploy-ready by default.
-
-1. Keep tools edge-safe and use \`ctx.db\` instead of importing database drivers.
-2. Run \`npm run agentkit -- build\` only when you want to validate the artifact locally.
-3. If the owner has not logged in yet, ask for an invited AgentKit Cloud alpha token and run \`npm run agentkit -- login --token <token>\`.
-4. Put production secrets into managed secrets with \`npm run agentkit -- secret set <NAME> --from-local-env\`, \`--from-env\`, or \`--stdin\`.
-5. Run \`npm run agentkit -- deploy\`.
-6. Run \`npm run agentkit -- chat-ui --deploy\` to test the hosted agent through a local UI using the auto-created \`.agentkit/chat-access-token.json\`. Create extra client-facing deploy access tokens with \`npm run agentkit -- access token create <name> --out <path>\` when a separate website or app needs its own credential.
-7. Use \`npm run agentkit -- deploy --smoke "hello"\` during deploy or \`npm run agentkit -- deploy smoke --message "hello"\` afterward for an official hosted smoke check.
-
-AgentKit owns hosted infrastructure and production secrets. Do not put production secret values in this capsule. Do not run operator/admin commands from a user capsule.
 `,
       },
       {
@@ -423,7 +339,7 @@ npm run dev
 The support template includes a local \`lookup_order\` TypeScript tool and uses \`test/fake\` by default.
 \`test/fake\` does not validate real conversation quality. The owner must choose OpenRouter, OpenAI, Anthropic, OpenCode Zen, OpenCode Go, or another supported provider before real model behavior is tested.
 
-For UI testing, run \`npm run dev\` and open the printed \`Chat:\` URL. After hosted deploy, run \`npm run agentkit -- chat-ui --deploy\` and open its printed \`Chat:\` URL.
+For UI testing, run \`npm run dev\` and open the printed \`Chat:\` URL.
 `,
       },
     ];

package/docs/guides/add-managed-composio.md

@@ -1,165 +0,0 @@
-# Add Managed Composio
-
-## Goal
-
-Enable AgentKit-managed Composio for one deployed agent so the agent can use explicitly allowed external app actions without the user owning Composio credentials.
-
-Use BYO `defineTool` wrappers instead when the user wants to use their own Composio account/API key for free.
-
-## Contract
-
-Managed Composio is paid hosted AgentKit infrastructure:
-
-- It works per agent/project, not per client.
-- It requires an AgentKit Cloud account with `managed_composio`.
-- AgentKit Cloud injects `COMPOSIO_API_KEY`; do not put it in `.env`, `.env.schema`, or `agentkit.config.ts`.
-- AgentKit Cloud resolves toolkit auth configs from its managed registry. The capsule owner only declares allowed toolkits/actions.
-- AgentKit Cloud assigns the deployed Composio `user_id` from the account, project, agent, and integration name. The local inspect/build id is only a preview.
-- The agent gets one generated tool, `agentkit_composio_execute`, only when explicit Composio action slugs are configured.
-- Anonymous deploys cannot use managed Composio.
-
-## Minimal Config
-
-Edit `agentkit.config.ts`:
-
-```ts
-import { composioManaged, defineAgent } from "@andreprado/agentkit";
-
-export default defineAgent({
-  name: "acme-receptionist",
-  runtime: "edge",
-  provider: {
-    name: "test",
-    model: "fake",
-  },
-  instructions: "./prompts/instructions.md",
-  secrets: [],
-  tools: [],
-  integrations: [
-    composioManaged({
-      toolkits: ["gmail", "googlecalendar"],
-      tools: {
-        gmail: ["GMAIL_FETCH_EMAILS", "GMAIL_SEND_EMAIL"],
-        googlecalendar: [
-          "GOOGLECALENDAR_EVENTS_LIST",
-          "GOOGLECALENDAR_CREATE_EVENT",
-          "GOOGLECALENDAR_UPDATE_EVENT",
-        ],
-      },
-      confirmExternalWrites: true,
-    }),
-  ],
-  access: {
-    mode: "private",
-  },
-  storage: {
-    driver: "agentkit",
-    database: {
-      driver: "turso",
-    },
-  },
-});
-```
-
-## Deploy
-
-```sh
-agentkit login --token agk_user_...
-agentkit deploy doctor
-agentkit deploy
-agentkit integrations status --toolkit googlecalendar
-```
-
-Expected readiness:
-
-- Hosted deploy access is active through `cloudflare_deploy_alpha` or purchased/manual deploy slots.
-- `managed_composio` is active.
-- `COMPOSIO_API_KEY` appears as an AgentKit-managed secret, not a user-managed hosted secret.
-- Each configured toolkit auth config is available in AgentKit Cloud.
-
-## Connect Apps
-
-The Composio connect link is deploy-scoped, so declare `composioManaged(...)` first, deploy, then connect. After deploy, create a hosted Composio Connect Link:
-
-```sh
-agentkit integrations connect composio --toolkit gmail
-agentkit integrations connect composio --toolkit googlecalendar
-```
-
-AgentKit prints a URL. Send that URL to the person who owns the app account.
-
-If the deploy has only one toolkit, `--toolkit` can be omitted.
-
-`agentkit deploy` prints the recommended `integrations connect composio --toolkit <slug>` command for each configured toolkit in its production handoff.
-
-## Calendar Defaults
-
-For Google Calendar agents, include read and write actions together. Do not expose only `GOOGLECALENDAR_CREATE_EVENT`; users naturally ask to see availability before booking.
-
-Use these starter actions:
-
-```ts
-googlecalendar: [
-  "GOOGLECALENDAR_EVENTS_LIST",
-  "GOOGLECALENDAR_CREATE_EVENT",
-  "GOOGLECALENDAR_UPDATE_EVENT",
-]
-```
-
-`GOOGLECALENDAR_CREATE_EVENT` requires extra care:
-
-- `start_datetime` must be explicit UTC RFC3339, such as `2026-06-03T15:00:00Z` for 12:00 in `America/Sao_Paulo`.
-- `event_duration_minutes` or `event_duration_hour` must be explicit. AgentKit blocks the implicit Composio default because `event_duration_minutes` defaults to 30.
-- Confirm the final title, date, local time, duration, timezone, and attendees/location when relevant before creating or updating an event.
-
-## Write Confirmation
-
-Managed Composio requires operator invocation for external write actions. If an integration allows create, update, delete, send, patch, move, insert, clear, remove, import, or quick-add actions, AgentKit blocks that generated tool during model-driven chat, channel, and eval runs. Review the exact action and invoke `agentkit_composio_execute` directly with `agentkit tool`; write actions also require `confirmed: true` by default.
-
-`confirmExternalWrites: false` disables only Composio's secondary `confirmed` input check. It does not bypass AgentKit's operator-only permission boundary:
-
-```ts
-composioManaged({
-  toolkits: ["googlecalendar"],
-  tools: {
-    googlecalendar: ["GOOGLECALENDAR_EVENTS_LIST", "GOOGLECALENDAR_CREATE_EVENT"],
-  },
-  confirmExternalWrites: false,
-})
-```
-
-## Verification
-
-```sh
-agentkit inspect
-agentkit build --target cloudflare
-agentkit deploy doctor
-agentkit integrations status --toolkit googlecalendar
-```
-
-Expected:
-
-- `inspect.integrations[0].provider` is `composio`.
-- `inspect.tools` includes `agentkit_composio_execute` when allowed actions are configured.
-- Build manifest includes `integrations`.
-- Build manifest includes `COMPOSIO_API_KEY`.
-- `deploy doctor` does not ask the user to set `COMPOSIO_API_KEY`.
-- `deploy doctor` reports each configured toolkit auth config as present before the connect link flow.
-
-## Troubleshooting
-
-`managed_composio_entitlement_required`:
-
-Log in with a paid AgentKit Cloud account that has `managed_composio`.
-
-`managed_composio_auth_config_missing`:
-
-The AgentKit Cloud account is entitled, but the requested toolkit is not configured in AgentKit Cloud yet. Report the exact error code and toolkit slug to the AgentKit owner.
-
-`managed_composio_not_configured`:
-
-Managed Composio is not available for this AgentKit Cloud environment. Use BYO `defineTool` wrappers for now or ask the owner to enable managed Composio for the account.
-
-`integration_toolkit_required`:
-
-The deploy has multiple configured toolkits. Re-run connect with `--toolkit <slug>`.