Generate the two pieces Anthropic’s cloud workflow actually uses: a cached environment setup
script for tools, and a repository-owned SessionStart hook for project dependencies.
#!/usr/bin/env bash set -euo pipefail # Paste this into the cloud environment's Setup script field. # It runs as root on Ubuntu 24.04 when Anthropic rebuilds the file cache. # Keep the complete script comfortably below the roughly five-minute budget. apt-get update apt-get install -y --no-install-recommends gh jq ripgrep
#!/usr/bin/env bash
set -euo pipefail
# This repository-owned hook runs on startup and resume.
# Skip it locally; CLAUDE_CODE_REMOTE is true in Claude cloud sessions.
if [ "${CLAUDE_CODE_REMOTE:-}" != "true" ]; then
exit 0
fi
if [ -f package-lock.json ]; then
npm ci
fi
exit 0
{
"hooks": {
"SessionStart": [
{
"matcher": "startup|resume",
"hooks": [
{
"type": "command",
"command": "\"$CLAUDE_PROJECT_DIR\"/scripts/claude-cloud-session-start.sh"
}
]
}
]
}
}
Review every command. If .claude/settings.json already exists, merge the
generated hooks object—do not overwrite other project settings.
Send the workflow—not your code or credentials. We’ll reply with an honest recommendation: keep Claude Code on the web and improve the setup, or use a persistent shell because the live state actually matters.
Describe the process or session you lose when your laptop closes.
Do not include secrets, credentials, or private repository details. We only use this information to discuss the fit check. See our privacy notice.
Do not pay Terminalbox merely to avoid writing a setup script. Pay only when the state you need cannot be represented by a fresh clone plus repeatable preparation.
Add the first script to the cloud environment’s Setup script field.
Add the shell file, make it executable, and merge the generated SessionStart hook into project settings.
Open a new cloud session, confirm setup finishes, and remove any command that is slow, unnecessary, or unsafe for that repository.
Use the cloud environment setup script for tools the cloud needs but your laptop already has. Anthropic caches its filesystem output, so later fresh sessions can start with those tools already present.
Use a repository-owned SessionStart hook for project preparation that should run when a session starts or resumes, such as installing dependencies from a committed lockfile.
No. Generation, copying, and downloading happen in your browser. Terminalbox records only bounded page-view and button-action labels, never generated scripts, repository details, environment variables, or credentials.
No. Do not commit secrets or embed them in setup commands. Configure environment variables through the provider’s environment controls and follow your organization’s credential policy.
Use a persistent terminal when the valuable state is a running process, interactive shell, database, tmux session, non-GitHub workflow, or frequent steering across devices—not merely files that can be rebuilt from a repository.