Buildkite vs Ably
Side-by-side trajectory, velocity, and editorial themes.
AI-agent skills and OAuth Token Exchange land — Buildkite is courting both Claude/Cursor users and security teams.
Buildkite is shipping in two strong directions at once. On platform/security: OAuth 2.0 Token Exchange (RFC 8693) replaces long-lived API tokens with IdP-minted short-lived ones, and per-user API rate limits stop one runaway script from starving an org's quota. On surface area: official Buildkite skills for Claude Code, Cursor and similar AI coding agents teach agents how to use the platform, plus broader GitHub event triggers for incremental Actions migration. Smaller UX work (new build page list view, queue search, cluster sort) rounds out a heavy ship cadence.
Two arcs are converging: lowering the on-ramp for teams migrating off GitHub Actions (more triggers, agent-friendly skills, cleaner UI) and meeting the security posture larger customers ask for in procurement (short-lived tokens, scoped per-user limits). The agent-skills release in particular signals Buildkite expects pipeline configuration to increasingly be authored or modified by AI agents, and is moving to teach them in Buildkite's own voice.
Expect more skills coverage across specific Buildkite features (dynamic pipelines, OIDC federation patterns) and follow-on auth work — OIDC-based agent authentication, finer scopes on exchanged tokens. The GitHub Actions migration push will likely add equivalents for less common triggers (deployments, workflow_dispatch) to remove remaining excuses to stay.
Ably pivots its developer surface toward AI agents as first-class consumers
Ably's developer surface has been visibly pivoting toward AI agents over the last six weeks. The CLI hit v1.0 with structured JSON output envelopes, hint fields for self-healing agents, and unified --force semantics. Two weeks later v1.1 added `ably init`, which installs the CLI plus Agent Skills bundles directly into Claude, Cursor, Windsurf, and VS Code in one step. A new AI Transport SDK lands separately, with end-to-end tool-calling and React providers for the Vercel AI SDK.
Ably is building two integration stories in parallel — agents as CLI users (via Agent Skills) and agents as transport consumers (via the AI Transport SDK). Together they bracket the workflow: agents read live data through the SDK and operate Ably itself through the CLI. The traditional client-library stream (JS, Python, Laravel) continues at steady pace in the background, with LiveObjects formally graduating to GA on the protocol-6 update.
Expect the AI Transport SDK to add tool-call adapters for at least one more AI runtime beyond Vercel — most likely the OpenAI Agents SDK or Anthropic's Claude Agent SDK — and Agent Skills coverage to expand to additional AI clients (Cline, Aider, Continue). Watch for the LiveObjects API to surface inside the chat/AI surfaces.
See more alternatives to Buildkite →
See more alternatives to Ably →