Document agents that don't fully integrate into gym
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.2k
- Forks
- 349
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 324
Description
broader comment on agents that don't fully integrate into gym, like this one: should agents declare whether they support resource server tools? It looks like in the current implementation, this agent server won't work with any Gym benchmarks that require using resource server tools.
https://github.com/NVIDIA-NeMo/Gym/tree/main/responses_api_agents/hermes_agent#resources-server-compatibility here's a good precedent. I will document like this in my README.
Originally posted by @hwolff99 in https://github.com/NVIDIA-NeMo/Gym/issues/2929#issuecomment-5638434922
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the README precedent at responses_api_agents/hermes_agent#resources-server-compatibility and inspect the README for the agent referenced by this issue. Document whether the agent supports resource server tools and what that means for Gym benchmarks; done when users can determine its compatibility from the README.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 74/100