npm - @cursor/july - Versions diffs - 0.1.49 → 0.1.51 - Mend

@cursor/july 0.1.49 → 0.1.51

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (119) hide show

package/dist/playground/index.html CHANGED Viewed

@@ -8,8 +8,8 @@
     />
     <meta name="viewport" content="width=device-width, initial-scale=1" />
     <title>agent-serve playground</title>
-    <script type="module" crossorigin src="./assets/index-Dq_HqyU-.js"></script>
-    <link rel="stylesheet" crossorigin href="./assets/index-Dox74yWJ.css">
+    <script type="module" crossorigin src="./assets/index-BKMz70wx.js"></script>
+    <link rel="stylesheet" crossorigin href="./assets/index-BmMrulSc.css">
   </head>
   <body>
     <div id="root"></div>

package/docs/deployment.md CHANGED Viewed

@@ -262,7 +262,7 @@ Slack** connects the workspace with a one-time authorization, and
 **Create Slack app** creates and installs the app, then stores its
 tokens as deployment secrets automatically. Redeploy when prompted so
 the running agent picks them up. See
-[Provision from the dashboard](./guides/slack.md#provision-from-the-dashboard-hosted-deployments)
+[Provision from the dashboard](./guides/slack.md#provision-from-the-dashboard)
 for the walkthrough, including workspace-admin approval.
 If you created the Slack app by hand instead, set its tokens as

package/docs/example-agents/benny.md CHANGED Viewed

@@ -101,9 +101,8 @@ For the watched-channel path, configure a dedicated Socket Mode app with:
 - have an App-Level Token with `connections:write`, and
 - be a member of the watched channel.
-Run `agent-sdk slack setup` for the guided app workflow. Generate the project
-manifest with `--channel-posts` when you create a new copy, then validate the
-configured channel prefix with `agent-sdk slack doctor`.
+Run `agent-sdk slack create --dir examples/benny --channel-posts` for a
+dedicated Socket Mode app, then `agent-sdk slack doctor`.
 Missing dedicated-app tokens leave that channel idle. They don't stop the
 account-linked channel.

package/docs/example-agents/oncall.md CHANGED Viewed

@@ -139,14 +139,13 @@ Channel watching is Socket Mode only, so this example uses a dedicated
 app:
 ```bash
-agent-sdk slack init --dir examples/oncall --name "Oncall" --channel-posts
+agent-sdk slack create --dir examples/oncall --name "Oncall" --channel-posts
 agent-sdk slack doctor --prefix ONCALL
 ```
-The generated manifest subscribes to `message.channels` and
-`message.groups` and includes `reactions:write` for the lock-in reaction.
-Install the app, export `ONCALL_SLACK_BOT_TOKEN` and
-`ONCALL_SLACK_APP_TOKEN`, and invite the bot to each watched channel.
+`--channel-posts` prefills channel-watch events (`message.channels` /
+`message.groups`). Invite the bot to each watched channel after the
+wizard finishes.
 `ONCALL_ALERTS_CHANNELS` sets the watch list as comma-separated ids or
 `#names`. It defaults to `#alerts`.

package/docs/guides/human-in-the-loop.md CHANGED Viewed

@@ -92,7 +92,7 @@ export default slackChannel({
 });
 ```
-The Slack app manifest needs interactivity enabled. Cards show redacted,
+Approval cards need interactivity on the Slack app. Cards show redacted,
 truncated arguments because of Block Kit size limits. Execution still
 uses the full validated input, so review sensitive tools in the
 playground when the arguments may exceed the card. Details in the

package/docs/guides/slack.md CHANGED Viewed

@@ -1,15 +1,15 @@
 ---
 title: "Slack"
-description: "Put the agent in Slack over Socket Mode: Add to Slack provisioning, manifests, tokens, doctor, engagement rules, access policy, and approval buttons."
+description: "Put the agent in Slack: Cursor-hosted connection or a dedicated Socket Mode app via the dashboard wizard, plus doctor, engagement rules, access policy, and approval buttons."
 ---
 # Slack agents
-The Slack channel puts your agent in Slack over Socket Mode: no public
-Request URL, streaming replies in threads, tool "thinking" steps,
-suggested prompts, and opt-in approval buttons. Cursor's **Add to
-Slack** provisioning handles the setup in one CLI command or one
-dashboard click; the manual manifest flow remains as a fallback.
+The Slack channel puts your agent in Slack. Two products: the Cursor-hosted
+connection (`cursorAccount: true`), or a dedicated Socket Mode app created
+in the dashboard wizard (`agent-sdk slack create`). Socket Mode has no
+public Request URL. Replies stream in threads, with tool "thinking" steps,
+suggested prompts, and opt-in approval buttons.
 The companion skill is
 [`skills/setup-slack/SKILL.md`](../../skills/setup-slack/SKILL.md).
@@ -99,17 +99,17 @@ export default slackChannel({
 ## Set it up
-Start with Cursor's **Add to Slack** provisioning: Cursor creates and
-installs a dedicated Slack app for the agent and delivers its tokens,
-so nobody visits [api.slack.com](https://api.slack.com/apps) or copies
-an `xoxb-…` / `xapp-…` pair by hand. Use the CLI for local development
-and the dashboard for hosted deployments. Fall back to the
-[manual manifest flow](#manual-setup-fallback) only when provisioning
-reports the feature is not enabled for your account.
+For a dedicated Socket Mode bot, run `agent-sdk slack create`. The CLI
+opens the signed-in Cursor dashboard wizard. Slack consent, bot name,
+and admin-approval wait happen there. Tokens are stored as deployment
+secrets and written to `.env.local`. They are never shown. Do not paste
+a manifest at [api.slack.com](https://api.slack.com/apps). `slack init`
+is removed.
-### Provision with the CLI
+Bots that already have tokens in `.env.local` keep working. Skip the
+wizard unless you want a Cursor-managed app.
-One command runs the whole setup:
+### Provision with the CLI
 ```bash
 agent-sdk slack create --dir .          # dev app (default)
@@ -118,97 +118,47 @@ agent-sdk slack create --dir . --prod   # prod app
 `slack create` needs a signed-in host (`agent-sdk login` or
 `CURSOR_API_KEY`). It scaffolds `agent/channels/slack.ts` when the file
-is missing, connects your Slack workspace through a browser consent
-page when it isn't connected yet (a one-time authorization per user and
-workspace), creates and installs the agent's dedicated Socket Mode app,
+is missing, opens the dashboard wizard, and waits. Finish **Add Slack
+to this agent** in the browser as the same Cursor account. The CLI
 writes `<PREFIX>_SLACK_BOT_TOKEN` and `<PREFIX>_SLACK_APP_TOKEN` into
-`<dir>/.env.local`, and finishes with a `doctor` pass. Then serve and
-smoke it as described [below](#wire-the-env-and-verify); the tokens are
-already in place.
-If the workspace requires admin approval for new apps, `create` prints
-the Slack approval page for a workspace admin. Re-run
-`agent-sdk slack create` after the approval to finish the install and
-mint the tokens.
-Useful companions: `--slack-team T0123ABCD` picks a workspace when
-several are connected, `--icon <https-url-or-file>` sets the app icon,
-`agent-sdk slack destroy` deletes the provisioned app, and
-`agent-sdk slack icon <source>` updates the icon later. A re-run of
-`create` refuses to overwrite manifest edits made by hand in Slack;
-pass `--force` to overwrite them.
-### Provision from the dashboard (hosted deployments)
-For a [Cursor-hosted deployment](../deployment.md#cursor-managed-hosting),
-provision from
-[cursor.com/dashboard](https://cursor.com/dashboard): open **Deployed
-Agents**, select the deployment, switch to the **Details** view, and
-expand the **Slack** row under **Integrations**.
-1. Click **Add to Slack** and approve the authorization in the tab that
-   opens. This is a one-time consent per user and workspace.
-2. Pick the bot name (and the workspace, when several are connected)
-   and click **Create Slack app**. Cursor creates and installs the app,
-   then stores its tokens as deployment secrets; the values are never
-   shown. The **Advanced** disclosure sets the env-var prefix, so the
-   secret names match what your `slackChannel({ envPrefix })` reads.
-3. If the workspace requires admin approval, the row shows **Waiting
-   for admin approval** with an **Approve in Slack** button that opens
-   Slack's pending-request page. After an admin approves, pick
-   **Retry** from the row's menu.
-4. Click **Redeploy** when the banner appears. The running agent keeps
-   its old environment until the next deploy.
-The row's menu also covers later care: rename the app, set its icon,
-rotate its tokens, remove it from Slack, or disconnect the workspace.
-### Manual setup (fallback)
-When Add to Slack is not enabled for your account, create the apps by
-hand. Generate the channel file, the app manifests, and the env
-template:
+`<dir>/.env.local`, then runs `doctor`. Serve and smoke it as described
+[below](#wire-the-env-and-verify).
-```bash
-agent-sdk slack init --dir . --name "My Agent"
-```
+If Slack needs a workspace admin to approve the app, keep the CLI
+running. Managed install does not file the request — open Slack's
+**Request approval** page (the CLI prints the link; the same URL is
+**Send a reminder** after you submit). After an admin approves, click
+**Retry** in the wizard.
-This writes `agent/channels/slack.ts` (with an `envPrefix` derived from
-the directory name), importable app manifests at
-`.agent-serve/slack/manifest.{dev,prod}.json`, and
-`.agent-serve/slack/env.example`. Use `--no-prefix` for the shared
-`SLACK_*` variables on single-agent hosts, `--prefix CUSTOM` to
-override, and `--channel-posts` if you plan to watch channels.
+Useful companions: `--name` / `--icon` / `--channel-posts` prefill the
+wizard. `--slack-team T0123ABCD` picks a workspace when several are
+connected. A second `slack create` for the same agent and env overwrites
+that Slack app. It keeps the Slack app id and replaces the manifest and
+tokens. `agent-sdk slack destroy` deletes the provisioned app.
+`agent-sdk slack icon <source>` updates the icon later.
-#### Create the apps (human, Slack admin)
+### Provision from the dashboard
-This phase needs a human with permission to create Slack apps.
+The same wizard is on [Deployed Agents](https://cursor.com/dashboard).
+Open **Integrations** on an agent and click **Add Slack to this agent**,
+or follow the URL `slack create` printed.
-1. Open [api.slack.com/apps](https://api.slack.com/apps) → **Create New
-   App** → **From a manifest**.
-2. Paste `manifest.dev.json` and create the dev app.
-3. Repeat with `manifest.prod.json`. Dev and prod are separate Slack
-   apps with separate tokens.
+A first-run agent that has no hosted engine yet shows **Not deployed
+yet**. Local `agent-sdk serve` works from `.env.local`. The next
+**Deploy** injects the stored secrets; there is no Slack-only Redeploy.
-#### Install and mint tokens (human)
+If Slack needs admin approval, the wizard waits. Click **Request
+approval** to file the request in Slack (that same page later sends a
+reminder). After an admin approves, click **Retry**.
-For each app: **Install to Workspace** and copy the Bot User OAuth Token
-(`xoxb-…`), then under **Basic Information → App-Level Tokens** create a
-token with scope `connections:write` and copy it (`xapp-…`).
+The app row's menu covers later care: rename, set an icon, rotate
+tokens, remove the app, or disconnect the workspace.
 ### Wire the env and verify
 `agent-sdk slack create` already wrote the tokens to `.env.local`, so
-after provisioning skip straight to `doctor`. After a manual setup,
-export the tokens in the shell that runs `serve`, using the names from
-`env.example`, or put them in the agent directory's `.env.local` —
-`serve`/`dev`/`slack doctor` load that file (real environment variables
-always win over it):
-```bash
-export MY_AGENT_SLACK_BOT_TOKEN=xoxb-…
-export MY_AGENT_SLACK_APP_TOKEN=xapp-…
-```
+after provisioning skip straight to `doctor`. `serve` / `dev` /
+`slack doctor` load that file (real environment variables always win).
 ```bash
 agent-sdk slack doctor --prefix MY_AGENT
@@ -252,15 +202,9 @@ export default slackChannel({
 ```
 Channel watching needs the `message.channels` / `message.groups` events
-on the Slack app (Socket Mode only — not available with
-`cursorAccount: true`). Generate manifests with `slack init --channel-posts`,
-or add the events and re-import. The bot must also be a member of each
-watched channel. Posts that mention the bot stay on the `app_mention`
-path, bot-authored posts never dispatch by default, and deleting a post
-inside the debounce window cancels its dispatch. Watched posts reuse the
-thread-scoped principal, so a later @mention continues the same session.
-Set `engagement.mentions` or `engagement.directMessages` to `false` to
-turn those surfaces off.
+on the Slack app (Socket Mode only; not available with
+`cursorAccount: true`). Pass `--channel-posts` on `slack create`. The
+bot must also be a member of each watched channel.
 Set `includeBotPosts: true` when the posts worth watching come from bots:
 alert feeds, webhook integrations, or other agents posting notes. The
@@ -289,9 +233,8 @@ export default slackChannel({
 });
 ```
-The Slack app manifest must have interactivity enabled. Regenerate with
-`buildSlackManifest({ interactivity: true })` (or edit and re-import) if
-your app predates it. Composing events by hand instead: spread
+Approval cards need interactivity on the Slack app. Recreate with
+`slack create` if clicks do nothing. Composing events by hand: spread
 `buildToolApprovalEvents({ credentials })` into `events` and set
 `interactivity: true` on the channel so Socket Mode routes the clicks.
@@ -331,15 +274,11 @@ Two habits matter most.
 The `slack` subcommands cover setup end to end.
 ```bash
-agent-sdk slack setup                     # guided checklist
-agent-sdk slack create --dir .            # provision via Add to Slack (dev app)
+agent-sdk slack setup                     # two-product chooser
+agent-sdk slack create --dir .            # dashboard wizard (dev app)
 agent-sdk slack create --dir . --prod     # prod app
 agent-sdk slack destroy --dir .           # delete the provisioned app
 agent-sdk slack icon ./icon.png --dir .   # set the provisioned app's icon
-agent-sdk slack init --dir . --name "My Agent"
-agent-sdk slack init --dir . --no-prefix  # shared SLACK_* vars
-agent-sdk slack init --dir . --channel-posts
-agent-sdk slack manifest --env both       # regenerate manifests
 agent-sdk slack doctor --prefix MY_AGENT  # token / connectivity checks
 ```

package/docs/reference/cli.md CHANGED Viewed

@@ -771,35 +771,27 @@ setup.
 agent-sdk slack setup
 agent-sdk slack create [--dir <path>] [--name <name>] [--prod]
                       [--slack-team <T…>] [--team <id>]
-                      [--icon <https-url-or-file>] [--force]
+                      [--icon <https-url-or-file>]
                       [--prefix <prefix> | --no-prefix] [--json]
 agent-sdk slack destroy [--dir <path>] [--prod] [--slack-team <T…>]
                        [--team <id>] [--json]
 agent-sdk slack icon <https-url-or-file> [--dir <path>] [--prod]
                     [--slack-team <T…>] [--team <id>] [--json]
-agent-sdk slack init [--dir <path>] [--name <name>]
-                    [--prefix <prefix> | --no-prefix] [--channel-posts]
-agent-sdk slack manifest [--dir <path>] [--name <name>]
-                        [--env dev|prod|both] [--channel-posts] [--print]
 agent-sdk slack doctor [--dir <path>] [--prefix <prefix> | --no-prefix] [--json]
 ```
-`slack setup` prints a guided checklist and doesn't change files.
+`slack setup` prints the two-product chooser and doesn't change files.
-`slack create` provisions a dedicated Socket Mode app through Cursor's
-Add to Slack API instead of the manual manifest import. It requires a
-signed-in host (`agent-sdk login` or `CURSOR_API_KEY`) and the
-provisioning feature to be enabled for the account. The command
-scaffolds the channel file when missing, opens the browser consent flow
-when the workspace isn't connected to Cursor yet, creates and installs
-the app, writes the bot and app-level tokens into `<dir>/.env.local`,
-and ends with a `doctor` pass. `--prod` provisions the production app;
-the default is the development app. When the install needs a Slack
-workspace admin's approval, the command prints the approval page and
-exits non-zero; re-run it after the approval to finish and mint the
-tokens. A re-run rebuilds the manifest from the command's flags and
-refuses to overwrite edits made by hand in Slack unless you pass
-`--force`.
+`slack create` opens the signed-in Cursor dashboard wizard. Finish Slack
+consent and the bot name there. The CLI writes the token pair into
+`<dir>/.env.local` and runs `doctor`. It requires a signed-in host
+(`agent-sdk login` or `CURSOR_API_KEY`). `--prod` provisions the
+production app; the default is the development app. `--name` / `--icon`
+/ `--channel-posts` prefill the wizard. A second create for the same
+slug and env overwrites the live Slack app. If Slack needs a workspace
+admin's approval, the wizard waits; keep the CLI running, open Slack's
+**Request approval** page (the CLI prints the link), and click **Retry**
+after the admin approves. Token values never print.
 `slack destroy` deletes the provisioned app for the selected
 environment. Tokens already written to `.env.local` stay in place and
@@ -808,23 +800,8 @@ stop working.
 `slack icon` sets the provisioned app's icon from an https image URL or
 a local png, jpg, or gif file of at most 512KB.
-`slack init` creates the channel file, development and production
-manifests, `env.example`, and setup status under the project. It refuses
-to overwrite a target file. If a collision occurs, it exits non-zero;
-files created earlier in the run remain. The token prefix defaults to
-the directory basename normalized to uppercase snake case. Explicit
-`--prefix` values use the same normalization when the Agent SDK builds token
-variable names. For example, `pr-approver` becomes
-`PR_APPROVER_SLACK_BOT_TOKEN`. `--no-prefix` uses shared
-`SLACK_BOT_TOKEN` and `SLACK_APP_TOKEN`. `--channel-posts` subscribes
-the manifests to channel-post events. The command always prints a JSON
-summary.
-`slack manifest` regenerates selected manifest files. `--env` defaults
-to `both`, and `--name` defaults to the directory name. `--print` writes
-the manifest JSON to stdout instead of changing files. With the default
-`--env both`, it prints development JSON, a `--- prod ---` separator,
-then production JSON.
+`slack init` is removed. It exits non-zero and writes no files. Use
+`slack create`.
 `slack doctor` checks both tokens, Socket Mode connectivity, and
 Slack's `auth.test`. It exits non-zero when any check fails.

package/docs/troubleshooting.md CHANGED Viewed

@@ -60,9 +60,9 @@ Match your symptom below. Keep the commands as `agent-sdk`; see
 | What you see | What to do |
 | --- | --- |
 | Logs show `channel idle … missing credentials` | Expected when tokens are missing. Run `agent-sdk slack create --dir <agent>` to provision the app and write the tokens, or set `<PREFIX>_SLACK_BOT_TOKEN` and `<PREFIX>_SLACK_APP_TOKEN` per agent yourself, then run `agent-sdk slack doctor --prefix <PREFIX>`. |
-| `slack create` reports the app needs admin approval | The workspace requires admin approval for new apps. A Slack workspace admin approves it at the printed link (in the dashboard: **Approve in Slack**), then re-run `agent-sdk slack create` (or **Retry** in the dashboard). |
+| `slack create` reports the app needs admin approval | Open Slack's **Request approval** page (the CLI prints the link; the same URL is **Send a reminder** after you submit). Managed install does not file the request. Keep the CLI running, then click **Retry** in the dashboard after an admin approves. |
 | The bot ignores ordinary channel posts | Default engagement is mentions and DMs only. Enable `engagement.channelPosts` with an allowlist, and subscribe the app to `message.channels` / `message.groups`. |
-| Approve / Deny buttons do nothing | Re-import a Slack app manifest with interactivity enabled. Channels that post approval cards need `toolApprovals: true` (and `interactivity: true` when you compose events by hand). |
+| Approve / Deny buttons do nothing | Channels that post approval cards need `toolApprovals: true`. Recreate the app with `slack create` if interactivity is off. |
 ## What if host MCP OAuth fails?

package/package.json CHANGED Viewed

@@ -1,6 +1,6 @@
 {
   "name": "@cursor/july",
-  "version": "0.1.49",
+  "version": "0.1.51",
   "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": {

package/skills/create-agent/SKILL.md CHANGED Viewed

@@ -97,7 +97,7 @@ Defaults that make first cuts good:
   `prompt\`…\`` / `prompt.lines\`…\`` from `@cursor/july` (dedents indented
   multi-line strings).
 - **Env prefix** for Slack tokens = upper-snake slug (`my-agent` →
-  `MY_AGENT_SLACK_*`); `agent-sdk slack init` derives it for you.
+  `MY_AGENT_SLACK_*`); `agent-sdk slack create` derives it for you.
   Dedicated-app path only — the Cursor-hosted connection has no tokens.
 - **Host prep beats model wandering — for evidence, not judgment.** When the
   purpose has a deterministic setup step (fetch a PR, seed files), do it in
@@ -159,10 +159,9 @@ plan:
    short hand-written `agent/channels/slack.ts`
    (`slackChannel({ cursorAccount: true, agentName: "<Name>" })` — no
    tokens, no manifests); for a dedicated Socket Mode app do not hand-write
-   the channel — `agent-sdk slack init --dir ./<slug> --name "<Name>"`
-   generates `agent/channels/slack.ts` (with the env prefix) plus manifests
-   and `env.example`; customize the generated file (e.g. `suggestedPrompts`)
-   afterwards.
+   the channel — `agent-sdk slack create --dir ./<slug> --name "<Name>"`
+   opens the dashboard wizard (env prefix from the directory name);
+   customize `agent/channels/slack.ts` afterwards (e.g. `suggestedPrompts`).
 5. `evals/evals.config.ts` — `defineEvalConfig({ maxConcurrency: 20 })`
    (playground runs are memory-only unless you add `persistRuns`)
    (`maxConcurrency` is required; hard-capped at 200 due to model provider