terminal-browser
Eliminates context switching between terminal and browser for web debugging, API testing, and documentation lookup.
A real browser inside your terminal
- Ask Claude to fetch and display a live webpage directly within your terminal environment
- Generate HTML previews and screenshots of web pages without leaving your command-line interface
- Automate browser-based testing workflows by controlling page navigation and interaction from terminal scripts
Eliminates context switching between terminal and browser for web debugging, API testing, and documentation lookup. Reduces friction in developer workflows where viewing rendered output without leaving the shell saves time and mental overhead.
Backend developers and DevOps engineers debugging APIs and services without leaving terminal-based development environments.
https://github.com/zenbu-labs/terminal-browser
By zenbu-labs
How to Get It
claude plugins install zenbu-labs/terminal-browser
Tip: Paste this into a Claude Code conversation. Verify command matches your Claude Code version.
Auto-generated from the tool's public listing — not hands-on verified. Cross-check against the source repo's README before running.
After installing, paste this into Claude:
Fetch and display a live webpage directly within my terminal environment
Trust Signals Auto-scanned
Community Pulse Active
Discussed on Hacker News
- Show HN: Spegel, a Terminal Browser That Uses LLMs to Rewrite Webpages — Hacker News · 426 pts
- IMDB Terminal Browser — Hacker News · 21 pts
- Show HN: Reddittui, a Terminal Browser for Reddit — Hacker News · 13 pts
3 mentions across 1 sources
Reviewer notes
Auto-scanned review. These are observations, not a security certification.
Scored from trust signals (evidence-eval-v1): 3,934 GitHub stars; contributors unknown; last commit 0d ago; license MIT.
Things to check
- Scanned, not hands-on tested — this entry was auto-scanned from public metadata (GitHub metrics, license, security flags). No reviewer has run it, and no tool-specific limitations have been documented yet.
How to evaluate tools before deploying →
Data shown here comes from public APIs and automated scanning. Reviewer notes reflect one person's experience. This is not a security certification or legal recommendation. Always evaluate tools according to your own organization's policies.
Evaluation
Scored from trust signals (evidence-eval-v1): 3,934 GitHub stars; contributors unknown; last commit 0d ago; license MIT.