v1.1.0

Highlights

Scheduled jobs can clear the agent's context after each run. A job gains clearContextAfter. Without it an unattended job piles every fire onto one growing conversation, and the agent eventually stops being able to act on new prompts while still reporting healthy. The platform performs the clear — an agent cannot reliably do it from inside its own turn.

Exclusive now means the agent is busy, not the dispatch is busy. The lock only ever spanned the tmux paste (milliseconds), while the turn it started ran for minutes — so a job firing faster than its own work completes stacked prompts onto a single-threaded agent and dispatches were silently dropped. A fire during an unfinished turn now records outcome=skipped reason=agent_busy.

An agent's skills are visible, and provably loadable. A read-only Skills tab on Agent Details, backed by GET /api/v1/agents/{name}/skills. The report scans the pod, not GitHub, so it names skills that are committed but loadable by nothing, malformed or undescribed SKILL.md files, vendored skills shadowing the agent's own, and skill directories written into a runtime home that won't survive a reprovision. The platform relinks and rescans on a loop, so a skill an agent simply writes and commits becomes loadable within a couple of minutes rather than depending on it remembering a command. There is no write path — skills are added and removed by talking to the agent.

A resumed session now receives its startup prompt. With sessionResume and startupPrompt both set, an agent returning from a pod recreate, preemption, or crash is handed the prompt instead of resuming with full context and no turn to act on. An intentional restart-session still starts fresh and delivers the prompt there, unchanged.

PWA browser branding. Transparent cyan Kyber diamond for the favicon and Android/PWA install icons, full-bleed Apple touch icon so iOS applies its own corner mask, and the active cluster name in the browser title.

Also in this release

• CI now builds the status-sidecar on pull requests, tagged by head SHA.
• Node 26 across the build and test toolchain.
• Go, Kubernetes client, and npm dependency bumps (~15 PRs).

Upgrading

• Installing restarts the control plane, then every agent — each loses its current session.
• New CRD field spec.jobs[].clearContextAfter, applied by the chart upgrade. Existing jobs are unchanged; the clear is off unless you set it.
• No manual steps.