@cursor/bdk 0.2.3 → 0.2.4

package/docs/deployment.md

@@ -62,7 +62,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.
 

package/docs/guides/jev.md

@@ -23,6 +23,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](../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

package/docs/reference/agent-config.md

@@ -35,7 +35,7 @@ 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. |
+| `hosting` | `{ egressDomains?, secretNames? }` | Managed-hosting declarations read by `bdk deploy`: the pod's egress allowlist and the secret names the agent expects. Mounted [extensions](./extensions.md#build-an-extension) add their own. Ignored by local serving. |
 | `concurrency` | `{ maxRunningTurns? }` | Engine-wide turn admission 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). |

package/docs/reference/extensions.md

@@ -54,6 +54,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
@@ -174,6 +178,7 @@ export default defineExtension({
     token: z.string(),
     logTailLines: z.number().int().positive().default(200),
   }),
+  hosting: () => ({ egressDomains: ["api.buildkite.com"] }),
 });
 ```
 
@@ -182,6 +187,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](./project-layout.md) owns each contribution's
 authoring contract. Keep extension instructions and tool descriptions
 namespace-neutral because the consumer chooses the final prefix.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cursor/bdk",
-  "version": "0.2.3",
+  "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.",
   "license": "SEE LICENSE IN LICENSE.md",
   "repository": {
@@ -28,14 +28,6 @@
     "!dist/internal/review-comments*",
     "!dist/internal/shallow-clone.*",
     "!dist/internal/managed-delivery.*",
-    "src/**/*",
-    "!src/**/*.test.ts",
-    "!src/internal/tenant-mcp/**",
-    "!src/internal/tenant-slack/**",
-    "!src/internal/grokbot/**",
-    "!src/internal/review-comments*",
-    "!src/internal/shallow-clone.ts",
-    "!src/internal/managed-delivery.ts",
     "skills/**/*",
     "templates/**/*",
     "!templates/pr-autofixer/README.md",