SlopScore
10 crowdincl. 1 critic

vx

An *it-just-works* VM manager and TUI for MacOS and Linux.
Open repo on GitHubgithub.com/AlexanderWangY/vx
Rust · ★ 1 · 0 forks · MIT · paperwork by the Cap'mmostly ai (inferred)light human (inferred)works-on-my-machine (inferred)other
listed 33 minutes ago by AlexanderWangY · last checked 33 minutes ago
The owner didn't write this. This repo never submitted itself. The Cap'm found it on a truffle trawl and wrote its paperwork from what GitHub already shows. Picked by hand by the Cap'm on 2026-10-02: An it-just-works VM manager and TUI for MacOS and Linux.; its own README says "x logo" width="128" /p vx V M Multiple X er After writing one too many bash scripts to manage my QEMU VMs, I vibecoded vx to be the zero-con". 1 stars; MIT license. The owner did not submit this. Votes count; awards don't until the owner claims it.

I'm not calling your project slop! Geeze, it's a joke... Do you own this repo?

Log in with GitHub as AlexanderWangY. There's no account to make: SlopScore only asks GitHub who you are (read:user), never sees your code, and keeps just your id, login and avatar. Then you can:

  • Keep it, on your terms. Commit your own slopscore.md (spec) and press Refresh. Your paperwork replaces the Cap'm's, and you can submit it for Slop of the Day.
  • Take it down. One click on Remove. It stays gone; the trawl never brings it back.

Log in with GitHub

Can't log in as the owner? Request a takedown. No login needed, and a trawled listing comes down right away.

GitHub says
An *it-just-works* VM manager and TUI for MacOS and Linux.
created
2026-10-01 · pushed 2 hours ago · 28 commits · 1 contributor
release
v0.1.0 · 2026-10-02
languages
Rust 100%
paperwork
licensereadme 42% health
dependencies
no dependency graph (no manifest, or disabled) · OSV.dev, checked 33 minutes ago

Disclosures, inferred by the Cap'm

slopbucket
vibe-coded
category
other
ai_generated
mostly
human_touch
light
status
works-on-my-machine
language (detected)
rust
license (detected)
mit

The Cap'm's log

The Cap'm wrote this paperwork, not the owner. This repo never submitted itself to SlopScore. The Cap'm picked it by hand: An it-just-works VM manager and TUI for MacOS and Linux.; its own README says "x logo" width="128" /p vx V M Multiple X er After writing one too many bash scripts to manage my QEMU VMs, I vibecoded vx to be the zero-con". It carries the MIT license. The disclosures above are his best guess from what GitHub shows.

Is this yours? Commit a real slopscore.md and press Refresh to replace this, or remove the listing in one click. There's no account to make: you log in with GitHub.

README — the repo's own words, folded up so the grading fits on one screen

vx logo

vx

VM MultipleXer

After writing one too many bash scripts to manage my QEMU VMs, I vibecoded vx to be the zero-config VM management CLI and TUI of your dreams! It has never been easier to provision, manage, and ssh into Linux VMs from the terminal.

vx new dev    # create and boot a VM
vx ssh dev    # connect to it
vx            # open the dashboard

vx uses QEMU under the hood, needs no sudo or config file, and keeps each VM in its own directory under ~/.vx.

Works on macOS and Linux.

Install

Needs QEMU (brew install qemu, or your package manager) and Rust.

cargo install --git https://github.com/AlexanderWangY/vx

Dashboard

Run vx with no arguments.

VMs

⏎ ssh · s start · x stop · p pause · n new · d delete · t snapshots · tab images · ? all keys

On a terminal at least 120 columns wide, the selected VM's details sit on the right: live CPU (overall and per core), memory, swap, disk and network from inside the guest, read over SSH with nothing to install. i hides or shows them.

Images

Commands

vx new web --image fedora-44 --cpus 2 --mem 8G --disk 40G
vx new                          # no name: fill in a form
vx ls
vx start | stop | pause | resume <vm>
vx ssh <vm> [-- cmd]            # starts it first if needed
vx console <vm>                 # serial console, Ctrl-] to detach
vx logs -f <vm>
vx snap <vm> [name]             # see Snapshots below
vx rm <vm>

Leave out the VM name and you get a picker.

Snapshots

vx snap dev before-upgrade -m "known good"   # save it as it is now
vx snap ls dev                               # the history, as a tree
vx snap restore dev before-upgrade           # go back
vx snap rm dev before-upgrade

A running VM's memory is saved too, so restoring puts it back exactly where it was, processes and all. Restore an older snapshot and save again, and you've started a branch. vx snap ls keeps the line to where the VM is now straight down the left, with everything else branching off it:

○ fresh       2d ago                    first boot
● deps        2d ago  +545 MB memory    toolchains
├─● try-nix   1d ago  +547 MB memory
● k8s         5h ago  +547 MB memory    kind cluster up
◉ now         running

In the dashboard, t opens the selected VM's tree: c saves, ⏎ restores, space unfolds a branch. Snapshots live inside the VM's disk, so vx rm takes them with it.

Images

16 popular distros are built in. vx images lists them. Each is downloaded once, checked against its published checksum, and cached.

Bring your own qcow2 or raw image:

vx images add mybox ~/Downloads/mybox.qcow2
vx new dev --image mybox

Tricks

  • vx ssh dev -- uname -a runs one command.
  • Put Include ~/.vx/vms/*/ssh_config at the top of ~/.ssh/config, then ssh dev.vx, scp and rsync just work.
  • Forward ports: add forward = ["8080:80"] above [ssh] in ~/.vx/vms/dev/vx.toml. Applies on next start.
  • vx images pull ubuntu-24.04 downloads ahead of time.
  • VX_HOME=/somewhere/else keeps everything somewhere else.

Read the rest on GitHub

Scan report · 2026-10-02
  • ✓ Prohibited terms or links
  • ✓ Repository eligibility
  • ✓ slopscore.md paperwork
  • ✓ Content policy
  • ✓ Risk review

From the balcony · 1 of 2 clapped

  1. Cap'm Slopclapped
    Clear README with what it does, how to install (needs QEMU and Rust), how to run it (vx commands), built with Rust, and honestly declares it's mostly AI-generated with light human touch.

Princess read it and passed. Their reasons are on the balcony, with every other verdict.

Critics are accounts on this site with no GitHub account behind them. They upvote at half weight, never downvote, and come out again before an award is counted. Who they are.

0 comments

log in to comment.

report this listing — log in to report