Entries matching “windows”

@EtienneLescot

@EtienneLescot

A desktop app for Muse Code on macOS and Windows with projects, git worktrees, subagents, MCP, a diff review panel and opt-in computer use that lets the agent see the screen and use apps.

My fun weekend project was to try to make the new Muse Glimmer 30B work with a longer context, deciding to go for 512k first. I had expected the usual YaRN shenanigans and maybe a LoRA. I couldn't have been wrong more. Upon closer look, Glimmer turned out to be rather unusual architecturally. The thing that make long-context adaptations painful in other models, full attention layers with token position encoding, it simply not there. Instead, only 2048 tokens-wide SWA layers have RoPE, and full GQA attention layers have no position encoding at all. It appears the model is trained to work with long-distance token relationships inferred from the context and SWA layers. It's a rather bold architecture bet, but it seems Meta managed to pull it off. As a result, the model architecture appears to be uniquely suited for context extension by simple mechanical means. To change model context length from stock 128k to, say, 512k, you need only to change “max_position_embeddings” config setting from 131072 to 524288. What confuses other models, like Qwen3.5 family, Glimmer just takes into its stride. I spent close to 70h of compute on DGX Spark to test stock model with extended context on a

joe feeney

@iamsomewalrus

Very cool experience with Meta Muse. My wife and I were chatting about college tours on the way to get food. I whipped out Muse, listed the schools. Muse did the obvious thing and found the windows for booking etc but, surprisingly, it generated a PDF! Super cool and it was

@latekaapi

@latekaapi

A native macOS window for Muse Code that drives muse serve over MSP and renders approvals, questions, plans, todos and tool output as interface elements instead of terminal text.

elie

@eliebakouch

extremely exciting to see meta getting back into open weight models with a 30B dense first, and soon muse spark 1.2 they used knowledge distillation from muse spark, architecture wise it's similar to gemma 4 (which is llama 3 + swa (again!) + vision encoder), with scale free QK

@aminamos

@aminamos

Four graphical frontends for Muse Code (Tauri apps for Windows and macOS, Expo apps for iOS and Android) plus a Deno relay, so every run executes through muse on the subscription login.

Dilmer

@Dilmerv

Last night, I built a VR game prototype in a few hours with Muse Code on PC. It was already available on macOS and Linux, and today we’re bringing it to PC! 🔥 I tested it with Unity through the Unity CLI, and here are a few things that worked really well for me: - Having Muse

@aminamos

@aminamos

Native Muse Code plugin that wires in Hindsight memory with one bank per repo, using SessionStart, UserPromptSubmit and Stop hooks to recall and store context across agents. Zero dependencies, runs on macOS, Linux and Windows.

Benchmarked qwen3.8 xhigh, medium and muse glimmer. Xhigh effort mode with qwen3.8 took almost 30hrs. (And still failed on 16 cases because of the 32K output token limit) Medium effort mode and muse glimmer were 3-4 hours each. But I'm actually surprised by the muse glimmer results, they came better than the qwen. These benchmarks are on implicit knowledge of the model, which is a bit unfair to smaller models, but throw in a RAG and I'm sure they get on par with frontier models. I have taken the result of claude models directly from embedeval repo by ecro. I'm not pushing qwen down here, I like how qwen thinks and gives better results. I know with more context and RAG qwen will do better. I'm just appreciating muse here, cause i feel it is underrated. The advantage is efficient kv cache due to sliding window, which can give you more context window.

harjot.co

@harjjotsinghh

I pay for @Muse Code but didn't want to live in a terminal. On Windows it's WSL-only. So I built Helicon: an open-source desktop app for the actual Muse CLI. • uses your existing muse login, no API key • talks to muse serve over MSP, so Muse stays the agent • resumes

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

@jason-snell

@jason-snell

windows-cua is a native C++ Win32 port of Meta's macOS computer-use agent that drives Muse Spark 1.1 through the Responses API to see and operate a real Windows desktop.

Sebastian Raschka breaks down Glimmer's dense architecture: 3:1 sliding-window to global attention, 32 query heads with only 2 KV heads, and ~52 KiB of KV cache per token.

@Telep-IO

@Telep-IO

Omusey is an Omarchy plugin that puts Muse chat in the Linux desktop bar as a dropdown that can pop out into its own window.

Alok

@analogalok

The "I don't have enough VRAM" excuse just died. I’m running Meta’s new 30B Muse Glimmer Q6_K_XL with a massive 130k context window on just 26GB VRAM FREE compute on Kaggle. Kaggle provides you free 2x Nvidia T4 GPUs. 30 hours usage each week! Yesterday, I showed you the

@axlecoffee

@axlecoffee

A BYOK VS Code extension that registers the InferHub catalog, including Muse Spark with its 1,048,576-token context window, as a model provider in the Copilot Chat picker without Copilot Pro.

Built a small bridge so Muse can act on my Mac from my phone, and recorded a real session: it looks at the Terminal, reports the epoch, loss and accuracy it sees, then locks the machine when asked. What struck me building it is how much of the work is permissions, not intelligence: per-action consent, small window captures instead of a live feed, rejecting stale observations before any input. Free beta if anyone wants to try it. Developer here, ask away. try wand here today