@cursor/bdk 0.2.3 → 0.2.5

package/dist/docs/llms-full.txt

@@ -13,9 +13,6 @@ a coding agent can create the project, exercise its tools, run a real
 turn, and inspect the result. You approve the plan and side effects
 while the coding agent owns the implementation loop.
 
-The `@cursor/bdk` imports and `bdk` commands on this page are docs-ahead
-until publication; see [BDK package availability](/docs/index.md#bdk-package-availability).
-
 This page covers a coding agent working inside a checkout. To let a
 running agent propose changes to its own source, use the separate
 [self-improvement extension](/docs/guides/improve.md).
@@ -153,10 +150,6 @@ Cursor-managed hosting builds the selected Git ref and operates the
 runtime; self-hosting gives you control of the network, process, and
 filesystem.
 
-The `@cursor/bdk` imports and `bdk` commands in these examples are
-docs-ahead until publication; see
-[BDK package availability](/docs/index.md#bdk-package-availability).
-
 ## Choose managed hosting or self-hosting
 
 | Option | Use it when | You manage |
@@ -173,9 +166,6 @@ API.
 Commit and push the exact ref you want to run, then sign in, validate,
 and deploy. The preferred CLI is `bdk`.
 
-> **Docs ahead:** `@cursor/bdk` is not on npm yet. This block shows future
-> CLI syntax and will not run until the package publishes.
-
 ```text
 cd my-agent
 bdk login
@@ -184,7 +174,7 @@ bdk validate
 bdk deploy
 ```
 
-The deploy command waits until the engine is running and prints the stable
+The deploy command waits until the runtime is running and prints the stable
 deployment URL.
 
 `deploy` reads from Git; it does not upload your working tree. Inside a
@@ -205,7 +195,10 @@ project.
 
 ## Add egress and secrets
 
-Declare the external hosts and secret names the agent needs. After the
+Declare the external hosts and secret names the agent needs. Mounted
+extensions add the ones they declare, so list only what your own code
+calls; `bdk info --dir .` shows the combined list and what each mount
+adds. After the
 deployment exists, set each value at the hidden prompt and follow the
 CLI or dashboard instruction to redeploy.
 
@@ -324,7 +317,7 @@ multi-agent deployment, stop, and delete behavior.
 
 Managed hosting persists framework-owned session, KV, and file state
 across normal runtime replacements. Files written elsewhere on the
-engine's local filesystem are disposable; use `ctx.host.kv` or
+runtime's local filesystem are disposable; use `ctx.host.kv` or
 `ctx.host.files` for durable application state.
 
 Parked approvals and in-memory reminder handlers do not survive a
@@ -402,9 +395,6 @@ not to discover what the prompt should do.
 Evals run real model turns and real tools. Guard external writes before
 running a suite against an agent that can post, merge, or deploy.
 
-The `@cursor/bdk` imports and `bdk` commands on this page are docs-ahead
-until publication; see [BDK package availability](/docs/index.md#bdk-package-availability).
-
 ## Protect a tool decision
 
 This smoke case asks for a PR verdict, requires the read-only inspection
@@ -661,9 +651,6 @@ help. The specialist keeps its own instructions, tools, and session,
 while the caller decides when to delegate and returns the answer to the
 user. Co-host both projects under one `bdk` process.
 
-The `@cursor/bdk` imports and `bdk` commands on this page are docs-ahead
-until publication; see [BDK package availability](/docs/index.md#bdk-package-availability).
-
 ## Delegate a question to a specialist
 
 Ask the concierge about the weather and it hands the question to the
@@ -818,9 +805,6 @@ current pull-request or commit state, and writes the result back to
 Bitbucket. `bitbucketChannel()` gives the same hooks and normalized
 payloads on Bitbucket Cloud and Data Center.
 
-The `@cursor/bdk` imports and `bdk` commands on this page are docs-ahead
-until publication; see [BDK package availability](/docs/index.md#bdk-package-availability).
-
 ## Review a pull request
 
 Creating a pull request, or pushing new commits to a Data Center pull
@@ -1114,10 +1098,6 @@ same branch.
 
 ## Mount it
 
-The extension will ship with `@cursor/bdk` when the package publishes.
-This import is docs-ahead; see
-[BDK package availability](/docs/index.md#bdk-package-availability).
-
 ```ts
 // bot/extensions/cloud.ts
 import cursorCloudAgents from "@cursor/bdk/extensions/cursor-cloud-agents";
@@ -1210,9 +1190,6 @@ path.
 configuration and prints a checklist for everything that still needs
 your judgment.
 
-The `@cursor/bdk` imports and `bdk` commands on this page are docs-ahead
-until publication; see [BDK package availability](/docs/index.md#bdk-package-availability).
-
 ## Convert and run locally
 
 The command creates a project named after the Automation, installs its
@@ -1297,9 +1274,9 @@ reply experience and app setup.
 
 The generated GitHub channel keeps mechanical filters such as PR
 actions, branches, issue actions, repositories, and simple user
-allowlists. Conditions that depended on backend-only context stay
+allowlists. Conditions that depend on dashboard-only context stay
 fail-closed, so the corresponding hook returns `null` until you replace
-it.
+them.
 
 For example, a converted CI trigger can wake only when the suite fails:
 
@@ -1394,9 +1371,6 @@ latest PR and CI state, then write back reviews, comments, checks, or
 pushes. Pull events from Cursor, so you don't expose a public webhook
 URL.
 
-The `@cursor/bdk` imports and `bdk` commands on this page are docs-ahead
-until publication; see [BDK package availability](/docs/index.md#bdk-package-availability).
-
 Connect GitHub in Cursor for the repos you care about (Settings or
 [cursor.com/dashboard](https://cursor.com/dashboard)). Sign the host in
 with `bdk login`. `cursorAccount` reuses that connection for
@@ -1623,7 +1597,7 @@ Every wake for the same repo and PR number resumes the same session. The
 channel keys turns as `github-pr:acme/checkout#42`. Opens, comments, and
 CI results share that conversation.
 
-## Call GitHub from determistic code via `ctx`
+## Call GitHub from deterministic code via `ctx`
 
 `cursorAccount` puts one credential on both surfaces:
 
@@ -1759,9 +1733,6 @@ project or merge-request state, and writes the result back to GitLab.
 `gitlabChannel()` supports the same hooks on GitLab.com and self-managed
 GitLab.
 
-The `@cursor/bdk` imports and `bdk` commands on this page are docs-ahead
-until publication; see [BDK package availability](/docs/index.md#bdk-package-availability).
-
 ## Review a merge request
 
 Opening, reopening, or pushing commits to a merge request starts a
@@ -2058,9 +2029,6 @@ the Grok Bot agents on its serve host's Cursor account. The bot keeps
 its existing conversation, memory, and tools, while your agent carries
 the delivered reply back into the current conversation.
 
-The `@cursor/bdk` imports and `bdk` commands on this page are docs-ahead
-until publication; see [BDK package availability](/docs/index.md#bdk-package-availability).
-
 Use this extension on the local runtime. It consults another Grok Bot;
 it does not move this agent onto a Grok Bot runtime.
 
@@ -2110,7 +2078,7 @@ The message must include who is asking, the relevant facts, and the
 shape of the answer. The Grok Bot does not see the current BDK
 conversation.
 
-> Netto is deciding whether to move Saturday's picnic. The forecast is
+> Avery is deciding whether to move Saturday's picnic. The forecast is
 > 70% rain from 1-4pm. Recommend keep or move, give one reason, and name
 > the best alternate time.
 
@@ -2205,9 +2173,6 @@ as updating metrics or sending alerts. They never change the turn, prompt, or
 reply. Author them under `bot/hooks/` with `defineHook` from
 `@cursor/bdk/hooks`.
 
-The `@cursor/bdk` imports on this page are docs-ahead until publication;
-see [BDK package availability](/docs/index.md#bdk-package-availability).
-
 ## Meter token usage
 
 With [OpenTelemetry](/docs/guides/opentelemetry.md) configured, this hook adds a live
@@ -2324,9 +2289,6 @@ work" into a source change. The agent prepares a brief, a Cursor cloud
 agent edits a checkout and opens a pull request, and the running agent
 reports the verified PR for human review.
 
-The `@cursor/bdk` imports and `bdk` commands on this page are docs-ahead
-until publication; see [BDK package availability](/docs/index.md#bdk-package-availability).
-
 Durable behavior does not change until that source is merged and
 deployed.
 
@@ -2464,9 +2426,6 @@ risk, choose a reviewer, or decide whether a merge needs a documentation
 follow-up. Jev returns a choice, score, or probability; your TypeScript
 decides what happens next.
 
-The `@cursor/bdk` imports on this page are docs-ahead until publication;
-see [BDK package availability](/docs/index.md#bdk-package-availability).
-
 Set `TYPESAFE_API_KEY`. The default model is `jev-latest`.
 
 ```ts
@@ -2476,6 +2435,13 @@ import jev from "@cursor/bdk/extensions/jev";
 export default jev();
 ```
 
+On Cursor-managed hosting, this mount adds `api.typesafe.ai` to the
+deployment's egress allowlist and `TYPESAFE_API_KEY` to the secrets it
+expects, so `bdk deploy` warns until you set the key. A project that
+imports `decide` or `evaluate` without mounting the extension has to
+list `api.typesafe.ai` in `hosting.egressDomains` itself; see
+[Add egress and secrets](/docs/deployment.md#add-egress-and-secrets).
+
 ## Start only the review turns you need
 
 Call Jev from a channel hook before a model turn starts. When a pull
@@ -2762,9 +2728,6 @@ without putting tokens in the agent's source or workspace. Use it when
 the server speaks OAuth and its credentials should belong to the serve
 host instead of a person's Cursor account.
 
-The `@cursor/bdk` imports and `bdk` commands on this page are docs-ahead
-until publication; see [BDK package availability](/docs/index.md#bdk-package-availability).
-
 ## Use a private MCP tool locally
 
 Declare the remote server, authorize it once in the browser, and start
@@ -2881,7 +2844,7 @@ bdk deploy
 ```
 
 `--store` writes deployment secrets; it does not restart the current
-engine. Follow the CLI or dashboard prompt to redeploy, then exercise
+process. Follow the CLI or dashboard prompt to redeploy, then exercise
 the hosted agent.
 
 These credentials belong to the deployment, not to the person who
@@ -2932,16 +2895,13 @@ cost metrics from the serve process.
 Export is opt-in. Nothing leaves the process until you configure a
 destination.
 
-The `bdk` commands on this page are docs-ahead until `@cursor/bdk` is
-published; see [BDK package availability](/docs/index.md#bdk-package-availability).
-
 ## Connect an OTLP collector
 
 Set the collector endpoint, start the agent, and send it a message. You
 should see an `agent_sdk.http` request span and an `agent_sdk.turn`
 trace, with any tool or subagent work nested under the turn.
 
-```text
+```bash
 export OTEL_EXPORTER_OTLP_ENDPOINT=https://otel.example.com
 export OTEL_EXPORTER_OTLP_HEADERS="Authorization=Bearer $OTEL_TOKEN"
 export OTEL_SERVICE_NAME=incident-agent
@@ -2954,7 +2914,9 @@ The default protocol is OTLP/HTTP protobuf. If you already call
 code:
 
 ```ts
-await serve(dir, {
+import { serve } from "@cursor/bdk";
+
+await serve(".", {
   otel: {
     serviceName: "incident-agent",
     exporters: [
@@ -3087,9 +3049,6 @@ in a channel it watches. From there, it keeps the conversation in one
 thread and can reply all at once, stream the answer live, or decide for
 itself when to post updates.
 
-The `@cursor/bdk` imports and `bdk` commands on this page are docs-ahead
-until publication; see [BDK package availability](/docs/index.md#bdk-package-availability).
-
 Run `bdk slack create --dir .`, then `bdk slack doctor`.
 
 ## Answer a mention or DM
@@ -3124,7 +3083,7 @@ export default slackChannel({
       reasoning: true,
       // Tool names as they start ("Running grep, glob...").
       tools: true,
-      idle: ["Checking the monorepo...", "Poking Datadog..."],
+      idle: ["Checking the request...", "Reviewing recent activity..."],
     },
   },
 });
@@ -3185,15 +3144,12 @@ This example watches `#triage-alerts`, so any substantial top-level
 message starts a thread even when nobody mentions the bot. The length
 guard filters out short posts before they can start a turn.
 
-Mentions are global — the bot answers an @mention in any channel it has
-joined — but listening without a mention names its channels: `allow`
-must include at least one channel id (`C…`/`G…`) and at most 10 distinct
-ids. `#name` entries may accompany the ids for readability. A lone `"*"`
-watches every channel the bot is in, thread replies only
-(`posts: "replies"`). Mixing `"*"` with ids is an error. `"*"` is the
-guest watcher: it is not a hosting subscription. A thread reply on
-Cursor-managed hosting is delivered when a mention already opened that
-thread, and a top-level post does not match.
+Mentions work in any channel the bot has joined. Listening without a
+mention requires an explicit allowlist with at least one channel ID
+starting with `C` or `G` and at most 10 distinct IDs. You can add
+`#name` entries for readability. A lone `"*"` watches replies in every
+joined channel (`posts: "replies"`), but it does not wake on top-level
+posts. Do not mix `"*"` with channel IDs.
 
 ```ts
 export default slackChannel({
@@ -3217,15 +3173,11 @@ export default slackChannel({
 When you create the app, pass `--channel-posts` and invite the bot to
 every channel in the allowlist.
 
-On Cursor-managed hosting the id entries also define the delivery set:
-each becomes a channel-scoped subscription, and a channel post outside
-the allowlist is dropped at ingress before any compute wakes (replies in
-threads the agent is already part of still arrive). The same watch runs
-at admission for each delivered event. `debounceMs` is ignored there:
-the control plane answers every delivery immediately, and edits arrive
-as separate deliveries that are dropped at the edge. Channel ids match
-without any Slack call; `#name` entries are resolved once per pod with
-the bot token and need the `channels:read` scope.
+On Cursor-managed hosting, the channel IDs in `allow` define which
+top-level posts can wake the agent. Replies in threads the agent has
+already joined still arrive. `debounceMs` applies only when you
+self-host. Add the `channels:read` scope when you include `#name`
+labels.
 
 ## Control who can message
 
@@ -3307,7 +3259,7 @@ Use the IDs on the hook `ctx` when handling an event, and
 
 ## Connect
 
-```text
+```bash
 bdk login
 bdk slack create --dir .
 bdk slack doctor --prefix TRIAGE
@@ -3333,7 +3285,7 @@ and tokens.
 Run `doctor` first to catch missing credentials, then start the agent
 and send it the same mention or DM a teammate would.
 
-```text
+```bash
 bdk slack doctor --prefix TRIAGE
 bdk serve --dir . --dev
 ```
@@ -3370,9 +3322,6 @@ conversation, then sends the result back to the system that started it.
 Use one when the built-in [HTTP API](/docs/reference/http-api.md) does not
 match the provider's payload, conversation key, or reply path.
 
-The `@cursor/bdk` imports on this page are docs-ahead until publication;
-see [BDK package availability](/docs/index.md#bdk-package-availability).
-
 Author `bot/channels/<id>.ts`. Its routes mount under
 `/<slug>/v1/channels/<id>`.
 
@@ -3614,9 +3563,6 @@ crossing the freeze line.
 The companion [`hillclimb` skill](https://github.com/cursor/cursor/blob/main/packages/agent-serve/skills/hillclimb/SKILL.md) can run
 this loop with you.
 
-The `bdk` commands on this page are docs-ahead until `@cursor/bdk` is
-published; see [BDK package availability](/docs/index.md#bdk-package-availability).
-
 ## Correct a wrong tool choice
 
 Suppose a PR reviewer calls `approve_pr` before `inspect_pr`. Pin one PR
@@ -3748,9 +3694,9 @@ Source: /docs/index.md
 
 # Grok Bot Development Kit (BDK)
 
-The Grok Bot Development Kit (BDK) is how Cursor builds agents. It's the
-open-source version of the engine behind Bugbot, Security Review, and
-Approval Bot.
+The Grok Bot Development Kit (BDK) lets you define, test, and deploy agents
+as code. It uses the Cursor SDK harness that powers Bugbot, Security Review,
+and Approval Bot.
 
 A BDK project is a folder of Markdown and TypeScript. Combine deterministic
 code with model judgment, then make the bot or agent available in source
@@ -3790,17 +3736,9 @@ sandboxing on Cursor infrastructure or on your own host.
 
 ![BDK architecture: you bring the agent as code, and the platform provides triggers, runtime, integrations, and operations](/docs/architecture.svg)
 
-## BDK package availability
-
-BDK uses the `@cursor/bdk` package and `bdk` binary. The package isn't on npm
-yet, so its install commands won't run until publication.
-
 ## Get started
 
-The preferred BDK workflow starts with `bdk init` and `bdk dev`.
-
-> **Docs ahead:** `@cursor/bdk` is not on npm yet. The package will install
-> the `bdk` binary; this block will not run until it publishes.
+Install `@cursor/bdk`, then start with `bdk init` and `bdk dev`.
 
 ```text
 npm install --global @cursor/bdk
@@ -3825,7 +3763,7 @@ my-bot/
 │   ├── mcp-connections/
 │   │   └── linear.ts          # tools from an MCP server
 │   ├── host-connections/
-│   │   └── internal.ts        # host-only MCP tools
+│   │   └── inventory.ts       # host-only MCP tools
 │   ├── subagents/
 │   │   └── verifier/
 │   │       ├── agent.ts
@@ -3845,10 +3783,11 @@ Describe your bot or agent in Cursor, or edit the files yourself.
 - [Build your first PR reviewer](/docs/quickstart.md): a working GitHub
   reviewer, one step at a time.
 
-- Start from a template with the docs-ahead `bdk init --template` command:
+- Start from a template:
+  [Grok Bot agents](/docs/templates/grokbot-agents.md),
   [security reviewer](/docs/templates/security-reviewer.md),
-  [thermo reviewer](/docs/templates/thermo-review.md),
-  [thermo quality reviewer](/docs/templates/thermo-quality-review.md),
+  [Thermo review](/docs/templates/thermo-review.md),
+  [Thermo quality review](/docs/templates/thermo-quality-review.md),
   [owners-policy approver](/docs/templates/agentic-owners.md),
   [issue triager](/docs/templates/triage.md).
 
@@ -3875,15 +3814,13 @@ review.
 
 - Node 22.13 or newer.
 
-- The docs-ahead BDK package and CLI. `@cursor/bdk` is not on npm yet,
-  so these commands will not run until publication. See
-  [BDK package availability](/docs/index.md#bdk-package-availability).
+- The `@cursor/bdk` package:
 
 ```text
 npm install -g @cursor/bdk
 ```
 
-- A Cursor credential for model turns. After publication, sign in once:
+- A Cursor credential for model turns. Sign in once:
 
 ```text
 bdk login
@@ -3893,9 +3830,6 @@ bdk login
 
 The preferred BDK workflow uses `bdk init` and `bdk dev`.
 
-> **Docs ahead:** `@cursor/bdk` is not on npm yet. This block shows future
-> CLI syntax and will not run until the package publishes.
-
 ```text
 bdk init ./pr-reviewer
 cd pr-reviewer
@@ -4188,9 +4122,6 @@ Source: /docs/reference/agent-config.md
 the agent and its local harness defaults.
 Everything is optional on the root agent.
 
-The `@cursor/bdk` imports and `bdk` commands on this page are docs-ahead
-until publication; see [BDK package availability](/docs/index.md#bdk-package-availability).
-
 ```ts
 import { defineAgent } from "@cursor/bdk";
 
@@ -4214,15 +4145,15 @@ export default defineAgent({
 | `description` | string | What the agent is for. Required on subagents; the parent model reads it to decide when to delegate. Documentation-only on the root. |
 | `instructions` | string | Inline instructions. Prefer `instructions.md`; this exists for subagents and generated configs. |
 | `local` | `{ cwd?, workspaceDir?, sandbox? }` | Local harness defaults. See [Local options](#local-options). |
-| `hosting` | `{ egressDomains?, secretNames? }` | Managed-hosting declarations read by `bdk deploy`: the pod's egress allowlist and the secret names the agent expects. Ignored by local serving. |
-| `concurrency` | `{ maxRunningTurns? }` | Engine-wide turn admission limit. See [Concurrency](#concurrency). |
+| `hosting` | `{ egressDomains?, secretNames? }` | Managed-hosting declarations read by `bdk deploy`: the deployment's egress allowlist and the secret names the agent expects. Mounted [extensions](/docs/reference/extensions.md#build-an-extension) add their own. Ignored by local serving. |
+| `concurrency` | `{ maxRunningTurns? }` | Agent-wide concurrent turn limit. See [Concurrency](#concurrency). |
 | `builtinTools` | `{ reminders? }` | Framework-provided model-facing tools, opted in per capability. See [Built-in tools](#built-in-tools). |
 | `tools` | `ToolName[]` | Allowlist of built-in harness tools offered to the model. Unset = the model's full standard toolset. See [Harness tools](#harness-tools). |
 
 ## Model
 
 `model` is a Cursor model id string, or `{ id, params }`. Effort and
-speed are params, not id suffixes. The SDK rejects suffix-style ids
+speed are params, not id suffixes. BDK rejects suffix-style ids
 like `grok-4.5-fast`:
 
 ```ts
@@ -4295,7 +4226,7 @@ servers, point `local.cwd` outside the checkout. See
 [Local cwd](#local-cwd). `local.sandbox` makes MCP tool calls fail
 closed.
 
-Use the SDK's public tool names, including `"shell"`, `"read"`,
+Use the Cursor SDK's public tool names, including `"shell"`, `"read"`,
 `"edit"`, `"grep"`, `"glob"`, `"ls"`, and `"task"`. Unknown names
 fail the turn with a `ConfigurationError`.
 
@@ -4382,9 +4313,6 @@ or decision records. An artifact kind defines the data it accepts, and
 the artifacts API tags or updates records by key. Records persist across
 sessions and can be listed, streamed, or downloaded.
 
-The `@cursor/bdk` imports on this page are docs-ahead until publication;
-see [BDK package availability](/docs/index.md#bdk-package-availability).
-
 ## Artifact kinds
 
 Author `bot/artifacts.ts` with `defineArtifacts` from
@@ -4503,9 +4431,6 @@ A channel connects an external surface to agent sessions. A file at
 under `/v1/channels/<id>`. The built-in HTTP session channel is always
 available alongside any custom or prebuilt channels.
 
-The `@cursor/bdk` imports on this page are docs-ahead until publication;
-see [BDK package availability](/docs/index.md#bdk-package-availability).
-
 ## Built-in HTTP channel
 
 The built-in channel serves the session, approval, tool, discovery, and
@@ -4667,15 +4592,13 @@ author their own chain, and `--allow-anonymous` swaps it for
 
 ## Prebuilt channels
 
-| Import | Factory | Surface |
+| Import | Function | Surface |
 | --- | --- | --- |
 | `@cursor/bdk/channels/slack` | `slackChannel()` | Slack messages, threads, streaming replies, and approvals. See [Slack](/docs/guides/slack.md) |
 | `@cursor/bdk/channels/github` | `githubChannel()` | GitHub and GitHub Enterprise webhooks. See [GitHub](/docs/guides/github.md) |
 | `@cursor/bdk/channels/gitlab` | `gitlabChannel()` | GitLab.com and self-managed GitLab hooks. See [GitLab](/docs/guides/gitlab.md) |
 | `@cursor/bdk/channels/bitbucket` | `bitbucketChannel()` | Bitbucket Cloud and Data Center hooks. See [Bitbucket](/docs/guides/bitbucket.md) |
 | `@cursor/bdk/channels/deployments` | `deploymentsChannel()` | Deployment events filtered by source, environment, or event name |
-| `@cursor/bdk/channels/change-monitors` | `changeMonitorsChannel()` | Change Monitor `checkpoint.created` events |
-| `@cursor/bdk/channels/issues` | `issuesChannel()` | Factory `issue.created` events |
 
 For other platforms like Discord or Teams, use the authored
 `defineChannel` route form.
@@ -4704,20 +4627,17 @@ Source: /docs/reference/cli.md
 The Grok Bot Development Kit (BDK) uses the `@cursor/bdk` package and `bdk`
 CLI.
 
-> **Docs ahead:** `@cursor/bdk` is not on npm yet. This command will work
-> after publication.
-
 ```text
 bdk <command>
 ```
 
-The command catalog below documents the `bdk` binary that will ship with
-`@cursor/bdk`. Run the published binary with Node 22.13 or newer; Bun is not
+The command catalog below documents the `bdk` binary from
+`@cursor/bdk`. Run it with Node 22.13 or newer; Bun is not
 supported. Commands exit nonzero when validation or a synchronous request fails;
 asynchronous commands can exit `0` once work is accepted. Project paths use the
 [BDK project layout](/docs/reference/project-layout.md).
 
-After publication, install `@cursor/bdk` to obtain the binary. `bdk help`
+Install `@cursor/bdk` to obtain the binary. `bdk help`
 prints top-level help; the Slack, GitHub, GitLab, and Bitbucket command packs
 provide their own `help` subcommands.
 
@@ -5137,7 +5057,7 @@ installs dependencies, and tries to put `bdk` on `PATH`.
 
 | Option | Contract |
 | --- | --- |
-| `--template <name>` | Use a bundled template: `agentic-owners`, `agents-md`, `code-wiki`, `demo`, `grokbot-agents`, `security-help`, `security-reviewer`, `thermo-quality-review`, `thermo-review`, `triage-jira`, or `triage-linear`. |
+| `--template <name>` | Use a bundled template: `agentic-owners`, `agents-md`, `code-wiki`, `demo`, `grokbot-agents`, `security-help`, `security-reviewer`, `thermo-quality-review`, `thermo-review`, `triage-jira`, or `triage-linear`. `triage` selects `triage-linear`. |
 | `--var id=value` | Answer a template question without a prompt. Repeat for multiple answers. |
 | `--json` | Skip interactive login and skill prompts, then print `{ ok, directory, template, created, skipped, installed, installError, cliOnPath, cliLinkError, next }`. `ok` reflects dependency installation. |
 
@@ -5176,7 +5096,7 @@ The command replaces the installed BDK skills with the package copy and
 removes stale bundled skills. `--print` previews the change. `--json` prints
 `{ ok, dryRun, directory, firstInstall, skills, removed }`.
 
-When `@cursor/bdk` publishes, package installation will perform this copy.
+Package installation performs this copy.
 Run `bdk install-skills` when you need to refresh it.
 
 ### Inspect a project {#info}
@@ -5296,8 +5216,7 @@ bdk deployments [--team <id>] [--json]
 ```
 
 Text output shows slug, status, generation, kind, and update time. `--json`
-prints `{ deployments }` and may also include `applications`. An empty list
-succeeds.
+prints `{ deployments }`. An empty list succeeds.
 
 ### Inspect a deployment {#deployment}
 
@@ -5326,10 +5245,7 @@ bdk cancel-runs <slug> [--team <id>] [--json]
 ```
 
 The command requests cancellation for a deployment's active runs and reminder
-wakes. For a multi-tenant
-application, this cancels every install; use `stop --cancel-runs` for
-install-local cancellation. It exits nonzero if any cancellation request fails
-to start.
+wakes. It exits nonzero if any cancellation request fails to start.
 
 ### Replace event repositories {#event-repos}
 
@@ -5623,9 +5539,6 @@ Put a server in `bot/host-connections/` when only host tools should
 call it. Host connections use the same `defineConnection` shape and
 support `bdk mcp oauth`; the model and playground don't see them.
 
-The `@cursor/bdk` imports and `bdk` commands on this page are docs-ahead
-until publication; see [BDK package availability](/docs/index.md#bdk-package-availability).
-
 ## Remote MCP server
 
 Point an MCP connection at a remote server with a URL.
@@ -5709,16 +5622,16 @@ export default defineConnection({
 The callback is evaluated on every turn, including reminder
 fires and post-restart follow-ups, so the identity always comes from the
 session itself, never from state parked in memory. The model never sees a
-tenant parameter and can never choose the tenant. A callback that throws
-fails the turn: a turn never silently runs without the connection's
-identity. `host.mcp` calls from server tools keep the static headers only.
-You can't combine `auth` with `oauth: true`; the host OAuth provider owns
-the Authorization header.
+downstream account parameter and cannot choose the account. A callback
+that throws fails the turn: a turn never silently runs without the
+connection's identity. `host.mcp` calls from server tools keep the static
+headers only. You can't combine `auth` with `oauth: true`; the host OAuth
+provider owns the Authorization header.
 
 Derive the identity from durable session facts: `session.auth`,
 `session.id`, or your channel's own session state. Do not key it off
 `session.continuationKey`. The HTTP channel rotates that key after every
-accepted follow-up, so a tenant mapping keyed on it breaks
+accepted follow-up, so an account mapping keyed on it breaks
 mid-conversation.
 
 `auth` works attached or advertised. Advertise the auth connection
@@ -5734,7 +5647,7 @@ characters and add numeric suffixes to avoid collisions.
 ```ts
 export default defineConnection({
   url: "https://api.cursor.com/v1/mcp/plugins",
-  auth: async (session) => ({ headers: await tenantHeaders(session) }),
+  auth: async (session) => ({ headers: await headersForSession(session) }),
   advertiseTools: true,
 });
 ```
@@ -5921,9 +5834,6 @@ tools, events, and output meet a contract. Files under the project-root
 discovers their IDs, executes them, and reports every assertion. See the
 [Evals guide](/docs/evals.md) for the regression workflow.
 
-The `@cursor/bdk` imports and `bdk` commands on this page are docs-ahead
-until publication; see [BDK package availability](/docs/index.md#bdk-package-availability).
-
 ## Eval discovery and case IDs
 
 Eval files live under the project-root `evals/` directory and end in
@@ -6212,9 +6122,6 @@ schedules, subagents, artifacts, and workspace seeds. One mount file
 adds them under a namespace without copying their source into your
 project.
 
-The `@cursor/bdk` imports and `bdk` commands on this page are docs-ahead
-until publication; see [BDK package availability](/docs/index.md#bdk-package-availability).
-
 Extensions and Cursor plugins execute as trusted host code. A namespace
 prevents name collisions; it does not sandbox the package or limit its
 side effects. Review the package before mounting it.
@@ -6255,6 +6162,10 @@ bdk info --dir . --json
 hooks, channels, schedules, subagents, and artifact kinds. The same
 data appears under `extensions` in `GET /v1/info`.
 
+A mount can also widen what a hosted deployment reaches. `info` shows the
+egress hosts and secret names each mount adds, and `bdk deploy` names
+every extension that adds egress before it deploys.
+
 Names inside the extension stay short. A tool authored as
 `tools/failed_jobs.ts` appears to the mounting agent as
 `<namespace>__failed_jobs`. The `__` separator is reserved, so root
@@ -6305,8 +6216,8 @@ not provide.
 ## Mount a Cursor plugin
 
 `cursorPlugin()` adapts a vendored Cursor or Claude plugin into the same
-namespace model. Skills, commands, agents, and MCP servers become Agent
-SDK skills, subagents, and connections.
+namespace model. Skills, commands, agents, and MCP servers become BDK
+skills, subagents, and connections.
 
 ```ts
 // bot/extensions/notion.ts
@@ -6375,6 +6286,7 @@ export default defineExtension({
     token: z.string(),
     logTailLines: z.number().int().positive().default(200),
   }),
+  hosting: () => ({ egressDomains: ["api.buildkite.com"] }),
 });
 ```
 
@@ -6383,6 +6295,14 @@ Modules inside the package import this definition and read
 applied. Publish the built entry point with its slot directories and
 prose assets beside it.
 
+`hosting` names the hosts the package calls and the secrets it reads
+from the environment. It receives the validated settings, and the
+mounting agent's `hosting.egressDomains` and `hosting.secretNames` gain
+whatever it returns, so a hosted deploy reaches Buildkite without the
+consumer listing `api.buildkite.com`. Leave out secrets that arrive
+through settings, such as `token` here; the consumer decides where that
+value comes from.
+
 The [Project layout](/docs/reference/project-layout.md) owns each contribution's
 authoring contract. Keep extension instructions and tool descriptions
 namespace-neutral because the consumer chooses the final prefix.
@@ -6410,9 +6330,6 @@ transcript copy, or derived state. Hooks run in the serving process for
 every session of the agent. They cannot change the turn, the prompt, or
 the reply; a handler that throws is logged and skipped.
 
-The `@cursor/bdk` imports on this page are docs-ahead until publication;
-see [BDK package availability](/docs/index.md#bdk-package-availability).
-
 Treat the event as read-only. Later subscribers see the same object.
 That makes hooks safe to add to a production agent, and the wrong
 surface for anything that must run before the model or must fail a
@@ -6735,7 +6652,7 @@ These read-only routes describe the running agent.
 | Route | Contract |
 | --- | --- |
 | `GET /v1/info` | Return the discovered model, tools, skills, connections, subagents, channels, schedules, hooks, and diagnostics |
-| `GET /v1/tools` | Return live server tools and advertised MCP tools as `{ name, title?, source? }`; bind tenant-scoped listings with `session` or `continuationToken` |
+| `GET /v1/tools` | Return live server tools and advertised MCP tools as `{ name, title?, source? }`; bind session-specific listings with `session` or `continuationToken` |
 | `GET /v1/tools/:name` | Return one tool's description, execution mode, approval and effect rules, schemas, and source |
 | `GET /v1/health` | Return per-agent liveness; no auth |
 | `GET /v1/logs?after=N` | Return recent server logs and the next polling cursor |
@@ -6840,9 +6757,6 @@ Agent instructions form the always-on system prompt and reach the model
 on every turn. A root agent requires them; a subagent may inline
 `instructions` in `agent.ts` instead.
 
-The `@cursor/bdk` imports on this page are docs-ahead until publication;
-see [BDK package availability](/docs/index.md#bdk-package-availability).
-
 ## Authoring forms
 
 | Form | Use it when |
@@ -6909,9 +6823,6 @@ Source: /docs/reference/playground.md
 mode). In multi-agent mode, each agent has its own playground, and `/`
 lists them all.
 
-The `bdk` commands on this page are docs-ahead until `@cursor/bdk` is
-published; see [BDK package availability](/docs/index.md#bdk-package-availability).
-
 ## Playground surfaces
 
 | Surface | What you can do |
@@ -6965,7 +6876,7 @@ For the capabilities below, identity comes from the path.
 | --- | --- |
 | `tools/approve_pr.ts` | tool `approve_pr` |
 | `mcp-connections/linear.ts` | MCP connection `linear` (model + host) |
-| `host-connections/anytool.ts` | Host MCP connection `anytool` (host + `mcp oauth` only) |
+| `host-connections/inventory.ts` | Host MCP connection `inventory` (host + `mcp oauth` only) |
 | `skills/pr-review.md` | skill `pr-review` |
 | `subagents/reviewer/` | subagent `reviewer` |
 | `extensions/ci.ts` | extension mount `ci`; its contributions become `ci__<name>` |
@@ -6994,7 +6905,7 @@ my-agent/
 │   ├── mcp-connections/
 │   │   └── linear.ts          # tools from external MCP servers
 │   ├── host-connections/
-│   │   └── anytool.ts         # privileged MCP, host tools only
+│   │   └── inventory.ts       # host-only MCP tools
 │   ├── subagents/
 │   │   └── reviewer/
 │   │       ├── agent.ts
@@ -7081,9 +6992,6 @@ import { prompt } from "@cursor/bdk";
 // or: import { prompt } from "@cursor/bdk/prompt";
 ```
 
-The `@cursor/bdk` imports on this page are docs-ahead until publication;
-see [BDK package availability](/docs/index.md#bdk-package-availability).
-
 ## Dedented strings
 
 `prompt` returns one string. It removes the common leading whitespace
@@ -7132,9 +7040,6 @@ reminder is a runtime wake bound to one conversation: "re-check this
 PR's CI in two hours." Schedules live in the filesystem; reminders are
 created by running code.
 
-The `@cursor/bdk` imports and `bdk` commands on this page are docs-ahead
-until publication; see [BDK package availability](/docs/index.md#bdk-package-availability).
-
 ## Schedules
 
 Cron expressions are standard 5-field, evaluated in UTC with minute
@@ -7307,9 +7212,6 @@ token, inspect it with a session ID, and follow progress on the NDJSON
 stream. Chat sessions wait for follow-ups; task sessions run once and
 stop.
 
-The `bdk` commands on this page are docs-ahead until `@cursor/bdk` is
-published; see [BDK package availability](/docs/index.md#bdk-package-availability).
-
 ## Session contents
 
 Each session combines:
@@ -7473,9 +7375,6 @@ loads the full content only when the task calls for it. Skills are how
 you give an agent a multi-step workflow without carrying it in the
 always-on [instructions](/docs/reference/instructions.md).
 
-The `@cursor/bdk` imports and `bdk` commands on this page are docs-ahead
-until publication; see [BDK package availability](/docs/index.md#bdk-package-availability).
-
 ## Authoring forms
 
 Skills support three authoring forms.
@@ -7553,9 +7452,6 @@ mid-turn. Each one lives under `bot/subagents/<id>/` with a required
 for a custom prompt. The parent model delegates through the `task` tool,
 and the stream records `subagent.called` and `subagent.completed`.
 
-The `@cursor/bdk` imports on this page are docs-ahead until publication;
-see [BDK package availability](/docs/index.md#bdk-package-availability).
-
 ```text
 bot/subagents/researcher/
 ├── agent.ts            # description (required), model (optional)
@@ -7621,14 +7517,10 @@ execution flavors: server tools run on the serving host, and
 agent tools run as scripts where the agent runs. Every server tool can
 also be called directly, with no model turn.
 
-The `@cursor/bdk` imports and `bdk` commands on this page are docs-ahead
-until publication; see [BDK package availability](/docs/index.md#bdk-package-availability).
-
 ## Define a server tool
 
 By default, `execute` runs in-process on the serving host with full
-access to `process.env` and your `bot/lib/` code. Turns call server
-tools as SDK custom tools.
+access to `process.env` and your `bot/lib/` code.
 
 ```ts
 // bot/tools/inspect_pr.ts
@@ -7950,9 +7842,6 @@ what your policy allows. Ownership rules live in
 the closest policy to a changed file wins, and policies are always read
 from the PR's base ref so a PR cannot exempt itself.
 
-The `@cursor/bdk` imports and `bdk` commands on this page are docs-ahead
-until publication; see [BDK package availability](/docs/index.md#bdk-package-availability).
-
 ## Scaffold
 
 ```text
@@ -8039,6 +7928,66 @@ sessions skip GitHub writes.
 
 ---
 
+Source: /docs/templates/grokbot-agents.md
+
+# Consult named Grok Bot agents
+
+The `grokbot-agents` template lets a BDK agent consult the Grok Bot
+agents you allow. Your BDK conversation stays active while the named
+agent works, and the delivered reply returns to the same conversation.
+A request for an unlisted name is refused.
+
+## Scaffold
+
+```bash
+bdk init ./grokbot-consultant --template grokbot-agents
+```
+
+`init` asks for the names shown in the Grok Bot app. Pass them directly
+in a script:
+
+```bash
+bdk init ./grokbot-consultant --template grokbot-agents \
+  --var agents="Plan Keeper,Chief of Staff"
+```
+
+## Run
+
+Sign in, validate the scaffold, and start the project:
+
+```bash
+cd grokbot-consultant
+bdk login
+bdk validate
+bdk dev
+```
+
+Open the playground and ask the agent to consult one of the names you
+entered. The delivered reply returns to the same conversation.
+
+## Choose who the agent can consult
+
+Edit `bot/extensions/grokbot.ts` to change the allowlist. The template
+supports descriptions that help the model choose the right specialist
+when several names are available.
+
+When someone asks which agents are available, the template lists them
+without sending a message. A consultation sends one self-contained
+question and reports the reply. Long-running consultations can be
+checked later, and an active turn can be interrupted when the task
+changes.
+
+See [Grok Bot agents](/docs/guides/grokbot-agents.md) for the extension's
+conversation and approval boundaries.
+
+## What to edit
+
+- `bot/extensions/grokbot.ts`: allowed agent names
+- `bot/instructions.md`: when to consult them
+- `evals/grokbot-agents.eval.ts`: list-without-sending smoke case
+
+---
+
 Source: /docs/templates/security-reviewer.md
 
 # Review pull requests for exploitable bugs
@@ -8049,9 +7998,6 @@ RCE. Style nits stay out.
 
 This template is one model turn: read the diff, then post one comment.
 
-The `@cursor/bdk` imports and `bdk` commands on this page are docs-ahead
-until publication; see [BDK package availability](/docs/index.md#bdk-package-availability).
-
 ## Scaffold
 
 ```text
@@ -8134,15 +8080,12 @@ Source: /docs/templates/thermo-quality-review.md
 # Review pull requests for structural code quality
 
 This agent reads a pull request diff and posts one review comment. It
-reports missing abstractions, spaghetti branches, feature logic
-leaking into shared paths, and files pushed past 1,000 lines. Style
-nits and behavior disputes stay out.
+reports missing abstractions, deeply nested control flow, feature logic
+leaking into shared paths, and files pushed past 1,000 lines. Style nits
+and behavior disputes stay out.
 
 This template is one model turn: read the diff, then post one comment.
 
-The `@cursor/bdk` imports and `bdk` commands on this page are docs-ahead
-until publication; see [BDK package availability](/docs/index.md#bdk-package-availability).
-
 ## Scaffold
 
 ```text
@@ -8217,14 +8160,12 @@ Source: /docs/templates/thermo-review.md
 # Review pull requests for bugs and breakage
 
 This agent reads a pull request diff and posts one review comment. It
-reports bugs, breaking side effects, devex breaks, and feature-gate
-leaks in added or modified code. Style nits stay out.
+reports bugs, breaking side effects, developer workflow failures, and
+unintended feature exposure in added or modified code. Style nits stay
+out.
 
 This template is one model turn: read the diff, then post one comment.
 
-The `@cursor/bdk` imports and `bdk` commands on this page are docs-ahead
-until publication; see [BDK package availability](/docs/index.md#bdk-package-availability).
-
 ## Scaffold
 
 ```text
@@ -8305,9 +8246,6 @@ duplicate when titles match.
 File the ticket however you already do. This template starts after the
 ticket exists.
 
-The `@cursor/bdk` imports and `bdk` commands on this page are docs-ahead
-until publication; see [BDK package availability](/docs/index.md#bdk-package-availability).
-
 ## Scaffold
 
 ```text
@@ -8315,6 +8253,8 @@ bdk init ./triage-agent --template triage-linear
 bdk init ./triage-agent --template triage-jira
 ```
 
+`bdk init --template triage` selects `triage-linear`.
+
 Pick the tracker you use. The agent is the same. The overlay is the
 connection.
 
@@ -8407,11 +8347,7 @@ Start with three checks:
    `bdk info --dir . --json`.
 3. Reproduce once, then inspect the serve log or session trace.
 
-The `bdk` commands on this page are docs-ahead until `@cursor/bdk` is
-published; see [BDK package availability](/docs/index.md#bdk-package-availability).
-
-Match the visible symptom below. The `bdk` binary ships with
-`@cursor/bdk` when the package publishes.
+Match the visible symptom below.
 
 ## Serve or the playground will not work
 
@@ -8445,9 +8381,9 @@ Match the visible symptom below. The `bdk` binary ships with
 
 | What you see | What to do |
 | --- | --- |
-| `401` outside localhost | Send the configured bearer token, alias token, or channel credential. Default custom routes admit direct loopback only. |
+| `401` outside local development | Send the configured bearer token, alias token, or channel credential. Default custom routes admit direct loopback only. |
 | `403` on a stream or follow-up | Use the same authenticated principal that created the session. |
-| A localhost route fails through a tunnel or LAN | Protect the shared host with `--bearer-token` or authored channel auth. Use `--allow-anonymous` only behind a proxy that authenticates every caller. |
+| A custom channel route fails through a tunnel or LAN | Protect the shared host with `--bearer-token` or authored channel auth. Use `--allow-anonymous` only behind a proxy that authenticates every caller. |
 | `409` on a follow-up | Refresh the rotating `continuationToken` and confirm the target is a chat session; task sessions do not accept follow-ups. |
 | `409 session_busy` from `call --session` | Wait for the turn, omit `--session`, or mark a read-only tool with `effect: "read"` so it can run concurrently. |
 | A custom route fails schema type-checking | Add the required Zod `querySchema` for `GET`, or `bodySchema` for `POST`, `PUT`, and `PATCH`. See [Channels](/docs/reference/channels.md). |