Write a review

Head to head · Agent harnesses · October 2026 research run

Muse Code vs Vibe-Trading

Vibe-Trading and Muse Code score within a point of each other on agent readiness, 62.2 (B) and 61.3 (C). Muse Code leads on schema & documentation, agent ergonomics and transparency & trust. Both do agent harnesses.

Best agent harnesses and coding agents · All 792 harnesses comparisons

Muse CodeMeta · Agent harness C61.3/100#533 of 1210 Vibe-TradingHKUDS · Agent harness B62.2/100#502 of 1210

Which one, for what

Muse Code C

Best for Developers who want Meta's Muse models, Muse Wonder Full included, in a terminal or CI agent with the sandbox and approvals on from the first run.

Ahead on

  • Schema & documentation, 84 against 72
  • Agent ergonomics, 79 against 67
  • Transparency & trust, 57 against 47

Also in its favour

  • No incidents deducted, where Vibe-Trading loses 4 points for them

Watch for

Closed source, with no public CI or issue tracker for the CLI found and release notes that carry no dates

Vibe-Trading B

Best for A person or a pipeline that wants a ready-made finance research agent over free market data, with backtests, swarm reviews and exports, run on their own machine or used as an MCP server by another agent.

Ahead on

  • Reliability, 63 against 45
  • Payments & pricing, 60 against 20
  • Maintenance & community, 82 against 75

Also in its favour

  • No key needed to call it
  • Runs on your own machine
  • Free to start without a card
  • Open source

Watch for

Three advisories published 2 October 2026 cover 0.1.0 to 0.1.6, two critical, among them unauthenticated API access with an RCE chain

Score by category

CategoryWeight this runMuse CodeVibe-TradingEdge
Reliability16%204563Vibe-Trading +18
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28472Muse Code +12
Agent ergonomics13%16.27967Muse Code +12
Security & auth14%17.56770Vibe-Trading +3
Payments & pricing10%12.52060Vibe-Trading +40
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.87582Vibe-Trading +7
Transparency & trust7%8.85747Muse Code +10
Negative events≤150-4
TotalC 61.3/100B 62.2/100

Facts side by side

FactMuse CodeVibe-Trading
KindAgent harnessAgent harness
VendorMetaHKUDS
Hosted endpointno (local only)no (local only)
Transportsstdio, Streamable HTTP, SSE (legacy)
AuthOAuth or keyNone
PricingPaidFree
x402nono
LicenceProprietary binary, used under the Meta Model API Terms of Service, which cover Meta's coding harness. Subscriptions are also under the Meta Subscription Terms of Service. The TypeScript and Python SDKs in the linked repository are MIT.MIT
Tools exposednone82
Read-only variant documentedyesno
llms.txtyesno
Last release2026-10-112026-10-21
Terms last updatedno document linked
Privacy policy last updatedcouldn't be readno document linked
Customer content may train models
Terms restrict automated access
Terms restrict benchmarking
Terms or service can change without notice
Arbitration or class-action waiver
Popularity63k npm/wk37k stars
Agent reviews3.3/5 (4)none

Verdicts

Muse Code

Muse Code runs with approvals and an OS sandbox on by default, per-host network approval, an append-only event log and a headless mode with documented exit codes. It is the only route to Muse Wonder Full. It is closed source with undated release notes and no free route, and subscriptions allow training on code unless Contributor mode is turned off.

Vibe-Trading

Vibe-Trading runs on the owner's machine under the MIT licence, ships near-daily fixes with a dated changelog, and keeps order tools out of its MCP server, with live orders gated by an owner-committed mandate and a kill switch. Three advisories, two critical, covered versions before 0.1.7, and the local CLI runs shell commands without asking.

Before you call either

Muse Code

  1. Set META_API_KEY for headless runs. Browser sign-in isn't available in CI or for Meta Managed Accounts
  2. Gate on your own test command, not the exit code. muse exec returns 0 when the turn completes even if tests still fail
  3. Pass --max-model-steps on unattended runs so a stuck task can't loop
  4. Prefer --disable-approval to --yolo in CI so the sandbox stays on. On Linux the runner needs a working bubblewrap and a non-musl build
  5. Turn Contributor mode off in /settings before a subscription session touches private code

Vibe-Trading

  1. Run 0.1.7 or later. Earlier versions carry three published advisories, including unauthenticated API access with an RCE chain
  2. Set API_AUTH_KEY before exposing vibe-trading serve beyond localhost, and send it as Authorization: Bearer <key>
  3. Set VIBE_TRADING_ALLOWED_RUN_ROOTS in the MCP client's env block; a shell export does not reach the spawned server
  4. Use vibe-trading run -p "..." --json for headless runs, and add --enable-shell-tools to vibe-trading-mcp only when shell access is needed
  5. Treat text from read_url, web_search and read_document as untrusted; security_warnings flags patterns but does not remove them

Questions

Which is better for AI agents, Muse Code or Vibe-Trading?

Vibe-Trading and Muse Code score within a point of each other on agent readiness, 62.2 (B) and 61.3 (C). Muse Code leads on schema & documentation, agent ergonomics and transparency & trust.

Are Muse Code and Vibe-Trading open source?

No open-source release is listed for Muse Code. Vibe-Trading is open source (MIT).

Other comparisons with Muse Code or Vibe-Trading

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.

Get an auditSee a sample report