5 pages for node_env.
Titles and paths first, then pages whose text carries it. Each row opens that page as this site last read it.
Configure cloud environments
Claude Code CLI · in the page
cloud-environments
…The following example defines three variables. ```text theme={null} NODE_ENV=development LOG_LEVEL=debug DATABASE_URL=postgres://localhost:5432/myapp ``` A session reads the environment's values in…
Desktop application
Claude Code CLI · in the page
desktop
…ct | Additional environment variables as key-value pairs, such as `{ "NODE_ENV": "development" }`. Don't put secrets here since this file is committed to your repo. For secrets, see [Set environment v…
Hooks reference
Claude Code CLI · in the page
hooks
…{null} #!/bin/bash if [ -n "$CLAUDE_ENV_FILE" ]; then echo 'export NODE_ENV=production' >> "$CLAUDE_ENV_FILE" echo 'export DEBUG_LOG=true' >> "$CLAUDE_ENV_FILE" echo 'export PATH="$PATH:./node_…
Configure permissions
Claude Code CLI · in the page
permissions
…tain known-safe environment variables, so `Bash(npm test *)` matches `NODE_ENV=test npm test`. An allow rule won't match past an assignment of any other variable. A deny or ask rule matches past any l…
SSH remote sessions in Claude Desktop on 3P
Claude Documentation · in the page
third-party/claude-desktop/ssh-remote-sessions
…re one of a few fixed logging and runtime names, such as `DEBUG` and `NODE_ENV`. A secret in an argument or in an `MCP_` variable reaches the host. On a Linux or macOS host, Claude Desktop leaves out…