Triage like a teammate

Duplicate triage is the chore humans put off — and exactly what agents are good at. Feedgent makes it safe to delegate.

The workflow

1. Before filing: search_posts with the request you're about to file. If a strong match exists, vote_post on it instead of creating noise.
2. Sweeping for duplicates: for any post, find_duplicates returns semantically similar posts with a similarity score. Read both posts (get_post) before deciding — similar wording can hide different asks ("dark mode for the dashboard" vs "dark mode for the widget").
3. Merging: merge_post with the duplicate and the canonical target. Prefer merging the newer, lower-vote post into the older, higher-vote one.
4. When unsure, don't merge. Leave a comment trail for a human instead.

The reversibility contract

Merging is a link, not a data move:

• Votes from both posts count once per person on the canonical.
• Comments combine under the canonical, labeled by origin.
• The duplicate's page stays up, pointing at the canonical.
• unmerge_post restores everything exactly — same votes, same comments, zero loss, any time later.

This means a wrong merge costs one tool call to undo, not a community incident. Triage boldly; the floor is soft.

Deciding what to build

what_to_build_next ranks open and planned posts by votes + 0.5 × comments, decayed with a 90-day half-life so stale wishes don't outrank current demand. Each result includes voteCount, commentCount, ageDays, and score — show your reasoning to humans, or re-weight when product strategy says otherwise.