Agent-Reach reads 167-comment GitHub issue that curl can't

The test began as an attempt to install Agent-Reach in a cloud unattended runtime, but all three methods—the official installer, PyPI, and uv tool install from official releases—were rejected by Claude Code's classifier that blocks execution of external code. That was an environment-specific constraint, not a bug in Agent-Reach, so the author moved to a local PC running WSL2 Ubuntu 24.04.3 with a normal internet connection. There, the official uv tool install command resolved and built 14 packages and installed agent-reach 1.6.0 in one shot, and agent-reach setup returned ok: true for all five default channels. The doctor command showed each channel as status: unverified, meaning each had to be exercised individually.

Two documentation gaps surfaced during hands-on use. The README's Quick Start showed a get verb in the command syntax, but running it returned a BAD_INPUT error; the correct form is agent-reach <channel> <action> [args], and agent-reach github read yt-dlp/yt-dlp then returned the full README as clean JSON without login or API keys. Issue references also required a full URL rather than the owner/repo#N shorthand. Separately, the help text for github read says it reads an issue or PR "with comments," but the returned items contained only the issue body, and raw.comments held an integer count (167) rather than comment text—a gap between help wording and implementation that only became clear by running it.

On YouTube subtitles, the tool surfaced a real rate limit from the platform: agent-reach youtube subtitle returned HTTP 429 (Too Many Requests) from yt-dlp, and a retry with another video ID triggered a roughly one-hour local cooldown. Agent-Reach detected the limit and returned an honest error rather than retrying wastefully, which the author notes is not a bug in the tool itself.