--ikwid currently appends --dangerously-skip-permissions for claude. In recent Claude Code versions the flag's interactive acceptance screen stopped persisting in containerized setups, so it can silently fall back to prompting — and it doesn't cover launches the flag never reaches (e.g. a user running claude --resume inside the container).
In my claude-container fork I switched to merging this into the mounted config dir's settings.json (preserving existing keys):
{ "permissions": { "defaultMode": "bypassPermissions" } }This applies to every claude launch in the container and needs no acceptance screen. For VibePod this could be what IKWID does for the claude agent (written into the per-agent config volume before start), instead of or in addition to the flag.
Reference: fughilli/claude-container@1bfc5d4 (flag approach, kept for context), superseded by the settings merge in fughilli/claude-container@b8925b6.
--ikwidcurrently appends--dangerously-skip-permissionsfor claude. In recent Claude Code versions the flag's interactive acceptance screen stopped persisting in containerized setups, so it can silently fall back to prompting — and it doesn't cover launches the flag never reaches (e.g. a user runningclaude --resumeinside the container).In my claude-container fork I switched to merging this into the mounted config dir's
settings.json(preserving existing keys):{ "permissions": { "defaultMode": "bypassPermissions" } }This applies to every claude launch in the container and needs no acceptance screen. For VibePod this could be what IKWID does for the claude agent (written into the per-agent config volume before start), instead of or in addition to the flag.
Reference: fughilli/claude-container@1bfc5d4 (flag approach, kept for context), superseded by the settings merge in fughilli/claude-container@b8925b6.