Profiles / Anysphere
Cursor
Closed editor, CLI, and cloud agent, harvested from the changelog, never from github.com/cursor/cursor.
Operator Read
Added 21 August 2026. Closed Anysphere product. The evidence is the changelog and the CLI docs.
github.com/cursor/cursor looks like a
repository. It is a README, a security policy, and a .github directory.
Download the editor from cursor.com. Install the terminal agent with
curl https://cursor.com/install -fsS | bash and run agent. Do not open
that GitHub tree looking for a sandbox.
At intake the changelog led with a 19 August 2026 entry about cloud-agent
subscriptions, custom modes, subagents on their own machines, and /goal.
Those sentences are what the vendor published that day. They are not yet a
statement that the agent CLI gained those behaviors. The next harvest has
to say which surface moved.
Operator Stance / as of 2026-08-21
- Use it for
- Teams already in the Cursor editor or cloud-agent product who need a dated, changelog-backed read of what the vendor says shipped. The terminal surface is the `agent` CLI from `curl https://cursor.com/install`.
- Avoid it for
- Anyone who must audit enforcement in source. github.com/cursor/cursor will not help. Do not treat a cloud-agent changelog entry as a CLI change, or Origin hosting as a permission model.
- Watch next
- Whether the CLI, the editor, and cloud agents keep one permission story or three; whether `/goal` and isolated-VM subagents are described for the CLI or only for cloud agents; whether any versioned binary digest becomes pinable the way Antigravity's tarball is.
Why it is here
People already run it. Omnigent already routes work onto it. A publication that watches the wrap and not the wrapped tool is guessing at the gate.
This is Claude Code's floor, not Codex's. You can date a changelog entry.
You cannot git merge-base a permission claim. That is still worth doing.
The changelog is how an operator learns that a control was announced, and
a local probe is how they learn whether it binds.
What to do with it
When you read an entry, write down editor, CLI, cloud agent, or Origin before you write down the feature. If the page does not say, the finding does not either. Pin a CLI version string if the installed binary reports one. If it does not, the dated changelog URL is the whole channel.
Verification
closed source release notes / evidence floor: official changelog / updated 2026-08-21
Open Questions
- Github Tracker Is Not Source
- Changelog Mixes Surfaces
Source policy: what Frontier watches and accepts as evidence
Edited and maintained by Bitter Frontier.