Skip to content

ClaudeBox v2.0.1 — macOS reliability and clipboard fixes

Latest

Choose a tag to compare

@RchGrav RchGrav released this 15 Sep 22:27
1011158

macOS reliability update

  • Fix Bash 3.2 empty-array errors in fresh installs, saved flags, profiles, and runtime paths.
  • Use macOS-compatible command checksums and portable multiline Dockerfile generation.
  • Preserve managed Python interpreters across fresh containers and slot changes.
  • Fix explicit slot selection when all slots are active; claudebox slot N attaches to the selected running session.
  • Add opt-in claudebox --clipboard for macOS clipboard images and application text copy. Requires host Python 3. The bridge is loopback-only, authenticated per session, bounded, and stopped with its launcher. It does not read host clipboard text.
  • Fix firewall startup so failed DNS resolution cannot leave default policies open; firewall setup failures now stop session startup.
  • Fix MCP cleanup, optional environment/gitconfig mounts, SSH fallback, profile installation, and onboarding documentation.

Installation

Download claudebox.run below and run bash claudebox.run profiles to install or update. Existing project images rebuild when changed build inputs are detected. Start clipboard-enabled sessions with claudebox --clipboard slot 1; a running slot without clipboard support must be restarted to enable it.

For Apple Terminal selection trouble, the reporter-confirmed workaround is Select All, paste into an editor, then copy the needed URL. This is separate from application clipboard forwarding; this release does not claim to change terminal mouse-selection behavior.

Validation

Native macOS Bash 3.2 and Linux CI, installed-artifact tests, Python/Node clipboard protocol tests, native private-pasteboard PNG/TIFF/text checks, and real Colima/Docker startup, firewall, clipboard, and Python persistence tests. The automated container smoke uses a fixture Claude command rather than an authenticated Claude TUI.

Includes the fixes integrated in #110, #111, #112, and #113, with thanks to the original issue reporters and pull-request contributors.