Josh Knapp d56c6e3845 fix: validate AWS SSO session before launching Claude for Bedrock Profile auth ...

When using AWS Profile auth (SSO) with Bedrock, expired SSO sessions
caused Claude Code to spin indefinitely. Three root causes fixed:

1. Mount host .aws at /tmp/.host-aws (read-only) and copy to
   /home/claude/.aws in entrypoint, mirroring the SSH key pattern.
   This gives AWS CLI writable sso/cache and cli/cache directories.

2. For Bedrock Profile projects, wrap the claude command in a bash
   script that validates credentials via `aws sts get-caller-identity`
   before launch. If SSO session is expired, runs `aws sso login`
   with the auth URL visible and clickable in the terminal.

3. Non-SSO profiles with bad creds get a warning but Claude still
   starts. Non-Bedrock projects are unaffected.

Note: existing containers need a rebuild to pick up the new mount path.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

2026-03-04 11:41:42 -08:00

..

Dockerfile

Trigger multi-arch container build for ARM64 support

2026-03-01 17:31:13 -08:00

entrypoint.sh

fix: validate AWS SSO session before launching Claude for Bedrock Profile auth

2026-03-04 11:41:42 -08:00

triple-c-scheduler

Add container-native scheduled task system with timezone support

2026-03-01 15:57:22 +00:00

triple-c-task-runner

Add container-native scheduled task system with timezone support

2026-03-01 15:57:22 +00:00