Skip to content

v1.3.0

Choose a tag to compare

View all tags
@github-actions github-actions released this 29 Aug 06:12
· 201 commits to main since this release
v1.3.0
07bc12d
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Upgrading

Installing restarts the control plane, then every agent. An agent loses its
current session unless it has session resume switched on.

Two new agent states appear in this release: DiskExhausted and
BrokenRuntime. Both are recoverable and both are described below.

Added

  • Agent resource usage. Agent Details shows CPU, memory and disk used against what the agent was allocated, with warnings at 80% and 90% disk. (#158, #170)
  • DiskExhausted. An agent that fills its disk is paused instead of dying. The pod and the Shell stay up so you can clear space, and it resumes on its own once you do. (#164, #177)
  • BrokenRuntime. An agent whose harness will not run is parked with the actual error instead of looping, and Agent Details offers Repair runtime. (#171, #174)
  • Scheduled-job flags on Codex. exclusive and clearContextAfter now work on Codex agents, not only Claude Code. (#162)
  • Agent request API. A scoped endpoint for external gateways to send an agent work and poll for the reply. Off by default — it needs Redis and api.agentRequests.enabled. (#155–#163)

Fixed

  • A Claude Code agent with no credential now stops at NeedsAuth. It previously reported Running, accepted prompts, discarded them, and recorded every scheduled job as a success. (#175)
  • Codex agents keep MCP servers they registered themselves across a restart. (#160)
  • A Codex agent whose config is unreadable or unparseable repairs itself at boot, instead of being stuck on a login prompt that could never fix it. (#165, #166, #173)
  • exclusive and clearContextAfter work on a brand new agent. They were silently inert until its first restart. (#176)
  • Disk usage measures the agent's allocation rather than the node's filesystem, and keeps reporting when it cannot read every file. (#170, #172)
  • An agent stuck on its way up now reports what can be seen about it, instead of an empty error and an unchanging phase. (#167)
  • Harness upgrades install atomically. An interrupted install leaves the working version in place. (#168)
  • EKS machine creation works again — zone and disk size come from the installer profile. (#153, #156)
  • Kyber's own Codex tests no longer write outside their temp directories, which could break the machine running them. (#169)
Assets 2
Loading