@cursor/bdk 0.2.4 → 0.2.6

package/docs/reference/channels.md

@@ -10,9 +10,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](/#bdk-package-availability).
-
 ## Built-in HTTP channel
 
 The built-in channel serves the session, approval, tool, discovery, and
@@ -174,15 +171,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](../guides/slack.md) |
 | `@cursor/bdk/channels/github` | `githubChannel()` | GitHub and GitHub Enterprise webhooks. See [GitHub](../guides/github.md) |
 | `@cursor/bdk/channels/gitlab` | `gitlabChannel()` | GitLab.com and self-managed GitLab hooks. See [GitLab](../guides/gitlab.md) |
 | `@cursor/bdk/channels/bitbucket` | `bitbucketChannel()` | Bitbucket Cloud and Data Center hooks. See [Bitbucket](../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.

package/docs/reference/cli.md

@@ -8,20 +8,17 @@ description: "Look up BDK commands, targets, flags, outputs, and exit status."
 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](./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.
 
@@ -441,7 +438,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. |
 
@@ -480,7 +477,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}
@@ -600,8 +597,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}
 
@@ -630,10 +626,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}
 

package/docs/reference/connections.md

@@ -16,9 +16,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](/#bdk-package-availability).
-
 ## Remote MCP server
 
 Point an MCP connection at a remote server with a URL.
@@ -102,16 +99,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
@@ -127,7 +124,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,
 });
 ```

package/docs/reference/evals.md

@@ -11,9 +11,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](../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](/#bdk-package-availability).
-
 ## Eval discovery and case IDs
 
 Eval files live under the project-root `evals/` directory and end in

package/docs/reference/extensions.md

@@ -11,9 +11,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](/#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.
@@ -108,8 +105,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

package/docs/reference/hooks.md

@@ -11,9 +11,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](/#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

package/docs/reference/http-api.md

@@ -140,7 +140,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 |

package/docs/reference/instructions.md

@@ -9,9 +9,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](/#bdk-package-availability).
-
 ## Authoring forms
 
 | Form | Use it when |

package/docs/reference/playground.md

@@ -10,9 +10,6 @@ description: "The built-in web UI: chat with streaming, Try buttons and slash co
 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](/#bdk-package-availability).
-
 ## Playground surfaces
 
 | Surface | What you can do |

package/docs/reference/project-layout.md

@@ -19,7 +19,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>` |
@@ -48,7 +48,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

package/docs/reference/prompt.md

@@ -15,9 +15,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](/#bdk-package-availability).
-
 ## Dedented strings
 
 `prompt` returns one string. It removes the common leading whitespace

package/docs/reference/schedules.md

@@ -11,9 +11,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](/#bdk-package-availability).
-
 ## Schedules
 
 Cron expressions are standard 5-field, evaluated in UTC with minute

package/docs/reference/sessions.md

@@ -11,9 +11,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](/#bdk-package-availability).
-
 ## Session contents
 
 Each session combines:

package/docs/reference/skills.md

@@ -11,9 +11,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](./instructions.md).
 
-The `@cursor/bdk` imports and `bdk` commands on this page are docs-ahead
-until publication; see [BDK package availability](/#bdk-package-availability).
-
 ## Authoring forms
 
 Skills support three authoring forms.

package/docs/reference/subagents.md

@@ -11,9 +11,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](/#bdk-package-availability).
-
 ```text
 bot/subagents/researcher/
 ├── agent.ts            # description (required), model (optional)

package/docs/reference/tools.md

@@ -12,14 +12,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](/#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

package/docs/templates/agentic-owners.md

@@ -12,9 +12,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](/#bdk-package-availability).
-
 ## Scaffold
 
 ```text
@@ -92,6 +89,8 @@ next to the policy that names them. The next review reads both.
 
 ## Evals
 
+Use the three smoke reviews as a local exercise:
+
 ```text
 bdk eval
 ```

package/docs/templates/grokbot-agents.md

@@ -0,0 +1,60 @@
+---
+title: "Consult named Grok Bot agents"
+description: "Scaffold an agent that delegates a focused question to an allowed Grok Bot agent and carries the reply back."
+---
+
+# 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](../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

package/docs/templates/security-reviewer.md

@@ -11,21 +11,16 @@ 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](/#bdk-package-availability).
-
 ## Scaffold
 
 ```text
-bdk init ./security-reviewer --template security-reviewer
+bdk init ./security-reviewer --template security-reviewer \
+  --var repos=acme/api
 ```
 
-`init` asks which GitHub repos to watch. Every repo must share one
-owner. Pass `--var repos=acme/api,acme/web` to skip the prompt.
-
-The list lands in `bot/lib/repos.ts`. The GitHub channel reads it for
-`cursorAccount` and for the wake filter. Edit that file when the set
-changes.
+`--var repos` must name a repository already connected in Cursor for
+your account. Separate multiple repositories with commas; they must
+share one owner. `init` writes the list to `bot/lib/repos.ts`.
 
 ## Connect GitHub through Cursor
 
@@ -71,7 +66,8 @@ comment.
 
 ## Evals
 
-Two smoke cases: one XSS fixture and one docs-only change.
+Use the two smoke cases, one XSS fixture and one docs-only change, as a
+local exercise:
 
 ```text
 bdk eval

package/docs/templates/thermo-quality-review.md

@@ -6,15 +6,12 @@ description: "Scaffold the agent, deploy it, and open a PR."
 # 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](/#bdk-package-availability).
-
 ## Scaffold
 
 ```text
@@ -67,8 +64,8 @@ API calls use your account. See the [GitHub guide](../guides/github.md).
 
 ## Evals
 
-Two smoke cases: one spaghetti-branch fixture and one clean fix. They
-need no GitHub access.
+Use the two smoke cases, one spaghetti-branch fixture and one clean fix,
+as a local exercise. They need no GitHub access.
 
 ```text
 bdk eval

package/docs/templates/thermo-review.md

@@ -6,14 +6,12 @@ description: "Scaffold the agent, deploy it, and open a PR."
 # 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](/#bdk-package-availability).
-
 ## Scaffold
 
 ```text
@@ -66,8 +64,8 @@ API calls use your account. See the [GitHub guide](../guides/github.md).
 
 ## Evals
 
-Two smoke cases: one auth-bypass fixture and one docs-only change. They
-need no GitHub access.
+Use the two smoke cases, one auth-bypass fixture and one docs-only
+change, as a local exercise. They need no GitHub access.
 
 ```text
 bdk eval

package/docs/templates/triage.md

@@ -12,9 +12,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](/#bdk-package-availability).
-
 ## Scaffold
 
 ```text
@@ -22,6 +19,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.
 
@@ -46,6 +45,10 @@ In the Cursor dashboard, open MCP and connect Linear or Jira.
 The connection stays on the host. The model calls `record_triage`.
 Linear and Jira tools stay off the model's tool list.
 
+Linear or Jira MCP must be connected for comments, priority changes,
+and duplicate links; queueing an issue can still classify it through
+`record_triage` without that connection.
+
 ## First verdict
 
 ```text
@@ -83,7 +86,8 @@ details, when to call `record_triage`, how to reply.
 
 ## Evals
 
-Three smoke cases, one per kind. Run them after you change the rubric.
+Use the three smoke cases, one per kind, as a local exercise after you
+change the rubric.
 
 ```text
 bdk eval

package/docs/troubleshooting.md

@@ -12,11 +12,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](/#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
 
@@ -50,9 +46,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](./reference/channels.md). |

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@cursor/bdk",
-  "version": "0.2.4",
-  "description": "(early alpha) Filesystem-first framework for defining Cursor agents as markdown and TypeScript and serving them over channels with the Cursor SDK.",
+  "version": "0.2.6",
+  "description": "Build, test, and deploy BDK bots and agents as code on Cursor's agent harness.",
   "license": "SEE LICENSE IN LICENSE.md",
   "repository": {
     "type": "git",

package/templates/agentic-owners/README.md

@@ -5,9 +5,6 @@ committed in your repository: risk-tiers the diff, requests the owning
 team or user as reviewers, and approves what the policy allows. Policies
 are always read from the PR's base ref, so a PR cannot exempt itself.
 
-> **Docs ahead:** `@cursor/bdk` is not on npm yet. This command will work
-> after publication.
-
 ```text
 npx @cursor/bdk init ./owners-agent --template agentic-owners
 ```

package/templates/agents-md/README.md

@@ -5,9 +5,6 @@ listed Slack channels. Parks an update until a person approves it, then
 opens a draft follow-up PR. Chores stay quiet. Same-base updates stack
 on `agents-md/<base>`.
 
-> **Docs ahead:** `@cursor/bdk` is not on npm yet. This command will work
-> after publication.
-
 ```text
 npx @cursor/bdk init ./agents-md --template agents-md
 ```
@@ -27,6 +24,10 @@ bdk slack create --dir .
 bdk dev
 ```
 
+The Slack app uses `AGENTS_MD_SLACK_BOT_TOKEN` and
+`AGENTS_MD_SLACK_APP_TOKEN`. `bdk slack create` writes both values to
+`.env.local`.
+
 Schedules do not fire under `dev`. Dispatch the weekly job:
 
 ```text

package/templates/agents-md/evals/agents.eval.ts

@@ -13,6 +13,7 @@ const AGENTS = [
   "# API",
   "",
   "Usage events are protobuf messages in `proto/billing.proto`.",
+  "Every new billing field goes on `UsageEvent`.",
   "Do not add ad-hoc billing columns on the request path.",
   "",
 ].join("\n");

package/templates/code-wiki/README.md

@@ -4,9 +4,6 @@ Keeps `wiki/` pages current after a pull request merges. Opens a
 follow-up PR against that merge's base when a durable fact changed.
 Skips chores. Same-base updates stack on `wiki/<base>`.
 
-> **Docs ahead:** `@cursor/bdk` is not on npm yet. This command will work
-> after publication.
-
 ```text
 npx @cursor/bdk init ./code-wiki --template code-wiki
 ```

package/templates/code-wiki/bot/instructions.md

@@ -18,10 +18,10 @@ or ownership change, a removed feature.
 An empty wiki is not a license to document the whole repo. Create a
 page only for a durable contract in this merge.
 
-Skip lint, format, lockfiles, dependency pins, tests-only, cherry-picks,
-backports, telemetry-only changes, one-off bug fixes that leave the
-described behavior the same, knobs the wiki never mentioned, and facts
-the matching page already states.
+Skip lint, format, lockfiles, dependency pins, tests-only, docs-only,
+cherry-picks, backports, telemetry-only changes, one-off bug fixes that
+leave the described behavior the same, knobs the wiki never mentioned,
+and facts the matching page already states.
 
 Do not write a changelog or a PR list.
 

package/templates/demo/README.md

@@ -3,9 +3,6 @@
 Host collects the PR into `pr.md` and `files.md`. The agent records a
 walkthrough and comments the result.
 
-> **Docs ahead:** `@cursor/bdk` is not on npm yet. This command will work
-> after publication.
-
 ```text
 npx @cursor/bdk init ./my-demo --template demo
 ```