Timely vs Kubernetes
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.
Kubernetes 1.36 leans into AI/ML scheduling and control-plane scaling.
The 1.36 cycle is graduation-heavy, with PSI metrics, declarative validation, and volume group snapshots all promoted to GA. Alongside that, the project is making architectural moves around workload scheduling (a new PodGroup API), API-server safety (Mixed Version Proxy on by default), and very-large-cluster scaling (server-side sharded list and watch in alpha). Etcd 3.7 has hit beta in parallel.
Kubernetes is repositioning the control plane for two pressures at once: AI/ML batch workloads, where gang scheduling and DRA are becoming first-class concerns, and very-large clusters, where the control plane itself needs to shard. The pattern across this cycle is consolidation — old experimental scaffolding is reaching GA or being removed (ExternalIPs), while new APIs land with explicit separation of static template from runtime state. Less feature sprawl, more API hygiene.
Expect 1.37 to push server-side sharded watch toward beta and to keep extending DRA's reach into native resources like memory and networking. Workload-aware scheduling will likely accumulate scheduler-plugin-level coordination patterns next, with downstream batch frameworks starting to converge on the PodGroup shape.
See more alternatives to Timely →
See more alternatives to Kubernetes →