How to remove empty mixtapes from view?

[diffusionnn]

In trying to install mixtapes that don't exist yet the mb mixtapes command "mb mixtapes ls" shows empty failed installation attempts without a way to remove them in the CLI.

mb % mb mixtapes ls
NAME TAG SIZE
base latest 0 B
claude-code latest 0 B
claude-code-mixtape latest 0 B
claude-code-mixtpae latest 0 B
coder latest 0 B
opencode latest 0 B
opencode-mixtape latest 4.4 GiB

How do we remove those empty failed attempts? Also, how can we check the server for what is actually available to pull with the mb pull command instead of just guessing?

I'm running masterblaster on macOS, what I was trying to do was run an autonomous agent with a starting prompt, I setup the jcard.toml with a prompt but it seems the opencode mixtape in particular will not work that way, it's simply a sandbox to manually run opencode at this point in time, right?

I'm really enjoying the idea of this, it's easy to get going but the mixtape process could be a bit smoother to manage. A little clarity in the docs could help as well. Thank you for building this! I know it's still early days but this is the most interesting repo I've seen for deploying agents like this.

[linear]

PCC-222

[jpmcb]

The mixtapes are artifact directories under ~/.config/mb/mixtapes so you should be able to just rm -rf ~/.config/mb/mixtapes/claude-code/ those directories.

Creating those directories when pulling mixtapes fails is definitely a bug - noted. We should also allow people to mb mixtapes rm a mixtape locally.

Also, how can we check the server for what is actually available to pull with the mb pull command instead of just guessing?

Related to: #24

The OCI registry is abit of a work in progress: I'm putting the final touches on getting it stood up and other mixtapes landing. The one that's there reliably right now is opencode:latest

I'll get this fixed as soon as possible! Thanks for the great feedback!!