Skip to content

v0.29.2 — commands you can actually type

Choose a tag to compare

@ralyodio ralyodio released this 08 Aug 23:50
· 37 commits to main since this release
e7a2fc0

A patch release: one documentation fix, and one rendering fix.

Plugin commands are namespaced, and now say so (#331)

Every plugin command was advertised bare — /crypto, /stocks, /signals — and none of those exist. Claude Code namespaces plugin commands as /<plugin>:<command> always, not only when two plugins collide, so the first thing anyone tried after installing was:

$ /crypto BTC
Unknown command: /crypto

The real names:

plugin commands
stocks@moshcode /stocks:stocks /stocks:signals /stocks:research /stocks:lookup /stocks:reports /stocks:discover
crypto@moshcode /crypto:crypto /crypto:quote /crypto:book /crypto:bars /crypto:spark /crypto:pairs /crypto:coin

Typing / and picking from the menu inserts the right form for you.

Fixed in the catalog, both plugin READMEs, the main README, and the cross-references inside the command files themselves — those tell the model which command to offer next, so a bare name there sent you to the same dead end one step later.

Nothing inside the moshcode pit changed. There, the same research really is plain /stocks … and /crypto …, because those are moshcode's own commands rather than a plugin's. Having both spellings in one project is the genuinely confusing part, so the READMEs now call it out.

Also fixed: the invitation printed after installing appended a hardcoded NVDA to whatever came first in the command list — telling anyone who installed the crypto plugin to go try a stock. Each plugin now carries its own runnable example (/crypto:crypto BTC), and a test asserts it invokes a command that plugin actually ships.

Why it survived two releases: the drift test compared the advertised commands against bare filenames, so /crypto "matched" crypto.md and stayed green — nothing checked the name against how the file is actually invoked. It now derives the namespaced form.

A down move no longer reads as "$-186.36" (#330)

moshcode crypto <PAIR> signed the change by letting the price formatter carry the minus, which put it after the currency mark. An up move read +$186.36 and a down move read $-186.36 — the same quantity rendered two different shapes depending on direction. The sign now leads in both cases, the way the percentage already did.

Thanks to @clawedassistant26 for catching it. It has been wrong since /crypto shipped in v0.27.0.