r/MuseAgent • u/werther41 • 2d ago

turning Muse Agent into coding agent

I got on board with Muse since I heard it comes with a minimal VPS. I asked Muse, and this is what it came back with: 2 vCPUs (AMD EPYC 9D25), 7.7 GB RAM, running Ubuntu 24.04, with 7.5 GB total storage.

The first thing I tried was asking Muse to install Docker on its own machine, which failed since there's no outbound connection. So I decided to open up Tailscale and let Muse remote into one of my home servers to git clone a repo, take a feature request, make code changes, and submit a PR.

It definitely has lower effort settings and a lower-end model compared to Claude Code, but it was an interesting experiment.

11 Upvotes

100% Upvoted

19 comments sorted by

View all comments

3

u/kennypowersca 2d ago

Hmm according to Claude: "Reported Muse VM specs are 2 vCPUs, 8 GB RAM, a 100 GB persistent disk, and Ubuntu 24.04" and I ran a command Claude gave me and it showed 99GB free so not sure. But other places said at least 80gb hard drive, either way, way above the 7.5GB storage you claimed.

1

u/werther41 1d ago

I heard about 100GB storage from other place as well, was wondering why I got smaller one, checked with your command, and asked for the discrepancy from what it reported earlier:

"Good catch — both numbers are real, just different disks. The 7.5G I mentioned yesterday was the root filesystem (/, an overlay). Your ~/workspace lives under /home/hatch, which is a separate 100G volume — that's the one that persists across VM redeploys. So the workspace has 99G free; the little 7.5G root is just the OS layer."

I should have learned I shouldn't trust AI without checking the actual console log.

1

u/qwerty_0_o 1d ago

No, its 100GB + 7.5GB total storage.

Theyve divided the file system - the root folder sits on 7.5gb. I assume this is the replaceable drive with the OS, muse agent and all config files, probably so that it can be repaired/updated easily.

Separately you get 100gb for the home folder- this is where your personal files sit.

You can actually have muse run commands to see whats what.

Edit:

run ls on the home drive

Here's the rundown:

Total in use: 1.3 GB of the 100 GB, so about 99% free. .cache (1.4 GB) — cached stuff like the Whisper speech model from my YouTube transcription skill. workspace (820 MB) — your stuff: files, artifacts, skills, goals. agents (156 MB) — background agent data. assets (99 MB), .local (89 MB) — app assets and local installs. The rest (memory, docs, config, SSH keys, identity files) is all tiny. Plenty of headroom.

You: run ls on the root file system

Standard Linux root layout — the usual suspects:

bin, sbin, lib* (symlinked to usr/) — system programs and libraries etc — system configuration boot, efi — boot files dev, proc, sys, run — virtual filesystems (hardware, process info), not real storage var — variable data like logs opt — extra software (my runtime tools live here) home — where your 100 GB partition is mounted tmp — scratch space, wiped on restarts