Timely vs Buildkite
Side-by-side trajectory, velocity, and editorial themes.
Timely repositions Memory.app as the time tracker that understands AI-tool work.
The dominant theme is AI-aware activity capture. Memory.app — Timely's local capture agent — now distinguishes Claude Desktop, Claude Code, Cowork, Codex, and Cursor Agents as discrete tools, pulls real window titles and URLs, and scrubs credentials from captured URLs before storage. Around that, Timely keeps grinding through platform work: inline project creation, OAuth auto-refresh, project audit logs, native changelog page, and integration manager improvements.
Timely is racing to be the time tracker that knows what AI tools you used and what you used them for. The Memory capture layer is being rebuilt assuming AI tools, agents, and chat sessions are first-class workstreams, not generic 'browser activity.' The platform updates underneath — audit logs, integration housekeeping, OAuth resilience — are keeping the enterprise surface presentable while the differentiation work happens in capture.
Expect support for more AI tools (Anthropic console, ChatGPT Desktop, Gemini, copilots inside IDEs) and richer project attribution heuristics that tie a conversation or branch to a billable project automatically. Privacy controls around AI activity capture are the natural next product question.
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.
See more alternatives to Timely →
See more alternatives to Buildkite →