Cloud Session Automator FAQs

Question 1

What is a SessionStart hook in Claude Code?

Accepted Answer

A SessionStart hook is a configuration defined in your .claude/settings.json file that triggers specific shell commands or scripts automatically whenever a Claude Code session starts in a cloud environment.

Question 2

How do I persist environment variables across a session?

Accepted Answer

To ensure environment variables are available throughout your session, you must append them to the $CLAUDE_ENV_FILE rather than using standard export commands. For example: echo "API_KEY=value" >> "$CLAUDE_ENV_FILE".

Question 3

Are databases like PostgreSQL available in the web environment?

Accepted Answer

Yes, the Claude Code web environment comes pre-installed with tools like PostgreSQL 16 and Redis 7.0, which can be configured during the session start hook.

Question 4

Can I run different setup scripts for local vs. cloud environments?

Accepted Answer

Yes, you can use the CLAUDE_CODE_REMOTE environment variable within your scripts to detect if you are running in the cloud and conditionally execute setup logic only when needed.

Question 5

What happens if my setup script takes too long to run?

Accepted Answer

By default, hooks have a 60-second timeout. If your setup requires more time, you can manually increase the 'timeout' field in your .claude/settings.json configuration.

Cloud Session Automator

About

Key Features

Use Cases

Cloud Session Automator

About

Key Features

Use Cases