Entries matching “codex”

@HarjjotSinghh

@HarjjotSinghh

Helicon is an open-source desktop and web app that wraps Meta's Muse Code CLI in a Codex/Claude-style interface, grouping sessions by project with history, resume and diffs on Windows, macOS and WSL2.

@cherry-nft

@cherry-nft

Experimental dependency-free Codex skill that lets Codex send tasks to Muse and read its responses through the user's signed-in Muse browser session, no server or API key.

Composio compares Muse Code and OpenAI Codex on pricing, models, agent architecture, extensibility, safety and open-source support.

After running out of quota on two Codex subscriptions, found it was almost trivially easy to run Muse Spark 1.3 in Codex Desktop; not as good as Astra, but cheap and it one-shots most of his prompts.

davidlee

@davidlee

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

@danny-hines

@danny-hines

Call Muse Code from Codex or ChatGPT desktop via MCP tools and skills for independent code review, approach comparison or delegated implementation, using a Muse Code subscription or API key.

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.

@NatesVibeCode

@NatesVibeCode

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

@alamorre

@alamorre

A Codex skill for selectively delegating bounded implementation tasks to Muse Spark 1.3 while the Astra model keeps strategic decisions and final review.

@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.

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

@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.

@Srimi1

@Srimi1

An experimental macOS gateway that keeps the stock Muse Code CLI in charge of the UI, sessions and tools but swaps the model connection for OpenAI or Z.ai models via a loopback gateway.

@LucasDuys

@LucasDuys

sol-loop pairs a GPT planner on a Codex subscription with Muse Spark in opencode as executor, which returns evidence and diffs for each atomic spec; the author says over 99% of tokens run on Muse.

@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.

@kengzzzz

@kengzzzz

An installer for a muse profile in OpenAI Codex plus helper binaries, including a Meta device-code login helper, so Codex can run on Muse without the muse binary.

Peter Steinberger 🦞

@steipete

CodexBar learned a few new tricks in the last few weeks! TypeSafe, Nous Portal, Muse Code, CodeRabbit, Replicate, HuggingFace, Pi, Helmcode, v0, Charm Hyper, GitKraken AI, Bifrost My ambitions for this app REALLY outgrew the app name. (Oh and these keychain alerts are no more)

rob

@goof

My muse has codex and Claude running on his machine so he can call up for some reinforcements when he gets stuck, unless you got muse 1.3 pro on deck

@Alphaxalchemy

@Alphaxalchemy

A ~90-line zero-dependency Node forwarder that lets OpenAI Codex switch between GPT and third-party models such as Meta Muse Spark just by model name.

@emonibnmustafa

@emonibnmustafa

A local translation gateway and profile manager that plugs Meta Muse Spark (or DeepSeek, Groq, Ollama) into OpenAI Codex and ChatGPT Desktop, translating tool calls and SSE streams, with a one-command switch between providers.

I've been running my work in Codex as project folders, and recently tried to properly understand how Muse Goals work under the hood. Made it a goal — good way to watch the machinery operate on itself. The structural problem is worth naming: the current design is a halfway house between two coherent designs, and it gets the costs of both. Design A is Codex: the project is a container. Everything — chat, state, artifacts, scheduled work — lives in one place. My course project has one tracker file, explicit resume rules for new chats, and the curriculum never holds status. Legible, but you have to go to it. Design B is full ambient: no containers at all. The goal is just context that wakes up wherever you mention it, and there's no Goals tab pretending otherwise. Muse picked ambient for activation — talk about the goal anywhere, it wakes up, you never "open" it. But then it built half of containment: a Goals tab showing summary, artifacts, activity, without the other half. Conversations, check-ins, and briefings still leak into whatever chat they happened in. So you get the scattering of ambient with the implied promise of a container. That's the worst combination. The fix is to

@syamimhazmi

@syamimhazmi

A vim-modal multi-tab Rust TUI for coding agents where each tab is a session, fronting Muse Spark via muse serve alongside Codex, Antigravity and Grok backends.

@accretional

@accretional

Unofficial knowledge base and tools for Meta's Muse Spark, starting with a root-cause write-up of Codex tool-calling failures with Muse Spark 1.1.

@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.

@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.

thehype.

@thehypedotnews

muse spark 1.2 vs gpt 5.6 sol vs kimi k3 vs grok 4.5 – on two landing pages four coding agents built two desktop landing pages from scratch, then had to open them in a real browser, find their own bugs and fix them before they were allowed to hand anything over the setup: each

I've been migrating my workflow from ChatGPT Work / Codex over to Meta's Muse, and I've been auditing the harness as I go — reading cron files, checking diffs, mapping what the system actually does versus what it claims to do. It's a documentation gap. What the docs describe Meta's documentation is written for a normal user. It talks about the Ideas tab, the Goals tab, the Feed, and "background jobs that help Muse improve over time." Everything is described in terms of what it does for you. There is no architectural documentation. Nothing about how any of it is built. What is actually on disk Meanwhile, the home directory contains a fully legible agent architecture, just sitting there(these are just SOME examples, the system file structure is HUGE): • ~/dreams/alignment/ — a nightly job that regenerates an alignment synthesis: a written portrait of the user, how to handle them, current frictions, relationship guidance. • ~/workspace/objectives/goals/STUDYING.md — a daily learning-state projection with mastery bands, next-review dates, and retrieval prompts, plus a file of inferred goal leads the system guessed from behavior (with confidence levels and what would confirm or re