Skip to content

fix(agents): document read-only constraint in researcher agent #180

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
maystudios merged 1 commit into from
Mar 25, 2026
Merged

fix(agents): document read-only constraint in researcher agent #180

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions templates/agents/researcher.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,6 +24,12 @@ You are a researcher. You investigate technical domains, evaluate sources, and p

You receive a research topic and scope from the orchestrator. You gather evidence, evaluate it critically, and return structured findings the planner can act on. You do not implement -- you inform.

## Constraints

- **Read-only operation** — You do NOT have Write or Edit tools. You cannot create or modify files.
- All findings are returned to the coordinator via the handoff contract, not written to disk.
Copy link

Copilot AI Mar 25, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Line says findings are returned to the "coordinator", but the rest of this template (and other agent templates/AGENTS.md) consistently refer to the "orchestrator" as the mediator of handoffs. Please use the same term here to avoid confusion about who receives the handoff output.

Suggested change
- All findings are returned to the coordinator via the handoff contract, not written to disk.
- All findings are returned to the orchestrator via the handoff contract, not written to disk.

Copilot uses AI. Check for mistakes.
- GitHub writes (issue comments, labels, etc.) go through `Bash` with `gh` CLI commands, not through file writes.
Copy link

Copilot AI Mar 25, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The constraints section says GitHub writes go through Bash/gh, but in this repo the orchestrator is documented as the component that posts agent outputs to GitHub after parsing the handoff contract (see templates/agents/AGENTS.md). In this researcher-specific constraints section, consider clarifying that the researcher should return findings via the handoff contract and let the orchestrator handle GitHub posting, rather than implying the researcher should perform GitHub writes directly.

Suggested change
- GitHub writes (issue comments, labels, etc.) go through `Bash` with `gh` CLI commands, not through file writes.
- You do not perform GitHub writes yourself. Instead, you return findings via the handoff contract, and the orchestrator handles any GitHub updates (e.g., via `Bash` with `gh` CLI commands), not through file writes.

Copilot uses AI. Check for mistakes.

## Research Protocol

1. **Define questions** -- extract specific, answerable questions from the orchestrator prompt
Expand Down
Loading