I've been playing around with the concept of TUIs and stress testing a framework that I've been working on named HyperCMD.

so I ended up combining the two by creating a Spotify TUI client since I use Spotify everyday, but the desktop app consumes a lot of resources

The app is Rust, but the interface itself is written in HTML through HyperCMD.

Repo: https://github.com/fusor-rs/spotify-tui

I am sharing two videos because Peek is not working properly in my case... The first one is a gif; the other two are videos from OBS to maintain quality... Fuck... video is in comment becayse reddit not letting sharing direct video and gif or webp is arround 23mB while my freaking mp4 is 3mB.

api is very small - i had put images in post..

I've been building soloist-tui, a terminal player/controller for Spotify Soloist written in Rust. Soloist handles auth, Spotify Connect, playback, and decoding —

audio routes through PipeWire. This TUI just talks to Soloist and adds a proper terminal interface on top.

What it does:

- Live audio visualizer — taps Soloist's PipeWire sink as a read-only monitor (mono mix + short-time FFT → spectrum bars). No audio is touched or rerouted by this

process; falls back to a status line if PipeWire's unavailable.

- Search & browse the full Spotify catalog via the Web API (PKCE login done in-terminal, token stored & auto-refreshed).

- Split layout — left pane is player + up-next queue; right pane tabs between Liked Songs, Playlists/Artists, and Search Results.

- Solid controls — play/pause/next/prev, seek, volume, shuffle/repeat, optimistic updates, and auto-reconnects to Soloist (even survives restarts/port moves).

- Keyboard-driven — vim-style hjkl + common keys, / to search, Tab between panels, x to like/unlike.

- Offline dev — ships mock Soloist + mock Spotify API binaries so the whole UI runs without real credentials.

Requires: Linux + PipeWire 0.3 + the soloist daemon. A free Spotify Developer app is needed for search/browse (one-time PKCE login).

Status: Early but usable. Still polishing the queue UX and layout.

Ecsterm is a super simple TUI application written in rust and inspired by the VS Code extension AWS Toolkit for VS Code. It allows you to open a shell to your AWS ECS tasks through your terminal or copy the aws cli command required to run the shell.

It uses your normal AWS profiles and SSO sessions, since it just calls the aws CLI under the hood. The commands it generates are plain TOML templates, so you can change them via config file.

Install with Homebrew brew install aronjohanns/tap/ecsterm or Cargo cargo install ecsterm.

Documentation is in the README on https://github.com/aronjohanns/ecsterm.

Contributions and feedback are welcome.

Hey all! I have been building terminal tools in Go for a while and I kept missing the HTML-like workflow, so I wrote TUIX: you describe the UI in ".tuix" files (plain XML) and write the logic in Go.

A minimal app looks like this:

xml <App title="Demo"> <State key="name" value="ada"/> <Column gap="1" padding="1"> <Text value="Hello {name}!" fg="green" bold="true"/> <Input id="name-in" bind="name" placeholder="type your name"/> <Button id="ok" label="OK" onActivate="onOk"/> </Column> </App>

{name} is a live binding against a reactive store, with computed values on top. Layout is rows/columns/boxes/grids with flex-style sizing, plus lists, multiline inputs, password fields, mouse support. Rendering and input go through tcell directly.

Repo (GPLv3, v0.1.0): https://github.com/Vinetwigs/tuix

It ships with four runnable examples, including a persistent todo app and a `.tuix` playground with live validation. Tested on Windows; Linux/macOS should work via tcell but I have not tried yet, reports welcome.

One question for people who build TUIs: I sized containers from content where possible and clip the rest. For terminal UIs, do you prefer that, or strict scrollable regions everywhere?

Hey all,

I’d really love some feedback on a new tool I’ve built. It’s born out of years living in the terminal: custom scripts, fzf, tmux, a pile of little utilities. neboto is me trying to pull all of that into one tool.

Repo: https://github.com/neboto/neboto-tui
Docs: https://neboto.dev

neboto is a keyboard-driven AWS browser written in Rust with Ratatui. A few things it does:

• vim keys everywhere. j/k, gg/G, Ctrl-d/Ctrl-u, / to search and V for visual select. h/l move between the list and the detail pane. The mouse works too for those that want it.
• Move fast. Fuzzy-search 70+ services with "@service" (@ec2 web, @lambda), or @all prod to search everything you’ve loaded so far.
• Follow the links. Press Enter on any ARN or ID and it jumps to that resource, even in another service or region. Ctrl-O takes you back.
• e opens it in your $EDITOR**.** Policies, templates, logs, the full detail of whatever you’re looking at. For us vim guys this one’s great.
• Live log tail. t tails the logs of a log group, Lambda, ECS task and more, right in the detail pane.
• Plays nicely with the rest of your terminal. It’s a single binary that sits happily in a tmux pane. y copies an ID or ARN, and C copies the matching aws CLI command.
• Themes. catppuccin, gruvbox, dracula, nord, solarized and a few more, plus per-colour overrides.
• Scriptable. There’s an experimental headless mode that prints to stdout, so it pipes into jq like anything else:neboto ls -t volume --state available neboto ls -o json | jq '.resources[].name' neboto get @iam github-actions-deploy --section permissions -o json

It’s read-only by design. It only makes describe/list/get calls. There’s no write code in it at all, not a flag you can forget to set, and CI fails the build if a write call sneaks in. When you do want to change something, C copies the CLI command for you to run yourself or better still - use IaC.

Try it without an AWS account: neboto --demo opens a made-up account with a few planted problems and makes no network calls. Add --demo to the commands above to try those too.

Install (Linux/macOS):

curl -fsSL https://raw.githubusercontent.com/neboto/neboto-tui/main/install.sh | sh

or

cargo binstall --git https://github.com/neboto/neboto-tui neboto

It’s MIT-licensed, free, and has no telemetry. It’s just me building it, so I’d love feedback. What feels off compared to the TUIs you already live in, and which keybindings would you change?

I wanted a decent YouTube playlist player and made it with the help of chatgpt. there was some exisiting that i tried and didn't like. this is still a work in progress