Buildkite
Buildkite keeps converting hand-rolled agent workarounds into first-class CI primitives.
A side-by-side editorial comparison of cbcTools and Cursor — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | cbcTools | Cursor |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 0.0 | 8.8 |
| Sparks · 30d | 0 | 3 |
| Top themes | conjoint-analysis, experimental-design, choice-modeling, performance | ai-agents, autonomous-agents, event-driven, cloud-agents |
| Last editorial update | 2h ago | 51m ago |
| Website | Visit → | — |
Two years quiet, then a release that makes its greedy design methods practical
cbcTools generates and evaluates designs for choice-based conjoint experiments, gathering several strategies behind one method argument in cbc_design(): random, orthogonal via DoE.base, D-optimal, Bayesian D-efficient and greedy. That structure was set during 2023 across 0.4.0 and 0.5.0, which introduced the method argument, added strategies and documented in a table which options each one supports. The only release since, in August 2025, removes efficiency limitations from the greedy methods.
Cursor's agents stop waiting to be asked - they subscribe, and they hold a goal until it's done.
Cursor has spent two months moving agents out of the editor: cloud agents on iPhone and iPad, in Slack, on schedules, a team marketplace, a router picking the model per request, and Origin hosting repos and pull requests inside the product. This release changes how those agents are started. Cloud agents can subscribe to an event source - a PR, a Slack thread, a schedule - and wake when something happens, and /goal gives one a long-lived objective it works toward until complete. Subagents now get their own virtual machines with isolated project copies.
cbcTools generates and evaluates designs for choice-based conjoint experiments, gathering several strategies behind one method argument in cbc_design(): random, orthogonal via DoE.base, D-optimal, Bayesian D-efficient and greedy. That structure was set during 2023 across 0.4.0 and 0.5.0, which introduced the method argument, added strategies and documented in a table which options each one supports. The only release since, in August 2025, removes efficiency limitations from the greedy methods.
The package was explicitly built for extension — the 0.4.0 notes say the function is now better set up to add methods in future — and the pattern since has been adding or repairing one method at a time behind a stable interface. After a two-year gap the recent work is performance rather than coverage, which suggests the greedy methods were slow enough to be impractical at realistic design sizes. Restrictions have been added deliberately too, such as blocking the label argument for orthogonal designs because it would destroy orthogonality.
On the extension pattern the maintainer set up, the next release most likely adds another design method or continues tuning existing ones for speed; the entries do not indicate which.
Cursor has spent two months moving agents out of the editor: cloud agents on iPhone and iPad, in Slack, on schedules, a team marketplace, a router picking the model per request, and Origin hosting repos and pull requests inside the product. This release changes how those agents are started. Cloud agents can subscribe to an event source - a PR, a Slack thread, a schedule - and wake when something happens, and /goal gives one a long-lived objective it works toward until complete. Subagents now get their own virtual machines with isolated project copies.
The through-line has been removing external dependencies and wait states; this release removes the human from the trigger. Agents that Cursor created now subscribe to their own pull requests and drive them to completion, fixing CI and answering bot comments unprompted. Isolated per-subagent VMs are what make that safe to parallelize - swarms can work without colliding - and steering lets a person redirect a running agent at the next tool call rather than interrupting it. Cursor is building the always-on case rather than the faster-autocomplete one.
With subscriptions limited to cloud agents for now, the obvious next step is bringing event-triggered runs to local agents, along with the controls an always-on fleet needs - spend limits, approval gates, and a way to review what ran while nobody was watching.
Other Infra & APIs products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either cbcTools or Cursor.
Buildkite keeps converting hand-rolled agent workarounds into first-class CI primitives.
Nexus does the diagnosis; the agent is now reaching into the status page too.
Warp turned its quarter of software-factory essays into infrastructure you can buy.
Okta's developer blog is a Cross App Access campaign, now diluted by advocacy-team storytelling.
A leaf-temperature model that finished its job in 2020 and has stayed finished
A credential platform assembled two or three pull requests at a time, never a headline
See all cbcTools alternatives → · See all Cursor alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Cursor is currently shipping more aggressively (velocity 8.8 vs 0.0), with 3 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Cursor is currently shipping more aggressively (velocity 8.8 vs 0.0), with 3 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
Top cbcTools alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "cbcTools alternatives" section above for the current picks, or visit /alternatives/cbctools for the full list with editorial commentary on each.
Top Cursor alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Cursor alternatives" section above for the current picks, or visit /alternatives/cursor for the full list with editorial commentary on each.