fix: use BASH_ENV for non-interactive shell config loading #11

Merged

brad merged 2 commits from fix/bash-env-for-agent-config into main

2026-02-13 17:18:48 -08:00

agent commented

2026-02-13 16:25:48 -08:00

Owner

Problem

Agent environment variables from AGENTS.md were not being loaded for non-interactive shell commands (bash -c).

Root Cause

/etc/bash.bashrc has a guard that exits early for non-interactive shells:

[ -z "$PS1" ] && return

The previous fix appended config sourcing to the bottom of bash.bashrc — after this guard — so it never ran for bash -c commands.

Solution

Use BASH_ENV — the standard environment variable that bash reads for non-interactive shell scripts. This replaces the 5-line bash.bashrc hack with a single ENV directive.

Testing

Verified with the current image + env override:

# Before (fails)
docker run --rm -v ~/.openclaw/workspace:/workspace:ro \
  git.brads.house/commune/sandbox:latest \
  bash -c 'echo FORGEJO_USER=$FORGEJO_USER'
# Output: FORGEJO_USER=

# After (works)
docker run --rm -v ~/.openclaw/workspace:/workspace:ro \
  -e BASH_ENV=/etc/profile.d/agent-config.sh \
  git.brads.house/commune/sandbox:latest \
  bash -c 'echo FORGEJO_USER=$FORGEJO_USER'
# Output: FORGEJO_USER=agent

## Problem Agent environment variables from AGENTS.md were not being loaded for non-interactive shell commands (`bash -c`). ## Root Cause `/etc/bash.bashrc` has a guard that exits early for non-interactive shells: ```bash [ -z "$PS1" ] && return ``` The previous fix appended config sourcing to the *bottom* of bash.bashrc — after this guard — so it never ran for `bash -c` commands. ## Solution Use `BASH_ENV` — the standard environment variable that bash reads for non-interactive shell scripts. This replaces the 5-line bash.bashrc hack with a single `ENV` directive. ## Testing Verified with the current image + env override: ```bash # Before (fails) docker run --rm -v ~/.openclaw/workspace:/workspace:ro \ git.brads.house/commune/sandbox:latest \ bash -c 'echo FORGEJO_USER=$FORGEJO_USER' # Output: FORGEJO_USER= # After (works) docker run --rm -v ~/.openclaw/workspace:/workspace:ro \ -e BASH_ENV=/etc/profile.d/agent-config.sh \ git.brads.house/commune/sandbox:latest \ bash -c 'echo FORGEJO_USER=$FORGEJO_USER' # Output: FORGEJO_USER=agent ```

agent added 1 commit

2026-02-13 16:25:49 -08:00

fix: use BASH_ENV for non-interactive shell config loading 9b9a48871d

The previous approach appended config sourcing to /etc/bash.bashrc, but
bash.bashrc has a guard that exits early for non-interactive shells:
  [ -z "$PS1" ] && return

This meant 'bash -c' commands (like OpenClaw exec) never loaded the
agent config from AGENTS.md.

BASH_ENV is the standard way to source config for non-interactive bash
shells. This replaces the bash.bashrc hack with a single ENV directive.

brad added 1 commit

2026-02-13 17:18:41 -08:00