@cursor/july 0.1.29 → 0.1.31

package/skills/hillclimb/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: agentkit-hillclimb
 description: >-
-  Iterate on a specific agentkit agent by running the local server,
+  Iterate on a specific Agent SDK agent by running the local server,
   sending real requests, measuring correctness/efficiency, and proposing
   the next harness or prompt change. Read this skill when improving an
   existing agent.
@@ -9,9 +9,9 @@ paths:
   - packages/agent-serve/**/*
 ---
 
-# Agentkit hillclimb
+# Agent SDK hillclimb
 
-Optimize one agentkit agent project
+Optimize one Agent SDK agent project
 with a tight measure → change → remeasure loop. Do not redesign the
 whole framework; climb one concrete failure mode at a time. Sibling skills:
 `framework-map` (orientation), `evals` (the ratchet), `ab` (live variant
@@ -36,15 +36,15 @@ If those are missing, ask before editing.
 A climb over a moving input is noise. Before round 1:
 
 - **GitHub agents** — replay, don't wait for live events:
-  `agentkit github replay <pr> --dir <project>` synthesizes signed,
+  `agent-sdk github replay <pr> --dir <project>` synthesizes signed,
   GitHub-shaped payloads from read access only, identically every run;
   `--dry-run --out fixtures/github` snapshots them for offline replay.
 - **Tool behavior** — isolate host tools from the model with
-  `agentkit call <tool> --dir <project> --input '{...}'` (schema-validated,
+  `agent-sdk call <tool> --dir <project> --input '{...}'` (schema-validated,
   in-process, no turn). If the tool output is wrong, no prompt change fixes it.
-- **Chat agents** — `agentkit run --dir <project> --message "<fixture>"`
+- **Chat agents** — `agent-sdk run --dir <project> --message "<fixture>"`
   gives a JSON trajectory plus an NDJSON trace under
-  `<project>/.agent-serve/traces/`; `agentkit trajectory --events <file>`
+  `<project>/.agent-serve/traces/`; `agent-sdk trajectory --events <file>`
   re-summarizes any saved trace.
 - **Manual probes** — the playground Try modal on any channel route
   remembers your last body per endpoint and has Copy curl; a successful Try
@@ -59,7 +59,7 @@ Repeat until the user stops or fixtures meet the criteria.
 - Serve with Node (never Bun):
 
   ```bash
-  agentkit serve --dir <project> --dev
+  agent-sdk serve --dir <project> --dev
   ```
 
 - Hit the agent the way a user would (channel HTTP, playground, Slack in
@@ -131,7 +131,7 @@ State the hypothesis in one sentence: *“If we X, metric Y should move because
 - **Ratchet every kept change**: land an eval that would have failed before
   it (tool-choice gate, `action.result` count bound, output-shape regex —
   see `evals/SKILL.md`), and never weaken an existing gate to make a round
-  pass. `agentkit eval --dir <project> --json` is the regression check
+  pass. `agent-sdk eval --dir <project> --json` is the regression check
   between rounds.
 
 Present a short round report to the user before starting the next climb.

package/skills/mcp-auth/SKILL.md

@@ -2,14 +2,14 @@
 name: agentkit-mcp-auth
 description: >-
   Authorize host MCP OAuth for defineConnection({ url, oauth: true }):
-  agentkit mcp oauth, local mcp-auth.json, --store deployment secrets,
+  agent-sdk mcp oauth, local mcp-auth.json, --store deployment secrets,
   hostOnly, and egress. Read when wiring or debugging MCP auth.
 ---
 
 # Host MCP OAuth (mcp auth)
 
 Use this skill when a human asks to authorize a remote MCP server on an
-agentkit host, store credentials for Cursor-managed hosting, or debug
+Agent SDK host, store credentials for Cursor-managed hosting, or debug
 `host.mcp` auth failures for `oauth: true` connections.
 
 Sibling skills: `framework-map` for layout, `create-agent` when scaffolding,
@@ -35,8 +35,8 @@ those tools.
 - [ ] `agent/mcp-connections/<name>.ts` with `url` + `oauth: true` (+ `hostOnly` if privileged)
 - [ ] `hosting.secretNames` lists `MCP_OAUTH_<NAME>_{ACCESS_TOKEN,REFRESH_TOKEN,CLIENT_ID}` when you will `--store`
 - [ ] Hosted engines that reach non-bootstrap hosts declare `hosting.egressDomains`
-- [ ] Local: `agentkit mcp oauth <name>` succeeds
-- [ ] Hosted: `agentkit mcp oauth <name> --store` then redeploy; `secrets list` shows the names
+- [ ] Local: `agent-sdk mcp oauth <name>` succeeds
+- [ ] Hosted: `agent-sdk mcp oauth <name> --store` then redeploy; `secrets list` shows the names
 
 ## Phase 0 — Author the connection (agent)
 
@@ -83,7 +83,7 @@ Update instructions so the model does not hunt IDE MCP namespaces or
 
 ```bash
 cd <agent-project>
-agentkit mcp oauth <connection>
+agent-sdk mcp oauth <connection>
 ```
 
 Human completes the browser login. Callback:
@@ -95,12 +95,12 @@ re-run; resource URL binding drops the old entry.
 
 ## Phase 2 — Store on the deployment (agent + human)
 
-Requires `agentkit login` (or `CURSOR_API_KEY`) and deploy rights.
+Requires `agent-sdk login` (or `CURSOR_API_KEY`) and deploy rights.
 
 ```bash
-agentkit mcp oauth <connection> --store [--slug <slug>] [--team <id>]
-agentkit secrets list <slug>
-agentkit deploy   # or your usual deploy; secrets apply next deploy
+agent-sdk mcp oauth <connection> --store [--slug <slug>] [--team <id>]
+agent-sdk secrets list <slug>
+agent-sdk deploy   # or your usual deploy; secrets apply next deploy
 ```
 
 `--store` upserts access (required), refresh (if present), and client id
@@ -111,8 +111,8 @@ agentkit deploy   # or your usual deploy; secrets apply next deploy
 Local:
 
 ```bash
-agentkit validate --dir .
-agentkit call <tool-that-uses-host.mcp> --dir .
+agent-sdk validate --dir .
+agent-sdk call <tool-that-uses-host.mcp> --dir .
 # or exercise the same path from the playground
 ```
 

package/skills/setup-slack/SKILL.md

@@ -1,17 +1,17 @@
 ---
 name: agentkit-setup-slack
 description: >-
-  Put an agentkit agent in Slack. Covers the required connection decision
+  Put an Agent SDK agent in Slack. Covers the required connection decision
   (Cursor-hosted connection vs dedicated Socket Mode Slack app) with an
   AskQuestion gate, then both setup paths end to end — cursorAccount
   sign-in + smoke, or manifests, tokens, doctor, smoke test, and opt-in
   Slack tool approvals (HITL). Read this skill when wiring Slack for an
-  agentkit project.
+  Agent SDK project.
 ---
 
-# Setup Slack for agentkit
+# Setup Slack for the Agent SDK
 
-Use this skill when a human asks to wire Slack to an agentkit agent.
+Use this skill when a human asks to wire Slack to an Agent SDK agent.
 
 There are **two ways to connect**, and they differ mostly in setup cost:
 
@@ -24,7 +24,7 @@ There are **two ways to connect**, and they differ mostly in setup cost:
   token pair. Required for channel watching, approval buttons, or a
   distinct bot handle. When the workspace is enrolled in Cursor's
   **Add to Slack** (feature gate + a workspace-manager consent),
-  `agentkit slack create` provisions all of it in one command.
+  `agent-sdk slack create` provisions all of it in one command.
 
 **Do not generate manifests or ask for tokens until the decision below
 is made.** Defaulting into Path B buries the user in Slack admin work
@@ -36,7 +36,7 @@ Walk the user through the tradeoffs before touching files:
 
 | | A: Cursor-hosted | B: Dedicated Slack app |
 | --- | --- | --- |
-| Setup | Zero Slack admin — sign the host in (`agentkit login` / `CURSOR_API_KEY`) and serve | Enrolled in Cursor's Add to Slack: one `agentkit slack create` per env (app + install + tokens, signed-in host). Otherwise: a Slack admin creates **two** apps (dev + prod) from manifests, installs them, mints `xoxb-…` + `xapp-…` for each |
+| Setup | Zero Slack admin — sign the host in (`agent-sdk login` / `CURSOR_API_KEY`) and serve | Enrolled in Cursor's Add to Slack: one `agent-sdk slack create` per env (app + install + tokens, signed-in host). Otherwise: a Slack admin creates **two** apps (dev + prod) from manifests, installs them, mints `xoxb-…` + `xapp-…` for each |
 | Prereq | Cursor Slack integration installed in the workspace and linked to the Cursor account | Permission to create Slack apps; token storage/rotation is on you |
 | How users reach it | `@Cursor <AgentName> …`, DMs to @Cursor, replies in claimed threads | Its own bot user: @mention, DM, channel invites |
 | Identity | Posts as the Cursor app under the agent's name + icon | Own app name, avatar, and handle |
@@ -81,7 +81,7 @@ threaded reply. No Slack app, no tokens, no manifests.
 ### A1 — Author the channel (agent)
 
 Write `agent/channels/slack.ts` by hand — do **not** run
-`agentkit slack init` (that scaffolds the Path B manifests + env):
+`agent-sdk slack init` (that scaffolds the Path B manifests + env):
 
 ```ts
 import { slackChannel } from "@cursor/july/channels/slack";
@@ -104,11 +104,11 @@ blocked by default; see `policy.blockExternals` in
 ### A2 — Sign in + serve (agent)
 
 ```bash
-agentkit login   # or export CURSOR_API_KEY
-agentkit dev .
+agent-sdk login   # or export CURSOR_API_KEY
+agent-sdk dev .
 ```
 
-Confirm log: `[agentkit] cursor-slack: relaying Slack for <AgentName> …`.
+Confirm log: `[agent-sdk] cursor-slack: relaying Slack for <AgentName> …`.
 An unsigned host fails `serve` with a sign-in hint naming the channel.
 
 ### A3 — Smoke (human)
@@ -145,7 +145,7 @@ Goal:
 
 Update `.agent-serve/slack/setup-status.json` as you complete phases.
 
-### Provisioned variant — `agentkit slack create` (primary when enrolled)
+### Provisioned variant — `agent-sdk slack create` (primary when enrolled)
 
 When the Slack workspace is enrolled in Cursor's **Add to Slack**
 (the provisioning feature gate plus a workspace-manager consent), one
@@ -153,8 +153,8 @@ command collapses Phases 0–3 — manifest import, app creation, install,
 and token minting:
 
 ```bash
-agentkit slack create --dir <agent>          # dev app (default)
-agentkit slack create --dir <agent> --prod   # prod app
+agent-sdk slack create --dir <agent>          # dev app (default)
+agent-sdk slack create --dir <agent> --prod   # prod app
 ```
 
 `create` scaffolds `agent/channels/slack.ts` + the `.agent-serve/slack`
@@ -163,11 +163,11 @@ consent flow when the workspace is not connected yet, provisions +
 installs the app, writes `<PREFIX>_SLACK_BOT_TOKEN` /
 `<PREFIX>_SLACK_APP_TOKEN` into `<dir>/.env.local` (replacing stale
 lines), and finishes with `doctor`. It needs a signed-in host
-(`agentkit login` / `CURSOR_API_KEY`). Pass `--slack-team <id>` when
+(`agent-sdk login` / `CURSOR_API_KEY`). Pass `--slack-team <id>` when
 several workspaces are connected. If the install lands in
 `pending_admin_approval`, a Slack workspace admin must approve the
 printed link — then re-run `create` to finish and mint the tokens.
-`agentkit slack destroy` deletes the provisioned app (tokens left in
+`agent-sdk slack destroy` deletes the provisioned app (tokens left in
 `.env.local` simply stop working). Skip to Phase 4 when `create`
 succeeds — `dev`/`serve` load the agent's `.env.local` (real env wins).
 Note: re-running `create` rebuilds the app manifest from the command's
@@ -222,7 +222,7 @@ MY_AGENT_SLACK_APP_TOKEN=xapp-…
 ```
 
 ```bash
-agentkit slack doctor --prefix MY_AGENT
+agent-sdk slack doctor --prefix MY_AGENT
 ```
 
 Stop when `app_token`, `connections_open`, `bot_token`, and `auth_test` are green.
@@ -230,10 +230,10 @@ Stop when `app_token`, `connections_open`, `bot_token`, and `auth_test` are gree
 ### Phase 4 — Serve + smoke (agent + human)
 
 ```bash
-agentkit dev .
+agent-sdk dev .
 ```
 
-Confirm log: `[agentkit/slack] Socket Mode connected`.
+Confirm log: `[agent-sdk/slack] Socket Mode connected`.
 
 When tokens are missing the channel logs
 `channel idle reason=missing credentials need=…` and `serve` continues — useful
@@ -336,14 +336,14 @@ Requirements and caveats:
 tooling; Path A needs only `login`.
 
 ```bash
-agentkit slack setup
-agentkit slack create --dir .                     # provision via Add to Slack (dev app)
-agentkit slack create --dir . --prod              # prod app
-agentkit slack create --dir . --slack-team T0123ABCD
-agentkit slack destroy --dir . [--prod] [--slack-team T0123ABCD]
-agentkit slack init --dir . --name "My Agent"
-agentkit slack init --dir . --no-prefix
-agentkit slack init --dir . --channel-posts   # + message.channels/groups events
-agentkit slack manifest --env both
-agentkit slack doctor --prefix MY_AGENT
+agent-sdk slack setup
+agent-sdk slack create --dir .                     # provision via Add to Slack (dev app)
+agent-sdk slack create --dir . --prod              # prod app
+agent-sdk slack create --dir . --slack-team T0123ABCD
+agent-sdk slack destroy --dir . [--prod] [--slack-team T0123ABCD]
+agent-sdk slack init --dir . --name "My Agent"
+agent-sdk slack init --dir . --no-prefix
+agent-sdk slack init --dir . --channel-posts   # + message.channels/groups events
+agent-sdk slack manifest --env both
+agent-sdk slack doctor --prefix MY_AGENT
 ```

package/src/bin/agent-serve.ts

@@ -189,7 +189,7 @@ Commands:
               machine-readable and never blocks on login. No directory:
               print the setup guide.
   install-skills
-              Install (or refresh) the agentkit skills for coding agents in
+              Install (or refresh) the Agent SDK skills for coding agents in
               ~/.cursor/skills/agentkit and print where they landed. \`init\`
               offers this once, interactively, and skips it when the prompt
               goes unanswered; this command never asks. --print previews
@@ -1240,7 +1240,7 @@ async function main(argv: string[]): Promise<number> {
             })
             .catch((error: unknown) => {
               process.stderr.write(
-                `[agentkit] restart failed: ${
+                `[agent-sdk] restart failed: ${
                   error instanceof Error
                     ? (error.stack ?? error.message)
                     : String(error)
@@ -1586,7 +1586,7 @@ function installTransportErrorGuards(): void {
   const log = (label: string, reason: unknown): void => {
     const text = reason instanceof Error ? reason.message : String(reason);
     process.stderr.write(
-      `[agentkit] ${label} (server stays up): ${text.slice(0, 400)}\n`
+      `[agent-sdk] ${label} (server stays up): ${text.slice(0, 400)}\n`
     );
   };
   process.on("unhandledRejection", (reason) => {
@@ -1602,7 +1602,7 @@ function installTransportErrorGuards(): void {
       return;
     }
     process.stderr.write(
-      `[agentkit] uncaughtException: ${error.stack ?? error.message}\n`
+      `[agent-sdk] uncaughtException: ${error.stack ?? error.message}\n`
     );
     process.exit(1);
   });

package/src/channels/github/index.ts

@@ -6,7 +6,7 @@
  *
  * export default githubChannel({
  *   botName: "my-agent",
- *   // Reuses `agentkit login` for events, ctx.github, ctx.host.github, and gh.
+ *   // Reuses `agent-sdk login` for events, ctx.github, ctx.host.github, and gh.
  *   cursorAccount: { repos: ["owner/repo"] },
  *   onComment: (ctx, comment) => ({ auth: defaultGitHubAuth(ctx) }),
  *   onPullRequest: (ctx, pr) =>

package/src/channels/slack/bot-mentions.ts

@@ -20,7 +20,7 @@ import type {
   SlackMessage,
 } from "./types.js";
 
-/** Slack message `metadata.event_type` for agentkit delegation posts. */
+/** Slack message `metadata.event_type` for Agent SDK delegation posts. */
 export const SLACK_DELEGATION_METADATA_EVENT_TYPE = "agentkit_delegation";
 
 /** Default budgets for {@link SlackBotMentionsOptions}. */

package/src/channels/slack/eval-directive.ts

@@ -154,7 +154,7 @@ export function isSlackEvalDirective(
 
 export function formatSlackEvalHelp(): string {
   return [
-    "*Eval commands* (same batches as the playground / `agentkit eval --prod`):",
+    "*Eval commands* (same batches as the playground / `agent-sdk eval --prod`):",
     "• `eval` — run all evals",
     "• `eval <id> [id…]` — run specific eval ids",
     "• `eval --tag <tag>` — run evals with a tag (`-t` also works)",

package/src/channels/slack/external-policy.ts

@@ -1,5 +1,5 @@
 /**
- * Workspace-membership checks for AgentKit Slack agents.
+ * Workspace-membership checks for Agent SDK Slack agents.
  * Mirrors backend `isExternalSlackUser` (cloud-agent/slack/externalChannelPolicy).
  */
 

package/src/channels/slack/log.ts

@@ -2,7 +2,7 @@
  * Shared logging for the Slack channel pack.
  *
  * Uses the same `(line: string) => void` contract as ServeOptions.logger.
- * Lines always start with `[agentkit/slack]` so Socket Mode docs and greps
+ * Lines always start with `[agent-sdk/slack]` so Socket Mode docs and greps
  * keep working. Optional key=value fields carry correlation ids.
  */
 

package/src/channels/slack/setup.ts

@@ -60,7 +60,7 @@ export const SLACK_SETUP_PHASES: SlackSetupPhase[] = [
     title: "Serve",
     steps: [
       "agent-serve serve --dir . --dev",
-      "Confirm log: [agentkit/slack] Socket Mode connected",
+      "Confirm log: [agent-sdk/slack] Socket Mode connected",
     ],
   },
   {

package/src/channels/slack/socket-mode.ts

@@ -52,7 +52,7 @@ function createBridgeLogger(write: (line: string) => void): Logger {
     },
     getLevel: () => level,
     setName() {
-      // Name is unused; agentkit prefixes lines itself.
+      // Name is unused; Agent SDK prefixes lines itself.
     },
   };
 }

package/src/evals/reporters.ts

@@ -16,7 +16,7 @@
  * });
  * ```
  *
- * `agentkit eval --junit <path>` and `--artifacts <dir>` attach these same two
+ * `agent-sdk eval --junit <path>` and `--artifacts <dir>` attach these same two
  * reporters without touching the eval files, which is usually the better fit:
  * CI owns the output paths, not the eval author.
  */

package/src/evals.ts

@@ -622,7 +622,7 @@ export interface HostStartEvalRunInput {
 
 /**
  * Host-facing playground eval batches — the same surface as
- * `/v1/dev/evals*` and `agentkit eval --prod`. Attached to
+ * `/v1/dev/evals*` and `agent-sdk eval --prod`. Attached to
  * {@link import("./types.js").HostContext.evals} by `serve`.
  */
 export interface HostEvalsApi {
@@ -663,7 +663,7 @@ export interface EvalConfigFile {
    * Optional. Max batches kept in the **playground / `/v1/dev/evals*`**
    * history window (in-memory, and pruned from the `defineStorage` evals
    * table when one is configured). Includes server-side batches started by
-   * `agentkit eval --prod` or `--url` (not the default local harness).
+   * `agent-sdk eval --prod` or `--url` (not the default local harness).
    *
    * Default {@link EVAL_DEFAULT_MAX_PLAYGROUND_RUNS}; hard-capped at
    * {@link EVAL_MAX_PLAYGROUND_RUNS}. Newest batches win.