@cursor/bdk 0.2.16 → 0.2.17

package/docs/guides/migrate.md

@@ -5,9 +5,9 @@ description: "Move a hosted BDK architecture v1 project to v2 through a reviewed
 
 # Migrate an early-alpha project to architecture v2
 
-Use this guide only for projects deployed during the Grok Bot Development Kit
-(BDK) early alpha. Projects that never deployed on architecture v1 already use
-v2 and need no migration.
+Use this guide only for Bot Development Kit (BDK) projects deployed during the
+early alpha. Projects that never deployed on architecture v1 already use v2
+and need no migration.
 
 ## Check whether your project needs migration
 

package/docs/quickstart.md

@@ -5,9 +5,9 @@ description: "Create a BDK bot or agent that reviews pull requests by complexity
 
 # Build a PR reviewer with BDK
 
-Build a Grok Bot Development Kit (BDK) PR reviewer that classifies changes as `trivial`,
-`moderate`, or `large`, then approves safe changes or requests human
-review.
+Build a PR reviewer with the Bot Development Kit (BDK). It classifies
+changes as `trivial`, `moderate`, or `large`, then approves safe changes or
+requests human review.
 
 ## Prerequisites
 

package/docs/reference/cli.md

@@ -5,7 +5,7 @@ description: "Look up BDK commands, targets, flags, outputs, and exit status."
 
 # BDK CLI
 
-The Grok Bot Development Kit (BDK) uses the `@cursor/bdk` package and `bdk`
+The Bot Development Kit (BDK) is published as `@cursor/bdk` with the `bdk`
 CLI.
 
 ```text

package/docs/reference/http-api.md

@@ -5,10 +5,10 @@ description: "Public session, discovery, and channel routes callers use."
 
 # HTTP API
 
-Grok Bot Development Kit (BDK) hosts expose one public HTTP surface. In the default
-multi-agent layout, each agent uses `/<slug>/v1/*`; `--mode single`
-serves the same routes at `/v1/*`. Routes use the agent's HTTP auth
-chain, and session-owned resources return `403` to another principal.
+Bot Development Kit (BDK) hosts expose one public HTTP surface. In the default
+multi-agent layout, each agent uses `/<slug>/v1/*`; `--mode single` serves the
+same routes at `/v1/*`. Routes use the agent's HTTP auth chain, and
+session-owned resources return `403` to another principal.
 
 Unless a section says otherwise, the default auth policy is
 `localDevStrict()`. `--bearer-token` replaces it with bearer auth, and

package/docs/reference/project-layout.md

@@ -5,9 +5,8 @@ description: "The canonical bot/ folder layout and its path-derived naming rules
 
 # Project layout
 
-The Grok Bot Development Kit (BDK) builds a project by walking the
-filesystem under `bot/`. The path a file lands in determines how BDK
-loads it.
+A Bot Development Kit (BDK) project keeps agent files under `bot/`. Each
+file's path determines how BDK loads it.
 
 Existing projects rooted at `agent/` remain supported.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cursor/bdk",
-  "version": "0.2.16",
+  "version": "0.2.17",
   "description": "Build, test, and deploy BDK bots and agents as code on Cursor's agent harness.",
   "license": "SEE LICENSE IN LICENSE.md",
   "repository": {
@@ -356,11 +356,11 @@
     "vitest": "^4.0.18",
     "yaml": "^2.4.2",
     "zustand": "^5.0.9",
-    "@anysphere/agent-exec": "1.0.0",
+    "@anysphere/agent-store-sync": "1.0.0",
+    "@anysphere/proto": "1.0.0",
     "@anysphere/context": "1.0.0",
     "@anysphere/ui": "1.0.0",
-    "@anysphere/proto": "1.0.0",
-    "@anysphere/agent-store-sync": "1.0.0"
+    "@anysphere/agent-exec": "1.0.0"
   },
   "scripts": {
     "build": "tsc -p tsconfig.build.json && node scripts/bundle-publish-shims.mjs && node scripts/copy-extension-assets.mjs && pnpm run build:playground && pnpm run docs:build",