v0.7.0 — workflows & autonomous agents 🤘

🤘 moshcode v0.7.0 — workflows & autonomous agents

New

• Workflow tools + autonomous agent launches — moshcode can now orchestrate multi-step workflows and kick off autonomous agent runs.

Fixes

• moshscript parses negative numbers correctly (#15)
• /prd quotes generated PRD titles so special chars don't break the header (#14)
• pwd respects home-path boundaries (#13)
• run accepts the equals-form --max=N option (#12)

Full changelog: v0.6.1...v0.7.0

v0.6.1 — upgrade actually updates moshcode 🤘

🎸 moshcode v0.6.1 — upgrade now really updates moshcode

moshcode upgrade / update always tried to self-update in addition to engines, but it reinstalled to the default ~/.moshcode. If your moshcode lived anywhere else, the reinstall went to a different directory and the moshcode on your PATH never changed.

Fixed:

• Targets the actual running install — the self-upgrade now points the installer at the exact dir moshcode runs from (resolved from import.meta.url), so that copy updates.
• Reports the version change — moshcode 0.6.0 → 0.6.1 — restart to load it, or already at X.
• Git-checkout safe — if you run moshcode from a git clone, it skips the destructive reinstall and tells you to git pull instead of wiping your working tree.

Engines are unchanged; self runs in addition to them on a bare moshcode upgrade.

v0.6.0 — moshcode pwd 🤘

🎸 moshcode v0.6.0 — where am I?

New read-only moshcode pwd (alias where; TUI: /pwd). Shows the current directory and, when you're inside a git repo, the repo name + branch, root, and origin:

~/src/moshcode
repo:   moshcode (main)
root:   ~/src/moshcode
origin: https://github.com/moshcoder/moshcode.git

• Zero-dependency — reads the .git dir directly instead of spawning git, so it works even without git on $PATH.
• Walks up to the nearest .git and requires a readable HEAD, so a stray/invalid .git dir (e.g. /tmp/.git) is never mistaken for a repo.
• Handles worktree/submodule .git files (gitdir: …) and detached HEAD (short sha). $HOME collapses to ~.

v0.5.0 — moshcode upgrade 🤘

🎸 moshcode v0.5.0 — one command to update everything

New moshcode upgrade (alias update; TUI: /upgrade). With no args it updates everything that has a newer version — moshcode itself + every installed engine:

moshcode upgrade            # moshcode + all installed engines
moshcode upgrade claude     # just one engine (any name/alias)
moshcode upgrade self       # just moshcode itself
moshcode upgrade engines    # all installed engines, skip self

Conductor pattern — no vendoring. Each engine is updated with its own native updater when it has one (opencode upgrade, aider --upgrade) and re-run through its idempotent installer otherwise (claude/codex/gemini → npm i -g, which fetches latest). moshcode self-updates via its install.sh update path.

• Streams each tool's own progress; prints a per-tool ✓/✗ and a final summary.
• Interactive runs hand back to the mosh pit; piped/CI exit non-zero if any upgrade failed.
• There's no plugin system yet, so "everything" = moshcode + engines today.

moshcode v0.4.0

Full Changelog: v0.3.1...v0.4.0

v0.3.1 — stay in the pit 🤘

🎸 moshcode v0.3.1 — sessions return to the mosh shell

When you launch an engine or subcommand directly and it exits, moshcode now captures the exit and drops you back into the mosh shell instead of quitting to your OS shell — one persistent pit.

Applies to the direct entry points:

• moshcode <engine> (claude · codex · gemini · aider · opencode)
• moshcode prd …
• moshcode install <engine>
• moshcode run <file.mosh>

/quit (or Ctrl-D) leaves the pit. The TUI already behaved this way internally — this closes the gap for the one-shot CLI commands.

Non-interactive is unchanged: piped / CI invocations (… | moshcode run -, scripts) still exit with the child's code and never open a TUI.

moshcode v0.3.0

What's Changed

• Reject invalid moshscript characters by @aiirvizionz in #5
• Require commas between moshscript arguments by @aiirvizionz in #6
• Validate moshcode run options by @aiirvizionz in #9
• Reject extra args for zero-arg moshscript commands by @aiirvizionz in #8

Full Changelog: v0.2.0...v0.3.0

v0.2.0 — spec command + one-line installer 🤘

🎸 moshcode v0.2.0

moshcode spec — spec-driven development, saved in your repo

A lean passthrough to OpenSpec. Agree on the requirements first, commit them, then let your coding agents build to the spec.

moshcode spec init        # writes an openspec/ folder (specs/ + changes/) to your repo
moshcode spec list        # list specs / changes
moshcode spec update      # refresh agent guidance + slash commands
moshcode spec validate    # check specs are well-formed

• In the TUI shell: /spec [init|update|list|…]
• Non-interfering by design: stdio is inherited and the exit code forwarded — moshcode never reads or touches the spec content. Conductor, not a fork.
• Prefers a globally-installed openspec; else runs via npx -y @fission-ai/openspec@latest (zero setup).

One-line installer

curl -fsSL https://moshcode.sh/install.sh | sh

Node.js 18+ only — pulls this release's tarball and drops a moshcode wrapper on your PATH. … | sh -s -- update / … | sh -s -- remove to manage it.

Full changelog: d81d7dc...v0.2.0