Entries matching “claude-code”

Greg Ceccarelli

@gregce10

For funsies, I got Claude Code running on my Muse agent’s computer tonight. Muse gives every agent a Linux VM with 2 vCPUs, ~8GB RAM, 100GB of persistent disk plus a scheduler, hosted artifacts and their permission system. The VM has no inbound ports, so I built a tiny

Composio looks at the three benchmark charts from Meta's Muse Code launch and whether developers should switch from Claude Code.

davidlee

@davidlee

Muse Glimmer powering any harness including Codex and Claude Code using @ollama

@rtravellin

@rtravellin

A Claude Code plugin that adds /muse:review, /muse:critique, /muse:delegate and /muse:transfer commands, running Muse Code reviews and delegated tasks as background jobs.

@AloreBB

@AloreBB

Port of openai/codex-plugin-cc that lets Claude Code call Muse for reviews or delegated tasks via muse exec, with /muse:review, /muse:adversarial-review and background job commands.

IchBinFabian installs Muse Code, compares Muse Spark 1.3 pricing with Claude Code and Codex, reviews the benchmarks and builds two real projects in OpenCode for a combined 82 cents.

@phareim

@phareim

musecode adds a /musecode slash command, a Haiku relay agent and a muse-run CLI so Claude Code Workflow fan-outs run their leaf tasks on the free Muse Spark 1.3 model through opencode.

@NatesVibeCode

@NatesVibeCode

Portable SKILL.md bundles for handing work to Muse, Antigravity, OpenCode, Grok Build, Cursor, Codex and Claude Code, each with supporting references.

@Solar2004

@Solar2004

A config (in Spanish) plus two helper proxies for using Muse Spark 1.2 Contributor from Claude Code and Hermes through routatic/proxy and an OpenCode Go subscription.

@ArshansGithub

@ArshansGithub

An OpenAI Responses-compatible shim that serves the Muse assistant as a stateless HTTP model backend for Claude Code via CLIProxyAPI, one model turn per request.

@Israelmusondaayliffe

@Israelmusondaayliffe

Muse workspace skills ported from a Codex/Claude Code plugin marketplace, translating manifests and hooks into procedures Muse can run with its terminal, browser and files.

@Wraient

@Wraient

A Go reverse proxy with an embedded dashboard that lets Claude Code and OpenAI/Codex clients use muse-spark models through a Muse Code subscription, authenticated with the muse login credential.

Theo (t3.gg) tests Meta's Muse Code terminal agent powered by Muse Spark 1.2 and focuses on how cheap it is compared with Claude Code.

@alexanderradahl

@alexanderradahl

A fork of Spotify's shunt plugin for Claude Code and Codex whose hooks block full reads of large files and route them to Muse Spark via muse exec; the author measured about 4,800 tokens out and 300 back on a 617-line file.

@Srimi1

@Srimi1

A hybrid harness with a claude-muse launcher that runs Claude Code on Meta Model API Muse Spark models, plus a /talk broker for structured exchanges between Claude Code and Muse Code terminals.

@jellologic

@jellologic

Claude Code plugin that offloads bulk coding work to Muse Code workers in isolated git worktrees, with a Claude supervisor that runs your acceptance check and sends failing patches back.

@Sighton-GH

@Sighton-GH

opencode-delegate is a Claude Code plugin where Claude plans and writes briefs while opencode sessions on free models, Muse Spark 1.3 by default, implement and review each task.

@CogniTechSystems

@CogniTechSystems

This repo documents running Muse Glimmer 30B locally on an M4 Max MacBook via llama.cpp, benchmarking it with and without speculative decoding, and wiring it into Claude Code through LiteLLM for fully offline coding.

@troioi-vn

@troioi-vn

delegate-to-muse is a Claude Code skill for handing repository work to Muse Code via muse exec, with a handoff template and checks for reviewing the diff and re-running tests rather than trusting the summary.

@corona10

@corona10

Unofficial native VS Code chat UI for Muse Code, modeled on the Claude Code VS Code extension's layout, commands and keybindings.

@gregmos

@gregmos

Routing overlay for the Superpowers plugin for Claude Code where Muse writes the code, Codex reviews it, and rules keep expensive models from being misused.

@luckeyfaraday

@luckeyfaraday

An unofficial loopback shim that lets Meta Muse Code use OpenAI Responses APIs, OpenRouter, Codex OAuth and the official Claude Code CLI, switchable from Muse's /model menu.

@kevintsai1202

@kevintsai1202

MCP server that gives Claude Code, Claude Desktop, Cursor and other MCP clients image generation and editing powered by Meta's Muse image model, published to npm.

A community-built VS Code chat UI for Muse Code, Meta's agentic coding CLI, inspired by the Claude Code extension; about 145 installs on the Marketplace.

ollama

@ollama

Muse Glimmer is now available to run with Ollama. Available today via Ollama’s MLX engine with state-of-the-art-performance on Apple Silicon, Muse Glimmer can power Claude Code, Codex, and more always-on local agent workflows natively using Ollama. Additional support and

li yin

@panda_liyin

muse spark 1.1 in AdaL Engineer beats Opus4.8 in Claude Code with 20% of the cost loop engineering, when done right, is beyond just running longer, its delivering better results when contexts are managed well and when workers are better prompted to stay honest. how GANs had

@vasyl-stanislavchuk

@vasyl-stanislavchuk

A separate launcher with its own config profile that runs Claude Code's interface on Meta's muse-spark-1.3, for comparing models on identical work or using a Muse Code subscription.

OK, for context, I have Claude Code desktop app driving the CLI and orchestrating the code and verification tasks to try to save tokens. So Claude runs things, a Deepseek 4.1 Flash (cloud) session does the planning, Qwen 3.8 27b Q8 does the boiler plate coding and Muse Glimmer sanity checks the code and pushes any issues back to Qwen. If there are issues Qwen and Glimmer can't agree on, Deepseek validates. If Deepseek can't sort it out, it goes back to Claude. This had been working fine, but then in the last few days token use spiked, tasks that used to take 10 minutes were taking an hour or more and Qwen started going into more and more reasoning loops. It seems that since I last checked (on 12th September) the CLI changed. I used to strip unnecessary tool calls from the prompt using --disallowedTools and enabledPlugins: false. It would seem that these no longer work. In the end I got Claude to build a request-dumping diagnostic server, that actually measured the payload bytes, and confirmed --tools (an allowlist) is the flag that works now: 55→7 tools, 161KB→24KB, byte-verified. It also caught something specific to my workflow running the wrapper from inside an already-active

Ollama shipped Muse Glimmer on day one: `ollama run muse-glimmer`, plus a muse-glimmer:30b-mlx tag for Apple Silicon that Ollama says runs 1.5–1.8x faster with DFlash.