Entries matching “orchestration”

Anyone using Muse an orchestrator for fleets of coding agents? I’ve found it surprisingly effective and it’s convenient to be able to do so on the go from my phone. Plus Muse can instantly serve your web app for quick testing. it’s actually been pretty fun.

@jefalcon

@jefalcon

Native Muse Code plugin with 18 specialist skills, 7 orchestrator commands and turn/session-end notifications, installed via the omm npm CLI. Requires Muse Code 1.3.0+.

@DevvGwardo

@DevvGwardo

muse-spark-crew is an opencode skill that orchestrates ten specialist subagents on Muse Spark 1.3, from architect to security auditor, with a phased fan-out and review gates.

Meta's post on Muse Code exiting beta with inter-session messaging, parallel-agent workflow orchestration, rewind, a TypeScript SDK and three subscription tiers.

INT21 ran Muse Spark 1.1 in its SwarmOS orchestration layer and argues the durable enterprise advantage is orchestration, not any single model.

jakef

@jakefeigs

.@Muse scoring me deals left and right. gave it access to my @xpticket account and it locked in two orchestra seats for concert tonight at $117 now it’s negotiating with a season ticket holder over warriors vs mavs tickets for my brothers birthday in november

@everyai-com

@everyai-com

A set of small fixes that let Muse Spark run in pi, Agent Orchestrator, opencode and other OpenAI-compatible tools, handling its non-standard SSE event and missing model-catalog entries.

RuntimeWire reverse-engineered the Muse Code R708.1 binary and found a dormant JavaScript workflow engine, multi-agent orchestration primitives and an environment-gated plugin manager.

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