# Changelog

## 0.6.0 (2026-11-03)

### Minimum versions

- `@grok/agent-sdk` requires `@cursor/sdk` 1.3.0.

### Behavior changes

- On Cursor-managed hosting, when the team turns on its Cloud Agent Allowlist, a turn checks the `url:` and `command:` connections it opens against that list. It also checks their network hosts against the team's network allowlist for Cloud Agents. Before, it used the team's MCP Allowlist. Agents that you run with `agent-sdk serve` keep the MCP Allowlist.
- On Cursor-managed hosting, when the team turns on its Cloud Agent Allowlist, the Cursor backend checks each `cursorAccount` connection against that list. The turn's local MCP checks no longer refuse these connections.
- An agent with `cursorAccount` connections starts its shared workspace after those connections resolve. Other agents still start it when the server starts.

## 0.5.0 (2026-10-28)

### Breaking changes

- No change to which file tools an `fs` agent has or what they do. Their results now use Cursor's native tool-call shape instead of Agent SDK's earlier MCP-style text, in `tool_call` events, transcripts, and direct tool calls. The same holds without `fs`. Update code that parses these results. For example, a direct `read` call returns `{ status: "success", value: { content } }` instead of numbered lines.
- With `fs`, a `tools` list gets only the file tools it names. Add `"read"`, `"ls"`, `"glob"`, `"grep"`, `"edit"`, and `"delete"` to keep them.
- `@grok/agent-sdk/executors` is removed. Remove that import. The npm package has no replacement.
- `synthesizeFileSystemTools` is removed. Pass your tree as `fs`.
- `nearestNeighborMissHint` is removed. Read suggests nearby names when a file is missing.
- `RunnerTurnRequest` carries `fs`, `reportedWorkspacePath`, and `settingSources` instead of `root` and `subagentInherit`.

### Minimum versions

- `@grok/agent-sdk` requires `@cursor/sdk` 1.2.0.

### Behavior changes

- With `fs`, `AGENTS.md` and `.cursor/rules/` in the workspace load as project rules, as they do on the host. Don't make a checkout you don't trust the workspace.
- With `fs`, omitting `tools` gives every tool the tree can back, including subagents, web search, web fetch, todos, and MCP.
- With `fs`, a `tools` list that names a tool the tree can't run, such as `readLints`, leaves it out with a warning. Before, `readLints` with `fs` failed validation.
- With `fs`, LS, Grep, and Glob search the workspace when a call names no path.
- With `fs`, each turn gets an empty `/tmp`. Large web results are written there.
- With `fs`, subagents work on the agent's tree, and their writes land in it as the agent's own do. Before, each subagent wrote to its own copy.
- `local.sandbox` works with `fs`. A tool call that needs approval, such as an external MCP call, fails closed. File access doesn't change.
- With `local.sandbox` and no `fs`, an agent with shell in `tools`, or with `tools` omitted, can read outside the session workspace with the file tools, as its shell already could. Writes and deletes outside it are still refused.
- With `local.sandbox` and no `fs`, an agent whose `tools` list file tools and no shell runs on its session workspace, mounted at `/workspace`, and its reads stay inside it. Cursor hooks don't run for it, so a Slack follow-up waits for the turn to end. `.cursor/mcp.json` from its working directory isn't loaded, host git status doesn't reach the model, and its skills are at `/agent/skills`.
- An agent tool can be named `Read`, `Grep`, or another file tool's name.

### New

- `workspace` sets the folder inside `fs` that the agent works in. For a sandboxed agent without shell, it sets where the session workspace is mounted.

### Fixes

- An agent that exports OpenTelemetry traces no longer logs a duplicate propagator registration error on its first HTTP request.

## 0.4.0 (2026-10-27)

### Breaking changes

- The `FileSystem` type, its helpers, and its errors match the file tools, and the package root exports `readOnlyFs`.

### Fixes

- A reply in a Slack thread that a schedule started continues that session.
- A hosted Slack agent with `botMentions.allowFrom` starts a session when an allowed bot mentions it.

## 0.3.0 (2026-10-25)

- GA Release
- `persistent` option is removed from `defineAgent`

## 0.2.29 (2026-10-23)

- Bug Fixes
