Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for developers who want a repo-scoped agent that can plan, implement, verify, and advance work without losing project context.
Who should use it
Who should skip it
Skip open-gsd/gsd-pi if the source link, documentation, or setup requirements do not align with your current workflow or stack.
About this signal
open-gsd/gsd-pi is tracked by RepoRadar as a local coding agent in the Developer Tools section. It was first seen on 2026-06-29 and last updated on 2026-06-29. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. The standout signals for open-gsd/gsd-pi are workflow potential (10.0) and practical usefulness (9.0), while setup ease (6.4) trails — that balance shapes where it fits best. This page summarizes the evidence RepoRadar has captured from captured source metadata. The score, tier, risk label, and verdict on this page are never influenced by sponsorship, ads, or tips — they reflect only the usefulness, popularity, novelty, momentum, maturity, and evidence signals described in the RepoRadar methodology.
How this item is evaluated
RepoRadar assigned open-gsd/gsd-pi a composite score of 8.6 out of 10, placing it in the Gold tier. This score combines weighted sub-signals: usefulness (35%), novelty (18%), momentum (14%), maturity (10%), open-source/build quality (7%), evidence quality (6%), workflow potential (6%), and setup ease (4%). Popularity is tracked separately at 6.0 and never affects the composite score or tier. The risk label of 'conditional' reflects inherent user-impacting hazards, not generic novelty. Items with no risk flag may still require normal code review before production use.
Putting this into practice? Read How to vet an AI agent or MCP server before you wire it in for the checklist behind this score.
Risk explanation
It can create worktrees, execute tools, and write project guidance under .gsd, so start on a disposable repo and inspect the generated workflow files before broader rollout; The release notes mention forward-looking provider labels such as Claude Fable 5, so verify the real model mappings in your environment before standardizing on them.