Summary
--skip-permissions (#357) is currently a per-invocation CLI flag with no config equivalent. Users who have decided their setup makes the flag safe must remember to pass it on every crosslink kickoff run. Forgetting it means the agent blocks on tool prompts and silently times out.
Proposal
Add a config key kickoff.skip_permissions (bool, default false). When true, crosslink kickoff run defaults to passing --dangerously-skip-permissions to claude. The CLI flag remains and overrides the config either direction.
The decision to skip permissions is the user's — based on their own sandbox, threat model, and risk tolerance. crosslink should not infer it from sandbox.command or any other state.
Context
Hit this in a swarm: 4 agents launched without --skip-permissions, all hit 1h timeout while blocked on permission prompts before producing committable work. A repo-level opt-in would have prevented this once configured.
Summary
--skip-permissions(#357) is currently a per-invocation CLI flag with no config equivalent. Users who have decided their setup makes the flag safe must remember to pass it on everycrosslink kickoff run. Forgetting it means the agent blocks on tool prompts and silently times out.Proposal
Add a config key
kickoff.skip_permissions(bool, default false). When true,crosslink kickoff rundefaults to passing--dangerously-skip-permissionsto claude. The CLI flag remains and overrides the config either direction.The decision to skip permissions is the user's — based on their own sandbox, threat model, and risk tolerance. crosslink should not infer it from
sandbox.commandor any other state.Context
Hit this in a swarm: 4 agents launched without
--skip-permissions, all hit 1h timeout while blocked on permission prompts before producing committable work. A repo-level opt-in would have prevented this once configured.