Skip to content

feat: strictly block legacy agent instantiation under controller V2 build tag#47

Draft
anj-s wants to merge 1 commit into
mainfrom
u/anj/harness-registry
Draft

feat: strictly block legacy agent instantiation under controller V2 build tag#47
anj-s wants to merge 1 commit into
mainfrom
u/anj/harness-registry

Conversation

@anj-s
Copy link
Copy Markdown
Collaborator

@anj-s anj-s commented Jun 2, 2026

Summary

  • Consolidated V2 Registry validations to strictly block legacy agent (Remote/Colab) configurations under the V2 (harness build tag) controller.
  • Registered legacy agents inside V2 NewControllerFromConfig loader (cliutil_harness.go) to ensure the V2 registry can detect and throw custom validation errors when legacy agent IDs are requested.
  • Added automated test coverage in registry_test.go and controller_test.go asserting the correct and precise blockade behavior.

Type of Change

  • New feature
  • Bug fix
  • Refactor
  • Documentation
  • Breaking change

Related Issues

Closes #323

Test Plan

  • Unit tests pass (go test -tags harness ./... and go test ./... all pass cleanly with 100% success)
  • Manually verified: Ran execution ax exec --agent coding-agent --input "hello" on a harness build tag compiled binary, and verified it cleanly fails fast with agent "coding-agent" is registered under legacy agent config but has no V2 harness interface implementation.

@anj-s anj-s force-pushed the u/anj/harness-registry branch from 1e468eb to 7ca09e5 Compare June 2, 2026 20:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant