@cursor/july 0.1.104 → 0.1.107

package/dist/docs/llms-full.txt

@@ -4372,6 +4372,99 @@ key. Handlers you author replace the matching defaults (same as
 
 ---
 
+Source: /docs/guides/grokbot-agents.md
+
+# Cursor Grok Bot agents
+
+The `cursor-grokbot-agents` extension lets an agent send a message to
+one of your Grok Bot agents and read the reply. The Grok Bot keeps its
+own conversation, memory, and tools. Your agent stays where it is and
+consults that bot the way you would in the Grok Bot app.
+
+This is different from moving this agent's turns onto a hosted Grok Bot.
+The extension keeps the agent where it is and lets it talk to *other*
+Grok Bot agents.
+
+## Mount it
+
+The extension ships with `@cursor/july`. Mount it with one file.
+
+```ts
+// agent/extensions/grokbot.ts
+import cursorGrokBotAgents from "@cursor/july/extensions/cursor-grokbot-agents";
+
+export default cursorGrokBotAgents({
+  agents: [
+    { name: "Plan Keeper", description: "Keeps or moves outdoor plans." },
+    { name: "Chief of Staff", description: "Routes work and tracks priorities." },
+  ],
+});
+```
+
+`agents` is the allowlist. List every Grok Bot the model may talk to;
+a name outside the list is refused. Calls run under the host's
+signed-in account (`agent-sdk login` or `CURSOR_API_KEY`). Keep
+approval on when you can't.
+
+Start from the [Grok Bot agents template](/docs/templates/grokbot-agents.md)
+when you want a project that already mounts this.
+
+## What the agent can do
+
+With the extension mounted, the agent can consult a Grok Bot and stay
+in its own conversation:
+
+- **Ask.** Send a self-contained message to a Grok Bot by the name
+  shown in the Grok Bot app. The message lands in your conversation
+  with that bot. The tool waits for the bot's reply.
+- **Keep waiting.** A long turn returns `status: "running"`. Call check
+  with the same name to read what arrived since the last look.
+- **Stop a turn.** Interrupt the bot's current work. The conversation
+  stays; a later ask continues it.
+- **See who you can talk to.** List the configured bots and the ones
+  this caller has already asked. Add a name to `agents` when you want
+  the model to reach another bot.
+
+A skill teaches the model when to bring a Grok Bot in, how to write a
+message the bot can act on alone, and how to wait or interrupt. The
+reply is what the Grok Bot sent to the person. If a turn finishes with
+no reply, the bot sent nothing; ask again with a clearer request, or
+open the bot in the Grok Bot app.
+
+The tools reach Grok Bot agents on the signed-in account. A bot another
+user owns is out of reach. That separation is only as fine as your
+host's auth; a shared bearer token or `--allow-anonymous` makes every
+caller one principal, so use
+[authored auth](/docs/reference/channels.md#auth-policies) when callers
+need their own.
+
+## Configure it
+
+| Option | What it controls |
+| --- | --- |
+| `agents` | The Grok Bot agents the model may talk to, by the name shown in the app. A lone entry is the default when a call names none. Omit `agents` to allow any name; an unknown name creates an empty Grok Bot on the account. |
+| `needsApproval` | Park asks for a [human decision](/docs/guides/human-in-the-loop.md). Defaults to `true` when no `agents` are configured, `false` otherwise. |
+| `apiKey` | A Cursor API key to call with instead of the host's own. |
+
+## Adjust it
+
+To take a capability away, such as interrupting a turn, mount as a
+directory and disable that tool; see
+[overlays](/docs/reference/extensions.md#adjust-a-mounted-extension).
+
+## What's next
+
+Continue with these pages:
+
+- [Grok Bot agents template](/docs/templates/grokbot-agents.md): scaffold
+  an agent that already mounts this
+- [Extensions](/docs/reference/extensions.md): how mounts, namespaces, and
+  overrides work
+- [Human-in-the-loop approvals](/docs/guides/human-in-the-loop.md): where parked
+  asks get approved
+
+---
+
 Source: /docs/guides/human-in-the-loop.md
 
 # Human-in-the-loop approvals
@@ -4768,10 +4861,9 @@ is `serve({ otel })` over `agent/otel.ts` over env. An empty
 `defineOtel()` still records traces; export starts when
 `OTEL_EXPORTER_OTLP_*` or a factory-returned `exporters` list appears.
 
-Hosted v2 binds deployment secrets after bake, onto the already-listening
-process. Pass a factory so flush can re-read them. Spans record from
-bake; the hosted handler flush constructs the OTLP client and sends the
-queued batch.
+Hosted deployments can bind secrets after startup. Pass a factory so
+flush can re-read them. The hosted handler constructs the OTLP client
+when it flushes and sends the queued batch.
 
 ```ts
 export default defineOtel(() => resolveMyOtelConfig());
@@ -5785,10 +5877,11 @@ npx @cursor/july docs
 | Building a new agent with Cursor | [Scaffold an agent with Cursor](/docs/scaffolding-agents.md) |
 | Turning a Cursor Automation into a project | [Convert a Cursor Automation](/docs/guides/convert-automation.md) |
 | Wiring an agent to Slack | [Slack guide](/docs/guides/slack.md) |
-| Starting from a packaged template | [Demo](/docs/templates/demo.md), [Code wiki](/docs/templates/code-wiki.md), [Living AGENTS.md](/docs/templates/agents-md.md), [Security reviewer](/docs/templates/security-reviewer.md), [Security help](/docs/templates/security-help.md), [Triage](/docs/templates/triage.md), or [Agentic Owners](/docs/templates/agentic-owners.md) |
+| Starting from a packaged template | [Demo](/docs/templates/demo.md), [Grok Bot agents](/docs/templates/grokbot-agents.md), [Code wiki](/docs/templates/code-wiki.md), [Living AGENTS.md](/docs/templates/agents-md.md), [Security reviewer](/docs/templates/security-reviewer.md), [Security help](/docs/templates/security-help.md), [Triage](/docs/templates/triage.md), or [Agentic Owners](/docs/templates/agentic-owners.md) |
 | Wiring an agent to GitHub webhooks | [GitHub guide](/docs/guides/github.md) |
 | Driving PRs from a cloud VM | [PR autofixer template](/docs/templates/pr-autofixer.md) |
 | Handing coding work to Cursor cloud agents | [Cursor cloud agents](/docs/guides/cloud-agents.md) |
+| Talking to your Grok Bot agents | [Cursor Grok Bot agents](/docs/guides/grokbot-agents.md) |
 | Driving an agent from Linear (or another tracker) | [Webhooks guide: Linear example](/docs/guides/webhooks.md#example-linear-as-the-control-plane) |
 | Making an existing agent measurably better | [Evals](/docs/evals.md), then [Hillclimbing](/docs/hillclimbing.md) |
 | Comparing variants on live traffic | [Live A/B metrics](/docs/ab.md) |
@@ -5812,6 +5905,8 @@ npx @cursor/july docs
 
 - [Record a walkthrough from a collected PR](/docs/templates/demo.md): host
   collects the PR, the model records, then comments.
+- [Talk to your Grok Bot agents](/docs/templates/grokbot-agents.md): name
+  the bots, then consult them from this agent's own conversation.
 - [Keep a code wiki current after merge](/docs/templates/code-wiki.md):
   update in-repo `wiki/` pages when a pull request merges.
 - [Keep AGENTS.md current from last week's work](/docs/templates/agents-md.md):
@@ -5855,6 +5950,8 @@ npx @cursor/july docs
   server; agents can delegate to each other.
 - [Cursor cloud agents](/docs/guides/cloud-agents.md): let the agent launch
   and steer cloud agents through the `cursor-cloud-agents` extension.
+- [Cursor Grok Bot agents](/docs/guides/grokbot-agents.md): let the agent
+  talk to Grok Bot agents through the `cursor-grokbot-agents` extension.
 - [OpenTelemetry](/docs/guides/opentelemetry.md): push session, turn, and
   tool traces to an OTLP collector you run.
 
@@ -6867,20 +6964,16 @@ events. Declare `events` and handle each one in `onEvent`. Each event
 carries `deploySourceUri` and `deployVersion`. Author
 `agent/channels/deployments.ts` with `deploymentsChannel()`.
 
-Omit `deploySourceUris` on hosted v2. The control plane binds
-`deploy_source` edges from the deploy's watched `repositories` and the
-channel admits what it is sent, which is what makes it multi-tenant
-safe.
-
-Name sources to narrow below that scope, or to drive the self-hosted
-pull relay, which has no deploy scope to inherit. There, subscribe per
-deploy source with `deploySourceUris` and narrow with `environments` /
-`events`. Each entry must match `Deployment.deploy_source_uri` as your
-deployment writer records it; matching is case-insensitive but
+On Cursor-managed hosting, omit `deploySourceUris`. The deployment's
+watched repositories bind the event scope automatically. Name sources
+to narrow the scope or to drive the self-hosted pull relay. Subscribe
+per deploy source with `deploySourceUris` and narrow with `environments`
+or `events`. Each entry must match `Deployment.deploy_source_uri` as
+your deployment writer records it. Matching is case-insensitive but
 otherwise literal. It uses the host credential. A restart resumes
-rather than dropping events. An empty `deploySourceUris` list mounts
-the channel but starts no pull, so an env-configured agent stays inert
-until its deploy sources are set.
+rather than dropping events. An empty `deploySourceUris` list mounts the
+channel but starts no pull, so an env-configured agent stays inert until
+its deploy sources are set.
 
 **Change Monitors** (`@cursor/july/channels/change-monitors`): Change
 Monitor Checkpoint events. The channel publishes Factory
@@ -6889,18 +6982,14 @@ result (for example to the `issues` arm). The payload contains the
 full Checkpoint resource. This channel is scoped to Change Monitors,
 not generic Factory Checkpoints. There is no repository filter or
 resource filter. Author `agent/channels/change-monitors.ts` with
-`changeMonitorsChannel()`. It uses the host credential. The v1 omitted
-continuation is `none/v1`. A v2 agent defaults to
-`change_monitors.checkpoint/v2`, which keys the session as
-`cont:change_monitors:{checkpointName}`.
+`changeMonitorsChannel()`. It uses the host credential.
 
 **Issues** (`@cursor/july/channels/issues`): Factory issue events.
 The channel publishes `issue.created` for every Issue create. The
 agent filters if it needs a subset. The payload contains the full
 Issue resource. There is no repository filter or resource filter.
 Author `agent/channels/issues.ts` with `issuesChannel()`. It uses the
-host credential. The v1 omitted continuation is `none/v1`. A v2 agent
-defaults to `issues.issue/v2`, which keys the session by issue name.
+host credential.
 
 For other platforms like Discord or Teams, use the authored
 `defineChannel` webhook form.
@@ -7338,6 +7427,7 @@ non-zero when the reconstructed trajectory failed.
 ```bash
 agent-sdk init ./my-agent          # scaffold package.json, tsconfig.json, agent/ + a demo tool
 agent-sdk init ./my-demo --template demo              # record a PR walkthrough
+agent-sdk init ./grokbot --template grokbot-agents    # talk to Grok Bot agents
 agent-sdk init ./code-wiki --template code-wiki       # keep wiki pages current after merge
 agent-sdk init ./agents-md --template agents-md       # keep AGENTS.md current from last week's PRs and Slack
 agent-sdk init ./my-reviewer --template security-reviewer   # review PRs for security bugs
@@ -7359,7 +7449,7 @@ agent-sdk init                     # no directory: print the setup guide
 Templates may ship `init.json`. On a TTY, `init` asks those questions
 before writing files. `code-wiki`, `pr-autofixer`, `security-help`, and
 `agents-md` ask for GitHub repos. `agents-md` also asks for Slack
-channels. Repeat
+channels. `grokbot-agents` asks for Grok Bot names. Repeat
 `--var id=value` to answer without a prompt.
 `--json` and non-TTY hosts skip the interview unless `--var` is set.
 
@@ -7597,14 +7687,17 @@ The command polls for up to ten minutes until the status reaches
 
 ## delete
 
-`delete` removes a deployment.
+`delete` removes a hosted deployment. You can delete a deployment that
+still runs. The command frees the slug. A later deploy can use the same
+name. Spend stays on the archived service account.
 
 ```bash
 agent-sdk delete <slug> [--team <id>] [--no-wait] [--json]
 ```
 
 The command waits until the deployment is gone. `--no-wait` returns after
-the delete request is accepted.
+the delete request is accepted. Architecture v2 slugs use the Agent SDK
+control plane. Architecture v1 slugs use the Agent Serve control plane.
 
 ## rotate-token
 
@@ -8464,6 +8557,8 @@ Continue with these pages:
 
 - [Cursor cloud agents](/docs/guides/cloud-agents.md): the extension that
   lets an agent launch and steer cloud agents
+- [Cursor Grok Bot agents](/docs/guides/grokbot-agents.md): the extension
+  that lets an agent talk to Grok Bot agents
 - [Tools](/docs/reference/tools.md): the tool contract extensions contribute to
 - [Skills](/docs/reference/skills.md): the skill forms an extension can carry
 - [Project layout](/docs/reference/project-layout.md): where `agent/extensions/` sits
@@ -11206,9 +11301,9 @@ export default defineOtel({
 3. `serve(dir, { otel: { … } })`. `otel: false` disables env and
    authored config.
 
-Hosted v2 secrets arrive after bake. Use `defineOtel(() => …)` so flush
-re-resolves exporters. Authored `agent/otel.ts` records from process
-start even when the factory returns no exporters yet.
+Hosted secrets can arrive after startup. Use `defineOtel(() => …)` so
+flush re-resolves exporters. Authored `agent/otel.ts` records from
+process start even when the factory returns no exporters yet.
 
 | Signal | Default |
 | --- | --- |
@@ -11949,6 +12044,59 @@ Playground and `/queue/pr` need the alias token. GitHub label and
 
 ---
 
+Source: /docs/templates/grokbot-agents.md
+
+# Talk to your Grok Bot agents
+
+This agent sends a message to a Grok Bot you already use and reads the
+reply. The Grok Bot keeps its conversation. This agent stays where it
+is.
+
+## Scaffold
+
+```bash
+npx @cursor/july init ./grokbot --template grokbot-agents
+```
+
+`init` asks for the names shown in the Grok Bot app. Every name is an
+allowlist entry. Pass `--var agents="Plan Keeper, Chief of Staff"` to
+skip the prompt.
+
+The names land in `agent/extensions/grokbot.ts`. A name outside that
+list is refused.
+
+## Log in
+
+Asks run under the signed-in account.
+
+```bash
+cd grokbot
+agent-sdk login
+agent-sdk dev
+```
+
+In the playground, ask it to talk to one of the names you entered.
+
+## What to edit
+
+- `agent/extensions/grokbot.ts`: who it may talk to. Add `needsApproval: true` to park each ask.
+- `agent/instructions.md`: when to consult them
+
+See [Cursor Grok Bot agents](/docs/guides/grokbot-agents.md) for the
+extension, and [Human-in-the-loop approvals](/docs/guides/human-in-the-loop.md)
+for where a parked ask gets approved.
+
+## Evals
+
+```bash
+agent-sdk eval
+```
+
+The smoke case asks who it can talk to. It must list the configured
+bots and not send a message.
+
+---
+
 Source: /docs/templates/pr-autofixer.md
 
 # Fix pull requests on a Cursor cloud VM

package/dist/docs/llms.txt

@@ -27,6 +27,7 @@
 - [Keep AGENTS.md current from last week's work](/docs/templates/agents-md.md): Scaffold the agent, pick a repo and Slack channels, dispatch the weekly job, and deploy.
 - [Keep a code wiki current after merge](/docs/templates/code-wiki.md): Scaffold the agent, pick repos, replay a merged PR, and deploy.
 - [Record a walkthrough from a collected PR](/docs/templates/demo.md): Scaffold the agent, seed the PR on the host, record a walkthrough, and comment the result.
+- [Talk to your Grok Bot agents](/docs/templates/grokbot-agents.md): Scaffold the agent, name the Grok Bot agents it may reach, and consult them from its own conversation.
 - [Fix pull requests on a Cursor cloud VM](/docs/templates/pr-autofixer.md): Scaffold the agent, point it at your repos, and opt in to auto-fix a PR.
 - [Answer security questions in Slack](/docs/templates/security-help.md): Scaffold the agent, connect Slack, and answer from your skills. Paste a GitHub pull request for a first look.
 - [Review pull requests for exploitable bugs](/docs/templates/security-reviewer.md): Scaffold the agent, pick repos, replay a PR, and deploy.
@@ -38,6 +39,7 @@
 - [Cursor cloud agents](/docs/guides/cloud-agents.md): Let an agent-sdk agent hand coding work to Cursor cloud agents and steer them: mount the extension, pick the repositories it may touch, and decide what needs approval.
 - [Convert a Cursor Automation](/docs/guides/convert-automation.md): Export a dashboard Automation into a local Agent SDK project, then review, validate, and run it.
 - [GitHub](/docs/guides/github.md): Wake your agent from pull requests, CI, and comments by pulling Cursor SCM events, with fixtures and replay for local tests.
+- [Cursor Grok Bot agents](/docs/guides/grokbot-agents.md): Let an agent-sdk agent talk to your Grok Bot agents: mount the extension, name the bots it may reach, and decide what needs approval.
 - [Human-in-the-loop](/docs/guides/human-in-the-loop.md): Gate a tool call on human approval: park it, resolve it from the playground, HTTP, or Slack, and keep the turn alive throughout.
 - [Host MCP OAuth](/docs/guides/mcp-oauth.md): Authorize defineConnection({ url, oauth: true }) with agent-sdk mcp oauth, store tokens locally, and push MCP_OAUTH_* secrets to hosted deployments.
 - [OpenTelemetry](/docs/guides/opentelemetry.md): Push session, turn, and tool traces from the serve process to an OTLP collector you run.