Heartbeat Monitoring and A Better Run Activity View

Heartbeat status became a first-class agent signal, and the run activity view became much easier to navigate during long executions.

This release focused on visibility. It became much easier to see whether an agent is still keeping its rhythm, and much easier to inspect long runs without losing your place.

Heartbeat Status Became A First-Class Agent Signal

Agent pages now expose heartbeat health more clearly, including the current cadence and the next expected execution time.

  • Heartbeat status is easier to understand from the agent itself
  • Recurrence changes are clearer and more immediate
  • Status presentation is more compact and scannable, so you can read it quickly instead of parsing a dense card

Long Run Activity Is Easier To Navigate

The run activity view picked up a long list of quality-of-life improvements that add up to a much smoother inspection flow.

  • Sticky headers keep important context visible while you scroll through active work
  • Older activity loads progressively, which helps long histories feel less heavy
  • Entity links, file links, and navigation state behave more reliably, so drilling into related work is less disruptive
  • The file viewer keeps its state better, making it easier to move between logs and files during investigation

Agent Kinds Got Stronger Operational Controls

Agent kind management also improved, including a reprovision action and stronger kind-specific defaults, which makes it easier to keep specialized agents aligned with the role they were created for.