Configuring Claude
How config reaches a Claude session: the keys actor.sh interprets, the defaults it sets, and how to forward anything else to the claude binary.
A Claude session is a claude process. actor.sh sets a couple of defaults,
interprets one key itself, and forwards everything else to the binary as
flags. This guide covers all three.
What actor.sh sets and interprets
permission-mode = autois applied by default to every Claude session, so agents can act without prompting for each tool. Override it like any other key (below).use-subscriptionis interpreted by actor.sh, not forwarded. Whentrue, actor.sh removesANTHROPIC_API_KEYfrom the agent's environment so Claude uses your subscription login instead of an API key.- The role
promptbecomes Claude's--append-system-prompt, layering the session's identity on top of Claude's own system prompt. See Roles.
Forwarding flags to claude
Any other config key is forwarded to the claude binary as a CLI flag. A
multi-character key model becomes --model; its value follows. So setting
defaults "claude" {
config model "claude-sonnet-4-6"
}
launches Claude sessions with --model claude-sonnet-4-6. actor.sh keeps no
allow-list: any flag your installed claude accepts can be set this way.
Three places to set config
Pick the scope that fits:
-
All Claude sessions — a
defaults "claude"block insettings.kdl:defaults "claude" { use-subscription #true config permission-mode "auto" } -
A class of session — a role's
configblock, so only sessions created with that role get it. -
One session, one flag — forward a raw argument to the binary for a single session with
--arg:actor new spike --arg --model --arg claude-opus-4-8And
--use-subscriptionis a first-class flag onactor new.
Cancelling an inherited value
A more specific layer can switch off a key set by a broader one with the
#null cancel marker — see
Actor Settings. The
full precedence order is documented there too.
For a compact table of the keys, see the Config reference.