more info on setup, if you can: are you using a non-intel GPU for rendering?

nvidia GPU for me with hardware acceleration enabled (required some command-line flags passed to chrome to get it working on wayland):

    google-chrome-stable --enable-gpu --ozone-platform=wayland --enable-features=UseOzonePlatform,WaylandLinuxDrmSyncobj

in this context, the container contains the running claude instance, and pairing synchronizes its worktree with your local worktree.

under sculptor, claude code CAN execute tests by itself when not paired. that will also work for non-dockerized applications.

sharing a postgres across containers may require a bit of manual tweaking, but we support the devcontainer spec, so if you can configure e.g. your network appropriately that way, you can use a shared database as you like!

regarding multiplexing: the cognitive overhead is real. we are investigating mechanisms for reducing it. more on that later.

regarding mobile integration: we also want that! more on that later.

no sir. only the fullest featured repositories for our free-range* claudes

* containerized, but meets free range standards