Skip to content

Add Claude Code cloud environment setup script#64

Merged
jssblck merged 1 commit into
mainfrom
claude/setup-env
Jun 23, 2026
Merged

Add Claude Code cloud environment setup script#64
jssblck merged 1 commit into
mainfrom
claude/setup-env

Conversation

@jssblck

@jssblck jssblck commented Jun 23, 2026

Copy link
Copy Markdown
Member

Adds scripts/setup-claude-env.sh, a setup script for a Claude Code cloud environment.

Point an environment's setup command at ./scripts/setup-claude-env.sh. On a fresh Debian/Ubuntu container it installs build tooling and the Rust stable toolchain (plus nightly rustfmt and clippy for the CI gates), fetches dependencies, and warms the build with cargo build --all-targets. Pure Rust: no native libraries, submodules, or secrets needed. Idempotent and safe to re-run.

🤖 Generated with Claude Code

scripts/setup-claude-env.sh provisions a fresh Linux dev container for a
Claude Code cloud environment: it installs the toolchain and system
dependencies, installs project dependencies, and warms the build cache.
The script is idempotent and safe to re-run.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@attune-tuna

attune-tuna Bot commented Jun 23, 2026

Copy link
Copy Markdown
Contributor

Reviewed PR #64. I didn’t find any material correctness, security, data-loss, migration, or test coverage issues.

The setup script is straightforward, scoped to the intended Debian/Ubuntu Claude Code environment, and the syntax checks out.

@attune-tuna

attune-tuna Bot commented Jun 23, 2026

Copy link
Copy Markdown
Contributor

Correction to my earlier review: the delayed sandbox pass found one material issue I agree with.

  • Medium — scripts/setup-claude-env.sh:42: the install guard checks only cargo, then unconditionally sources $HOME/.cargo/env and later uses rustup. If the environment already has Cargo installed outside rustup, e.g. apt/prebuilt image, $HOME/.cargo/env may not exist and rustup may be unavailable, so the script exits despite being advertised as idempotent. The guard should check/install rustup or only source the env file when it exists.

@jssblck jssblck merged commit eb3c502 into main Jun 23, 2026
14 checks passed
@jssblck jssblck deleted the claude/setup-env branch June 23, 2026 18:35
@jssblck

jssblck commented Jun 23, 2026

Copy link
Copy Markdown
Member Author

@attune-tuna can you make a a follow up pr to fix this? i merged based on your prior review.

also, please in the future update your review process to wait for async results before posting your comment

@attune-tuna

attune-tuna Bot commented Jun 23, 2026

Copy link
Copy Markdown
Contributor

You’re right — that was my mistake. I’ve updated my durable review process note to wait for async sandbox results before posting final review comments.

I’ll make the follow-up PR now to fix the rustup/cargo guard.

@attune-tuna

attune-tuna Bot commented Jun 23, 2026

Copy link
Copy Markdown
Contributor

Sorry again — I should have waited.

Follow-up PR is up: #65

I also added a durable note to my review process: when I delegate review work asynchronously, I won’t post the final review until the sandbox result is complete/failed/stopped and checked.

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.

1 participant