Purpose
Launch an interactive Codex session that personalizes an initialized Harness repository.
Usage
harness configure [options]
Options
--provider codex: explicit provider selection. codex is the only supported value.--help: show the command help text.
Requirements
- Run inside a valid Harness scaffold.
- Have the local
codex executable available on PATH.
What Codex Should Do
The seed prompt asks Codex to:
- read the repository docs before editing;
- read
CHANGELOG.md as part of the scaffold;
- interview the user about project direction and technical choices;
- personalize the existing markdown guidance instead of implementing source code;
- define local validation and observability workflows;
- keep the repository self-sufficient for future autonomous agent work;
- enforce the validation-subagent rule for non-trivial implementation.
It also explicitly tells Codex not to create ExecPlans, feature product specs, or source files during configure, and not to edit changelogs or version numbers without explicit user approval.
Validation-Subagent Rule
Configured repositories must require:
- a separate validation subagent after implementation;
- a validation prompt that is different from the implementation prompt;
- review of correctness and regressions first;
- test execution second;
- repetition or style and organization improvements third;
- iteration on findings until the validation pass reports no material issues;
- no move to completed status until that review loop is closed.