new hasTrustDialogHooksAccepted option can't be set via `claude config set`

[nadzinski]

We run Claude Code within github codespaces. Every time a new codespace is created, the user has to accept all the onboarding and trust dialogs again, even though they've used Claude Code on the repo before.

Since this is annoying to do each time, we've added a codespace startup script to auto-accept the various prompts, e.g. using claude config set hasTrustDialogAccepted true

However, recently the hasTrustDialogHooksAccepted field was added to claude.json. It's not possible to set this using claude config set, so we're seeing trust dialogs appear again every time we start a codespace.

• It would be great if you could add hasTrustDialogHooksAccepted to the options for claude config set
• In addition, the hasCompletedOnboarding global option is also not available in claude config set. It would be great if you could add that as well!

Thanks! We love using your tool here at Rover.com!

[github-actions]

Found 2 possible duplicate issues:

1. [DOC] Config params dontCrawlDirectory and hasTrustDialogAccepted not documented #720
2. [BUG] Onboarding Process Ignores Environment Settings. #4714

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

[coygeek]

Hey! It's definitely a pain to have to click through the same dialogs every time.

I was digging into this recently and I think I found the root of the problem. According to the changelog for version 1.0.7, the claude config commands were deprecated in favor of managing configuration through settings.json files.

1.0.7

• Renamed /allowed-tools -> /permissions
• Migrated allowedTools and ignorePatterns from .claude.json -> settings.json
• Deprecated claude config commands in favor of editing settings.json
• ...

The settings you're trying to modify (hasTrustDialogHooksAccepted and hasCompletedOnboarding) seem to be internal state flags stored in ~/.claude/claude.json, not user-facing configurations in settings.json, which is probably why they aren't exposed via the (now deprecated) config set command.

As a workaround, you could add a step to your codespace startup script that modifies that JSON file directly. This is a bit of a hack since you're editing an internal file, but it should get the job done. Using a tool like jq is probably the safest way to do it.

Here's a snippet you could adapt for your startup script:

# Ensure the config file exists by running a quick command
claude --version > /dev/null

# Path to the internal config file
CONFIG_FILE="$HOME/.claude/claude.json"

# Use jq to set the flags to true if the file exists
if [ -f "$CONFIG_FILE" ]; then
  echo "Pre-accepting Claude Code dialogs..."
  jq '
    .hasTrustDialogHooksAccepted = true |
    .hasCompletedOnboarding = true
  ' "$CONFIG_FILE" > "${CONFIG_FILE}.tmp" && mv "${CONFIG_FILE}.tmp" "$CONFIG_FILE"
else
  echo "Claude Code config file not found, skipping pre-acceptance."
fi

This should bypass those prompts for you on each new codespace.

That said, I totally agree with your feature request. Having a proper setting in .claude/settings.json or even a CLI flag like --accept-all-dialogs would be a much cleaner solution for automated environments.

Hope this helps you out in the meantime

[github-actions]

This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.

[github-actions]

This issue has been automatically closed due to 60 days of inactivity. If you're still experiencing this issue, please open a new issue with updated information.

[github-actions]

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.