Skip to content

Refresh bench tooling and Claude profiles#1

Open
brettheap wants to merge 1 commit into
mainfrom
agent/bench-refresh-2026-07
Open

Refresh bench tooling and Claude profiles#1
brettheap wants to merge 1 commit into
mainfrom
agent/bench-refresh-2026-07

Conversation

@brettheap

@brettheap brettheap commented Jul 13, 2026

Copy link
Copy Markdown

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

Update the bench development environment to use refreshed runtime/tooling and shared Claude account profiles while keeping it aligned with the synchronized workBenches parent.

Enhancements:

  • Refresh bench-specific development tooling and runtime configuration.
  • Integrate portable, shared Claude account profile support into the bench setup.
  • Align bench configuration with the synchronized workBenches parent to reduce drift.

Build:

  • Adjust devcontainer configuration to reflect the updated bench tooling and shared profiles.

@brettheap

Copy link
Copy Markdown
Author

@codex review

Copilot AI review requested due to automatic review settings July 13, 2026 00:13
@sourcery-ai

sourcery-ai Bot commented Jul 13, 2026

Copy link
Copy Markdown
Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Refreshes devcontainer configuration to align bench tooling and Claude profiles with the synchronized workBenches parent, updating runtime/tooling and mounting portable Claude account profiles where applicable.

File-Level Changes

Change Details Files
Update the devcontainer configuration to use refreshed bench runtime/tooling and mount portable Claude profiles while staying aligned with the parent workBenches setup.
  • Adjust devcontainer settings to reflect the updated bench-specific runtime and administration toolchain.
  • Configure mounting or usage of portable Claude account profiles when available in the devcontainer environment.
  • Synchronize devcontainer options and extensions with the shared workBenches parent configuration to reduce drift.
.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

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the simBench devcontainer setup to support shared/portable Claude account profiles as part of the bench tooling refresh and alignment with the synchronized workBenches parent.

Changes:

  • Add a new devcontainer bind mount for ~/.claude-profiles into the container user’s home directory.

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

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: c194e19196

ℹ️ 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".


"source=${localEnv:HOME}/.claude,target=/home/${localEnv:USER}/.claude,type=bind,consistency=cached",
"source=${localEnv:HOME}/.claude.json,target=/home/${localEnv:USER}/.claude.json,type=bind,consistency=cached",
"source=${localEnv:HOME}/.claude-profiles,target=/home/${localEnv:USER}/.claude-profiles,type=bind,consistency=cached",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Make the Claude profiles bind mount optional

When a developer opens this devcontainer on a host that has the existing Claude files but has not created ~/.claude-profiles, this new bind mount prevents the container from starting. I checked the Dev Container metadata reference and mounts strings use Docker --mount semantics; Docker rejects missing bind sources unless bind-create-src is used, so this turns an optional profile directory into a required local prerequisite.

Useful? React with 👍 / 👎.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: c194e19196

ℹ️ 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".


"source=${localEnv:HOME}/.claude,target=/home/${localEnv:USER}/.claude,type=bind,consistency=cached",
"source=${localEnv:HOME}/.claude.json,target=/home/${localEnv:USER}/.claude.json,type=bind,consistency=cached",
"source=${localEnv:HOME}/.claude-profiles,target=/home/${localEnv:USER}/.claude-profiles,type=bind,consistency=cached",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Keep Claude profile bind mount optional

For hosts that already have ~/.claude and ~/.claude.json but have not created the non-standard ~/.claude-profiles directory, this new required bind mount prevents the dev container from starting: the Dev Containers metadata reference says mounts entries use Docker CLI --mount syntax, and Docker's bind-mount docs state that --mount errors when the source path does not exist. Please create the directory in initializeCommand or only add this mount when the host path exists.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants