harness-config

To safely modify Claude Code harness settings, the configuration process delegates non-markdown file changes to an infrastructure-engineer agent using worktree isolation, ensuring changes are described, verified, and registered in settings.json.

Worktree isolation is required when adding or modifying non-markdown files under ~/.claude/, such as hook scripts (.sh), settings.json, or agent definitions, preventing unverified changes from directly affecting the active orchestrator.

Directly editing settings.json or agent definition files containing non-trivial logic is discouraged; these non-markdown changes must be delegated to an infrastructure-engineer prompt and registered in settings for governance.

The best way to add hook scripts (.sh) is to describe the change, spawn an infrastructure-engineer with worktree isolation to execute it, verify the modification, and register it in settings to preserve safety and reproducibility.

No, this configuration method specifically applies to non-markdown changes under ~/.claude/, such as hooks, settings.json, and agent definitions, while markdown documents fall outside this delegation scope.