rtv

RTV (Reddit Terminal Viewer) is a Python-based terminal UI (TUI) for browsing Reddit from the command line, including viewing submissions and expanding/collapsing comments, with optional OAuth login for authenticated actions.

Evaluated Mar 29, 2026 (23d ago)
Repo ↗ Communication command-line tui reddit python oauth terminal-ui cli
⚙ Agent Friendliness
28
/ 100
Can an agent use this?
🔒 Security
56
/ 100
Is it safe for agents?
⚡ Reliability
20
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
0
Documentation
45
Error Messages
0
Auth Simplicity
45
Rate Limits
0

🔒 Security

TLS Enforcement
80
Auth Strength
65
Scope Granularity
30
Dep. Hygiene
40
Secret Handling
60

Uses OAuth via browser for login, which is generally safer than embedding credentials, but provided documentation does not cover scopes, token storage, or secret handling. RTV also supports launching external programs (mailcap/media opening) which can increase risk if misconfigured.

⚡ Reliability

Uptime/SLA
0
Version Stability
30
Breaking Changes
20
Error Recovery
30
AF Security Reliability

Best When

You want an interactive TUI for personal browsing from a terminal (Linux/macOS-like environments) and are comfortable with local configuration and OAuth browser-based login if needed.

Avoid When

You need a service-oriented interface (REST/SDK/webhooks) or require guaranteed long-term maintenance and API stability beyond a desktop/CLI workflow.

Use Cases

  • Browse Reddit feeds and subreddits from a terminal
  • Read submission details and navigate comment trees in a TUI
  • Copy Reddit links to the system clipboard
  • Use themes and configurable UI/launch settings for a terminal-based experience
  • Optional OAuth-based login to interact with Reddit accounts

Not For

  • Building an API client for programmatic access by other services (no REST/GraphQL interface described)
  • Production automation/scheduling where a stable machine interface (API) is required
  • Use on Windows (not supported per README)

Interface

REST API
No
GraphQL
No
gRPC
No
MCP Server
No
SDK
No
Webhooks
No

Authentication

Methods: OAuth2 login via web browser (per README: press 'u' to login)
OAuth: Yes Scopes: No

Authentication is described as browser-based OAuth for logging in; no details on scopes are provided in the README content.

Pricing

Free tier: No
Requires CC: No

No pricing info in provided README; appears to be an open-source CLI.

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • No programmatic interface (REST/SDK/MCP) is described—an agent would need to drive the CLI/TUI or parse screen output, which is brittle.
  • Project indicates it is no longer maintained (repository metadata archived; README states shut down), so agent workflows may break over time.
  • OAuth login requires a web browser interaction flow, which is difficult to automate safely in headless contexts.

Alternatives

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for rtv.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

$3

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

Scores are editorial opinions as of 2026-03-29.

8642
Packages Evaluated
17761
Need Evaluation
586
Need Re-evaluation
Community Powered