Refresh bench tooling and Claude profiles

[brettheap]

Summary

• mount portable Claude account profiles where applicable
• refresh the bench-specific runtime and administration toolchain
• keep the bench aligned with the synchronized workBenches parent

Validation

• git diff --check
• changed shell scripts: bash -n
• changed Dockerfile: docker buildx build --check

Summary by Sourcery

Enhancements:

• Add devcontainer volume mapping for portable Claude profiles directory to make local Claude account profiles available inside the bench environment.

[brettheap]

@codex review

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates devcontainer bench tooling to mount portable Claude profiles into the container and keeps devcontainer configuration in sync with the shared workBenches setup.

File-Level Changes

Change	Details	Files
Mount portable Claude profiles into the devcontainer to share local Claude configuration with the bench runtime.	Add a bind mount for the host ~/.claude-profiles directory into the container user’s home directory Ensure the new Claude profiles mount uses cached volume semantics consistent with other Anthropic-related mounts	.devcontainer/docker-compose.usermap.yml
Refresh devcontainer configuration to align with the synchronized workBenches parent (no behavioral change visible in provided diff).	Update devcontainer.json as part of keeping bench configuration aligned with the parent workBenches setup	.devcontainer/devcontainer.json

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've reviewed your changes and they look great!

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[Copilot]

Pull request overview

This PR updates the devcontainer configuration to make portable Claude account profiles available inside the bench environment, keeping local development tooling aligned with the bench’s refreshed runtime/admin setup.

Changes:

• Add a host bind mount for ~/.claude-profiles into the devcontainer via docker-compose usermap configuration.
• Add a matching bind mount for ~/.claude-profiles in devcontainer.json mounts.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
.devcontainer/docker-compose.usermap.yml	Adds ~/.claude-profiles volume mapping into the container home directory.
.devcontainer/devcontainer.json	Adds a devcontainer mount for ~/.claude-profiles to make profiles available in-container.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: e975ed1917

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Avoid requiring optional Claude profiles

On any workstation that has the existing Claude/Codex config but no ~/.claude-profiles, this new active devcontainer mount prevents the container from being created: the devcontainer spec says mounts uses Docker --mount syntax, and Docker reports an error when a bind source path does not exist rather than creating it (see https://containers.dev/implementors/json_reference/ and https://docs.docker.com/engine/storage/bind-mounts/). If profiles are optional, create the directory in initializeCommand or make this mount opt-in so developers without that profile directory can still open the bench.

Useful? React with 👍 / 👎.