Appearance
Changelog
0.6.0 (2026-11-03)
Minimum versions
@grok/agent-sdkrequires@cursor/sdk1.3.0.
Behavior changes
- On Cursor-managed hosting, when the team turns on its Cloud Agent Allowlist, a turn checks the
url:andcommand: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 withagent-sdk servekeep the MCP Allowlist. - On Cursor-managed hosting, when the team turns on its Cloud Agent Allowlist, the Cursor backend checks each
cursorAccountconnection against that list. The turn's local MCP checks no longer refuse these connections. - An agent with
cursorAccountconnections 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
fsagent has or what they do. Their results now use Cursor's native tool-call shape instead of Agent SDK's earlier MCP-style text, intool_callevents, transcripts, and direct tool calls. The same holds withoutfs. Update code that parses these results. For example, a directreadcall returns{ status: "success", value: { content } }instead of numbered lines. - With
fs, atoolslist gets only the file tools it names. Add"read","ls","glob","grep","edit", and"delete"to keep them. @grok/agent-sdk/executorsis removed. Remove that import. The npm package has no replacement.synthesizeFileSystemToolsis removed. Pass your tree asfs.nearestNeighborMissHintis removed. Read suggests nearby names when a file is missing.RunnerTurnRequestcarriesfs,reportedWorkspacePath, andsettingSourcesinstead ofrootandsubagentInherit.
Minimum versions
@grok/agent-sdkrequires@cursor/sdk1.2.0.
Behavior changes
- With
fs,AGENTS.mdand.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, omittingtoolsgives every tool the tree can back, including subagents, web search, web fetch, todos, and MCP. - With
fs, atoolslist that names a tool the tree can't run, such asreadLints, leaves it out with a warning. Before,readLintswithfsfailed 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.sandboxworks withfs. A tool call that needs approval, such as an external MCP call, fails closed. File access doesn't change.- With
local.sandboxand nofs, an agent with shell intools, or withtoolsomitted, 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.sandboxand nofs, an agent whosetoolslist 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.jsonfrom 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
workspacesets the folder insidefsthat 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
FileSystemtype, its helpers, and its errors match the file tools, and the package root exportsreadOnlyFs.
Fixes
- A reply in a Slack thread that a schedule started continues that session.
- A hosted Slack agent with
botMentions.allowFromstarts a session when an allowed bot mentions it.
0.3.0 (2026-10-25)
- GA Release
persistentoption is removed fromdefineAgent
0.2.29 (2026-10-23)
- Bug Fixes