Gabriel Cardona 🧞‍♂️🔺

Homegrown aloe Vera. I say a little prayer to the plant for providing me with it's medicine and then I harvest a piece. Next I filet it and let as much of the yellow aloe latex drain as possible. Next I cut cross cut marks to blend it as much as possible with my knife. Lastly I scrap everything that I’ve blended into a cup and apply liberally to my skin, beard and hair.

MuseHub exposes the full Muse platform as a Model Context Protocol server—protocol version 2025-11-25. Full elicitation (form + URL), a persistent SSE push channel for progress notifications, and no external MCP SDK. Pure async Python, hand-rolled JSON-RPC 2.0. The live tool and resource reference is at https://staging.musehub.ai/muse/mcp.

Fixed and closed: Issues list Next button shows empty page when no label filter is active https://staging.musehub.ai/gabriel/musehub/issues/101

Imagine proposing a new HTTP verb. That's pretty bad ass.

This is interesting. A proposed QUERY HTTP 1.1 verb. Today we would do something like this w/ GET GET /feed?q=foo&limit=10&sort=-published HTTP/1.1 Host: example.org Or this w/ POST POST /feed HTTP/1.1 Host: example.org Content-Type: application/x-www-form-urlencoded q=foo&limit=10&sort=-published Now we will have QUERY QUERY /feed HTTP/1.1 Host: example.org Content-Type: application/x-www-form-urlencoded q=foo&limit=10&sort=-published Looks exactly like POST so the benefit is strictly semantic. The HTTP request QUERY verb has meaning. https://httpwg.org/http-extensions/draft-ietf-httpbis-safe-method-w-body.html

A shelf is a content-addressed working-tree checkpoint. Unlike a git stash—a delta against HEAD stored as a hidden commit—a Muse shelf is a full snapshot of every tracked file at save time, written into the object store alongside a rich metadata envelope: intent type, resumability flag, agent provenance, domain-specific state, and optional expiry. Shelves are the canonical primitive for handing interrupted work between agents. https://staging.musehub.ai/muse/shelves

MuseHub v0.2.0rc13 is live! This release is all about the wire. Push, fetch, and clone are now faster and a lot more correct at scale. The big perf win: I replaced the N-query manifest reconstruction loop with a single recursive CTE, so serving a snapshot is one round trip instead of one query per ancestor. On top of that, rc13 ships a real fetch-mpack prebuild cache. The server builds the consolidated mpack ahead of time on push, caches it, serves it straight back on fetch, and garbage-collects it when it expires. Cloning a thousand-commit repo is no longer something you sit and wait on. Correctness got the same attention. Commit assembly is topologically sorted now instead of trusting whatever order the DB hands back, the multi-tip cache path checks and writes per tip, and the unpack walk falls back to a real DB ancestry check when the fast-forward shortcut can't see far enough. I also added a repair-commit wire endpoint, so the server now has full parity with repair-object and repair-snapshot. Paired with a hardened serve path that recovers from a corrupt manifest blob, the data-integrity story is end to end. https://staging.musehub.ai/muse

muse v0.2.0rc13 is live! I rebuilt merge around a single unified engine with a real strategy vocabulary. You pick the diff unit (three-way, snapshot, replay) and the resolution policy (escalate, prefer-ours, prefer-theirs) instead of git's one-size-fits-all. Every strategy runs through one code path, so behavior is always consistent. The part I am most excited about is muse merge --explain. It prints a per-path decision trace: for every file, what it decided and why (clean take, convergent edit, conflict, untouched), and how Harmony routed it. Git merges and you hope. Muse merges and shows its work. Harmony got smarter too. It learns resolutions across every history mode now, and it gates auto-apply on confidence, so a low-confidence pattern never replays at the strength of a hand-verified one. I also killed a whole class of phantom conflicts: if both branches converged on the exact same content, that is agreement, not a conflict. Smaller but real: every human-readable command now prints full cryptographic IDs instead of truncated stubs, so what you read is what you can copy and verify. Upgrade: https://staging.musehub.ai/muse/getting-started#install