pickfit

BrowseDeveloper CLIs

neboto

Read-only terminal UI for browsing AWS with fuzzy search, detail panes, logs and charts.

Tested on macOS and Linux

Use it

macOS arm64

You need first

  • Runtimes: recent stable Rust toolchain
  • System packages: aws CLI + session-manager-plugin
  • Keys or accounts: AWS credentials
  1. download installer script

    curl -fsSLO https://raw.githubusercontent.com/neboto/neboto-tui/main/install.sh && ls -l install.sh && wc -l install.sh
  2. install pinned version bypassing GitHub API rate limit

    NEBOTO_VERSION=v0.11.0 sh install.sh

Check that it works

neboto --version

The output should contain “neboto 0.11.0”.

Run neboto services to list the AWS services you can browse.

Linux x86_64

You need first

  • Runtimes: recent stable Rust toolchain
  • System packages: aws CLI + session-manager-plugin
  • Keys or accounts: AWS credentials
  1. download installer script for reading

    curl -fsSLO https://raw.githubusercontent.com/neboto/neboto-tui/main/install.sh
  2. run installer script into ~/.local/bin

    sh install.sh

Check that it works

neboto --version

The output should contain “neboto 0.11.0”.

First thing to try

neboto services

Run neboto services to list the AWS services you can browse.

What it does

  • Browse AWS services in a terminal UI
    How to use it
    1. Run neboto services to list services and their prefixes, such as @lambda.
    2. Run neboto ls @lambda --demo -o json to list resources for a service.
    3. Run neboto ls @ec2 --demo -o json to list EC2 resources.
    Tested
  • View console-style detail panes
    How to use it
    1. Run neboto get @lambda <resource-name> --demo -o json to see a resource's details, starting with its Overview.
    Tested
  • Tail live logs
    Not tested
  • View CloudWatch charts
    Not tested

How far pickfit got

macOS arm64

  1. Installs
  2. Starts
  3. 0 of 4 features work
  4. Works offline

Linux x86_64

  1. Installs
  2. Starts
  3. 2 of 4 features work
  4. Works offline

Good for

  • tail and search live logs for AWS resources
  • view CloudWatch charts for AWS resources
  • view change timeline merging CloudTrail and alarm history
  • run security audit over loaded resources
  • follow links across AWS resources by ARN or ID

How pickfit tested it

Each run starts from a clean machine and follows the steps above. How pickfit verifies

macOS arm64

Installs and starts

  • Replayed from scratch
  • Works offline
  • Checked on 1 Nov 2026
  • Version 0.11.0

Differences the test machine hit

  • README: curl -fsSL https://raw.githubusercontent.com/neboto/neboto-tui/main/install.sh | sh installs latest
    In the test: GitHub API returned 403 for /releases/latest (rate limit); needed NEBOTO_VERSION=v0.11.0 sh install.sh to fetch tarball directly

Linux x86_64

Its main function works

  • Replayed from scratch
  • Works offline
  • Checked on 30 Oct 2026
  • Version 0.11.0

Differences the test machine hit

  • README: installer verifies SHA-256 and signed build provenance when gh is installed
    In the test: SHA-256 verified; provenance skipped without logged-in gh; release tarball binary itself cannot be read before running

How to read a tool card

Stitching
pickfit installed this tool itself. Everything under the stitches comes from that run. A tool pickfit has not run never gets stitches.
Verified on your OS
The install steps ran on the system you chose. “Ran on Linux only” means it has not been run on yours yet.
macOS, Linux and WindowsWhere it ran
Green OS marks: pickfit ran the install steps there. Grey ones: the README says it runs there, and pickfit has not tried.
How far the run got
Installs and starts, its main function works, its service answers, it produces model output. A window means a desktop app opened; a plug, an MCP client used it. The mark sits beside the run’s result, under “Why it fits and how we know” and in “How pickfit tested it”.
Visual check
pickfit looked at screenshots of the app. Green: it looks right. Amber with a number: things that look wrong; open it to see them. Grey and dashed: not checked yet.
Known vulnerabilities
Known high or critical vulnerabilities (OSV.dev) in what it installs. Green: none known. Red with a number: how many; open it for the list, and read it before you install. Grey and dashed: not checked, which does not mean safe.
About the run
The day it ran, and the version that ran.
Source of a reason
Every reason a pick fits rests on one profile field. Open the reason to see the field and the value it relies on.
Hidden gem
High quality, little known.
Quality and popularity
Two scores out of 100. Quality: how well it installed and worked when pickfit tried it, and how good its install docs and upkeep are. Popularity: from stars, downloads and Hacker News.
Features checked
Of the main features the README advertises, how many the run actually exercised (green), and how many failed (red). Grey ones were not checked, and the card says why.
Not verified
A well-known tool Fitz mentions from general knowledge. No run record, no steps, no score.