Support for multiple agents (i.e. coding agent and reviewer agent)

Open
#198 1 comment 1 reaction 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
github, go

Research direction

The issue asks for an optional agent name in PR comments, such as @agent:<binding-name>, with the current behaviour kept when the name is missing. The payload names no files or tests, so first find where PR comments are parsed for agent mentions and how agent bindings are resolved. Done means a named comment routes to the right binding, an unnamed comment behaves as before, and the syntax is settled in the thread first.

Written by the indexing model from the issue text.

Description

Currently a PR comment cannot say which one it means.
It would be good to parse an optional name.
Maybe something like @agent:<binding-name> or @agent[<name>] and then fall back to the current behaviour when it is missing.

Dominant language
Go
Stars
421
Forks
50
Avg merge
17h 34m
Merged PRs (30d)
80

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Windshiftapp/core

All issues in Windshiftapp/core

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.