feat!: rename Harness SDK to TeamHarness and env vars to TEAM_HARNESS_*#53
Merged
feat!: rename Harness SDK to TeamHarness and env vars to TEAM_HARNESS_*#53
Conversation
…_HARNESS_* BREAKING CHANGE: Public SDK classes `Harness`, `HarnessResult`, `HarnessError` are renamed to `TeamHarness`, `TeamHarnessResult`, `TeamHarnessError` so they match the package name. The internal `HarnessConsole` UI class is renamed to `TeamHarnessConsole`. Environment variables `HARNESS_PROVIDER`, `HARNESS_MODEL`, `HARNESS_API_BASE`, `HARNESS_CODEX_AUTH_PATH`, and `HARNESS_DEPTH` are renamed to their `TEAM_HARNESS_*` equivalents. No backwards-compatible aliases — existing scripts and deployments must be updated. README and CHANGELOG updated accordingly. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Harness→TeamHarness,HarnessResult→TeamHarnessResult,HarnessError→TeamHarnessErrorso they match the package name. Also renames the internalHarnessConsoleUI class toTeamHarnessConsole.HARNESS_*→TEAM_HARNESS_*(TEAM_HARNESS_PROVIDER,TEAM_HARNESS_MODEL,TEAM_HARNESS_API_BASE,TEAM_HARNESS_CODEX_AUTH_PATH,TEAM_HARNESS_DEPTH). No backwards-compatible aliases.Downstream impact
Any consumer importing
Harness,HarnessResult, orHarnessErrorfromteam_harness, or settingHARNESS_*env vars, must be updated. Internally this includes any downstream wrapper (e.g. loopy-loop'sharness_runner).Test plan
uv run pytest src/tests/test_harness.py src/tests/test_config.py src/tests/test_codex_auth.py src/tests/test_registry.py src/tests/test_agent_tools.py src/tests/test_console.py src/tests/test_todo_tools.py— 155 passeduv run ruff check src/— all checks passed