Skip to content

chore: bump all coding CLI versions to latest#888

Merged
thepagent merged 1 commit into
mainfrom
chore/bump-cli-versions-2026-05-21
May 21, 2026
Merged

chore: bump all coding CLI versions to latest#888
thepagent merged 1 commit into
mainfrom
chore/bump-cli-versions-2026-05-21

Conversation

@chaodu-agent
Copy link
Copy Markdown
Collaborator

@chaodu-agent chaodu-agent commented May 21, 2026

Summary

Bump all 7 coding CLI versions to their latest stable releases.

CLI Previous New Notes
kiro-cli 2.2.0 2.4.0
claude-code 2.1.124 2.1.146 + bubblewrap/socat for sandbox
codex 0.128.0 0.133.0
copilot 1.0.40 1.0.51
cursor 2026.04.30-4edb302 2026.05.20-2b5dd59
gemini-cli 0.40.1 0.42.0
opencode-ai 1.14.31 1.15.7

Why bubblewrap and socat in Dockerfile.claude?

Claude Code v2.1.144+ introduced mandatory sandbox mode for bash tool calls on Linux:

  • bubblewrap (bwrap): Lightweight Linux namespace sandbox. Claude Code uses it to isolate every bash command execution into a restricted namespace (filesystem, PID, network).
  • socat: Socket relay tool. Claude Code uses it to pipe stdin/stdout between the sandboxed process and the main Claude Code process.

The problem: If these binaries are missing, Claude Code v2.1.144+ silently exits on launch with no error message (anthropics/claude-code#61094). There is no fallback to unsandboxed mode.

Since openab already runs inside Docker containers, this is effectively sandbox-inside-container — redundant but harmless. Both packages add ~400KB total to the image layer. The alternative (pinning to 2.1.143) would miss 22 patch releases of fixes and improvements.

Why not Dockerfile.codex too?

Codex CLI also uses bubblewrap for its Linux sandbox, but bundles its own bwrap binary. If the system bwrap is not found on PATH, Codex prints a warning and falls back to its bundled copy — it does NOT crash. No additional system packages needed for Codex.

Regression Check

Reviewed open issues on all public trackers. Key findings:

  • claude-code #61094: v2.1.144+ silently exits on Linux when bubblewrap and socat are missing. Mitigated by adding both packages to Dockerfile.claude.
  • claude-code #61141: MCP permissions lost in ephemeral containers (Remote Routines specific — does not affect openab's ACP-based invocation).
  • claude-code #61232: Worktree isolation bleed on Linux (intermittent, multi-agent worktree specific).
  • codex #23651: Zellij scrollback over SSH (TUI-specific, not applicable to headless Docker).
  • codex #23857: Sandbox supervision unreliable (macOS-specific).
  • opencode #27908: Spinner garbage in non-TTY (cosmetic only).
  • gemini-cli: Zero open bugs.
  • copilot / cursor / kiro-cli: No public regression trackers or zero relevant issues.

Testing

  • Docker build smoke test (CI)

- kiro-cli: 2.2.0 → 2.4.0
- claude-code: 2.1.124 → 2.1.146 (+ add bubblewrap/socat for sandbox)
- codex: 0.128.0 → 0.133.0
- copilot: 1.0.40 → 1.0.51
- cursor: 2026.04.30-4edb302 → 2026.05.20-2b5dd59
- gemini-cli: 0.40.1 → 0.42.0
- opencode-ai: 1.14.31 → 1.15.7

Claude Code v2.1.144+ requires bubblewrap and socat for its sandbox
on Linux. Without them the CLI silently exits (anthropics/claude-code#61094).
Added both packages to Dockerfile.claude apt-get layer.
@github-actions
Copy link
Copy Markdown

⚠️ This PR is missing a Discord Discussion URL in the body.

All PRs must reference a prior Discord discussion to ensure community alignment before implementation.

Please edit the PR description to include a link like:

Discord Discussion URL: https://discord.com/channels/...

This PR will be automatically closed in 3 days if the link is not added.

@github-actions github-actions Bot added the closing-soon PR missing Discord Discussion URL — will auto-close in 3 days label May 21, 2026
@thepagent thepagent merged commit 28c212e into main May 21, 2026
18 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

closing-soon PR missing Discord Discussion URL — will auto-close in 3 days

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants