agent-harness-settings-parity

Topics in the source

• Agent harness settings parity
• When to use
• Procedure
• Restart policy
• Pitfalls
• References

An operator runs several coding harnesses on the same machine (for example omp/oh-my-pi, pi, codex, opencode, dsh) and expects a policy — model, thinking effort, compaction threshold — to hold on ALL of them. Each harness has its own config file, its own knob name, and its own unit for the same concept. Treat this as a repeatable audit-and-apply task, never as one edit. "给所有 harness 配上 X" / "check whether every harness still has X" / "apply this on all machines". Any policy that must hold across several harnesses at once: model, thinking effort, compaction threshold, approval mode, telemetry. Before claiming a setting is already in place anywhere — the audit half is the point. 1. Inventory what is installed before touching anything. command -v for each CLI, then locate the real binary (version-manager installs and npm globals are usually NOT on PATH). Record each config root. 2. Find each harness's own knob from its own docs or CLI. Never map one harness's key name onto another: the same concept is thresholdPercent (omp), buffer (opencode), reserveTokens (pi), modelpostturncompactthresholdpercent (codex), thresholdRatio (dsh), compression.threshold (the gateway harness). 3. Read th

This is an excerpt. Refer to the complete source and its current requirements.