Refactor agent provider message handling
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 1.2k
- Forks
- 76
- PR merge metrics
- No merged PRs in 30d
Description
The current mechanism that turns agent provider responses into Message instances (under lib/roast/cogs/agent/providers/) is not optimal and hard to maintain long term.
It would be good to have a better way of constructing the agent cogs' message objects from provider responses.
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 by reading the provider implementations under lib/roast/cogs/agent/providers/ and trace how provider responses are currently turned into Message instances. Identify the shared construction pattern and its maintenance problems before proposing a replacement. Done means agent cogs still receive correctly constructed Message objects through a clearer, more maintainable mechanism.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- ai
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100