Compatibility

Agent Harness is currently in a soft-stable compatibility period.

Current commitments

• keep existing top-level CLI commands working unless a break is explicitly versioned
• prefer additive config evolution
• keep report and persisted artifact changes additive where possible
• preserve current high-level SDK and MCP flows

Release discipline

Before cutting a release:

1. run npm run release:check
2. update CHANGELOG.md
3. fill in the release notes template
4. state compatibility impact explicitly, even when it is none

Release operator process

The website docs summarize the policy. The repository release checklist defines the concrete versioning, verification, and tagging workflow.