Provide a migration path for existing agents during local harness migration
Open
- Dominant language
- TypeScript
- Stars
- 193k
- Forks
- 42.4k
- PR merge metrics
- PR metrics pending
Description
Since we are moving from the local harness to the copilot harness, the `tools` definitions in front matter of agent.md files supposedly is not the future. We should educate the user properly that these are no longer valid, if that's the case, or provide them with the right tools to update their agent.md files to work with the new harness.
Contributor guide
Assessment
This issue has not been assessed yet.