[
    "CLAUDE_CODE_USE_BEDROCK=1",
    "AWS_REGION=us-east-1",
    "AWS_BEARER_TOKEN_BEDROCK=bearerfake",
    "ANTHROPIC_MODEL=anthropic.claude-x",
    "DISABLE_PROMPT_CACHING=1",
    "ANTHROPIC_BEDROCK_SERVICE_TIER=priority",
    "NODE_EXTRA_CA_CERTS=",
    "REQUESTS_CA_BUNDLE=",
    "SSL_CERT_FILE=",
    "AWS_ACCESS_KEY_ID=",
    "AWS_SECRET_ACCESS_KEY=",
    "AWS_SESSION_TOKEN=",
    "AWS_PROFILE=",
    "AWS_SSO_AUTH_REFRESH_CMD=",
    "ANTHROPIC_BASE_URL=",
    "ANTHROPIC_AUTH_TOKEN=",
    "ANTHROPIC_DEFAULT_OPUS_MODEL=",
    "ANTHROPIC_DEFAULT_SONNET_MODEL=",
    "ANTHROPIC_DEFAULT_HAIKU_MODEL=",
    "ANTHROPIC_DEFAULT_FABLE_MODEL=",
    "CLAUDE_CODE_OAUTH_TOKEN=",
    "TRIPLE_C_CUSTOM_ENV=",
    "VPN_SUPPORT_ENABLED=0",
    "TRIPLE_C_PERMISSION_MODE=default",
    "CLAUDE_INSTRUCTIONS=## Scheduled Tasks\n\nThis container supports scheduled tasks via `triple-c-scheduler`. You can set up recurring or one-time tasks that run as separate Claude Code agents.\n\n### Commands\n- `triple-c-scheduler add --name \"NAME\" --schedule \"CRON\" --prompt \"TASK\"` — Add a recurring task\n- `triple-c-scheduler add --name \"NAME\" --at \"YYYY-MM-DD HH:MM\" --prompt \"TASK\"` — Add a one-time task\n- `triple-c-scheduler list` — List all scheduled tasks, with a running/idle status column\n- `triple-c-scheduler remove --id ID` — Remove a task\n- `triple-c-scheduler enable --id ID` / `triple-c-scheduler disable --id ID` — Toggle tasks\n- `triple-c-scheduler status [--id ID] [--watch]` — Show what is running right now, and for how long\n- `triple-c-scheduler logs [--id ID] [--tail N]` — View execution logs\n- `triple-c-scheduler run --id ID` — Manually trigger a task immediately (streams its log)\n- `triple-c-scheduler notifications [--clear]` — View or clear completion notifications\n\n### Cron format\nStandard 5-field cron: `minute hour day-of-month month day-of-week`\nExamples: `*/30 * * * *` (every 30 min), `0 9 * * 1-5` (9am weekdays), `0 */2 * * *` (every 2 hours)\n\n### One-time tasks\nUse `--at \"YYYY-MM-DD HH:MM\"` instead of `--schedule`. The task automatically removes itself after execution.\n\n### Working directory\nUse `--working-dir /workspace/project` to set where the task runs (default: /workspace).\n\n### Checking results\nWhile a task is running, `triple-c-scheduler status` reports it with elapsed time — a log that has stopped growing is normal, because `claude -p` writes its answer only at the end, so use `status` rather than log silence to tell a slow run from a dead one. After tasks run, check notifications with `triple-c-scheduler notifications` and detailed output with `triple-c-scheduler logs`.\n\n### Timezone\nScheduled times use the container's configured timezone (check with `date`). If no timezone is configured, UTC is used.\n\n## Referring to files\n\nThe user can click a file path in this terminal to open it in a viewer (while a program holds the mouse: Shift+click, or Option+click on macOS). Paths relative to the project work. When you mention a file outside the project (for example in `/tmp`, including your scratchpad directory, or under `~`), print its full absolute path, not a shortened or relative one, so it can be opened.",
    "CLAUDE_CODE_NO_FLICKER=",
    "CLAUDE_CODE_ENABLE_AWAY_SUMMARY=",
    "CLAUDE_CODE_SUBPROCESS_ENV_SCRUB=0",
    "ENABLE_PROMPT_CACHING_1H=0",
    "CLAUDE_CODE_SETTINGS_JSON={\"autoScrollEnabled\":true,\"sandbox\":{\"enabled\":false},\"showThinkingSummaries\":false}",
    "CLAUDE_CODE_SETTINGS_CLEAR=[\"awaySummaryEnabled\",\"effortLevel\",\"tui\",\"viewMode\"]",
]
