Add Cursor Agent and Grok Build
Install the Cursor Agent and Grok Build CLIs in managed workspaces from pinned, digest-checked packages. Bind an account API key and enable their Internet egress groups only where you need them.
Cursor Agent and Grok Build are partial adapters: they have no devctrl MCP injection, quota telemetry or Task Graph reports, and live authenticated runs have not been executed. The native process can read its API key. They are two of the optional native CLI adapters listed in the capability matrix; none of those is claimed as verified native support.
How it works
Install a verified CLI
Cursor Agent and Grok Build install from pinned packages whose digests are checked before use. A newer adapter does not replace a running native CLI.
Bind the account key
Bind one owned secret as the account API key. Only new launches of that account’s sessions receive it, and shared accounts never receive the owner’s key.
Grant network access explicitly
Their model and sign-in hosts are optional egress groups. Existing Project Internet restrictions stay in force until you enable them.
Try the interface
Explore the sample projects, accounts, files and access requests. Live sessions and file transfers are available in your own console.
Put your server to work.
Give your agents persistent remote workspaces. Start with one repository and server, then add projects, developers and resources from the same console.