Tldr yes they're the same agentic harness in different UIs. Web browser, android app, ide extension, cli tool. They all change the "how" but not the "what".
You buy premium you get more prompts and models.
For my personal cms I'm using sveltia. But their oath page assumes the repo remote is also the IdP, this means my login button has a GitHub logo instead of Google logo. Now I had spare credits so I forked it. Next weekend I'm fixing their weird support for asset management in R2 buckets.
So your company is fine giving access to their entire GitHub to a third party, and being locked into GitHub too?
If their SaaS could work with local only repo setups it would be a better UX...
It sounds like diff #2 depends on approval of diff #1? But with cursor it's a set of diffs that'll be retroactively approved or rejected one by one.
So you can get coffee during the thinking and still have interactive checks. Swarm changes nothing about this, except affecting the thinking time.
I think cursor doesn't make distinction between single or multiple logical tasks for swarm-like workloads. Subagents is the word they use for the swarm workers.
Fwiw when I select multiple models for a prompt it just feeds the same prompt to them in parallel (isolated worktrees), this isn't the same as the swarm pattern in 2.4+ (default no worktrees).
I ran parallel prompt with composer 2 and gpt5.3 codex. Composer did slightly better, in terms of variable naming and extra tweaks to loosely related files to keep the codeb consistent.
How is that relevant. A decent scientist can critique general design aspects of a paper in any field. They're hardly splitting hairs on some niche topic.
They all do, true. But some are better than the others in how they retrieve, digest and present you with the information. Boils down to personal preferences and experimenting.
reply