v0.7.1
Codex starts normally again after updating
Agentctl v0.7.1 is a quick follow-up to v0.7.0, released earlier today. It fixes a problem where Codex could stop launching in an existing agentctl container after a Codex update, and it includes all improvements introduced in v0.7.0.
Highlights
- Codex starts normally again in Alpine-based agentctl containers. Affected users previously saw
package link escapes its rootorfailed to read start time for pid-managed app server. - The fix works whether or not Codex Remote Control is enabled. Remote Control remains optional and is not enabled automatically.
- Existing Remote Control sessions continue using their shared background service.
- Codex updates no longer leave behind a package layout rejected by newer Codex versions.
Included from v0.7.0
- Inspect managed MCP definitions and connection health with more detailed
agentctl mcp listoutput and the new read-onlyagentctl mcp statuscommand. - Diagnose MCP failures through bounded, owner-only logs and recent sanitized error events without exposing credentials, request contents, URL paths, or query strings.
- Let progressing stdio MCP operations continue through resettable idle timeouts while enforcing a configurable maximum duration, and isolate timed-out requests so healthy shared servers keep running.
- Preserve image references still used by running or stopped containers during pruning, and stop safely when image usage cannot be verified.
- Prevent upgrades from continuing with incomplete runtime-state backups, including OpenCode, Pi, and Qwen state.
- Automatically use Codex's bundled
bwrapwhen the system version cannot start the Codex sandbox, while leaving the system package unchanged.
Updating to v0.7.1
- Pull the latest repository changes to obtain agentctl v0.7.1 and all v0.7.0 improvements.
- Run
agentctl refreshfor each existing container that should receive the fix. - Start Codex normally with
agentctl run --online; the temporary--no-daemonworkaround is no longer necessary. agentctl upgradeis not required for this release.- Existing containers do not need to be recreated.
- Images do not need to be rebuilt.