M Code By NULLXRECode with focus. Make room for everything around it.
A coding workbench and Miku Personal, together in one thoughtfully connected environment.
Move between engineering and creative planning. Give each kind of thinking its own space.
Explore a project, work through a plan, and review proposed changes. Keep the context of your code close to the decisions you make.
A separate space for conversations, saved notes, and daily planning. Make room for the creative work that surrounds a build.
Keep your intent in view, your changes reviewable, and your next step close at hand.
Use Miku Personal to capture the idea, save useful context, and organize the day’s priorities.
Move into Code to work with your project. Inspect plans, review file changes, and follow execution in the run tree.
Return to the bigger picture. Coordinate the artwork, release notes, and creative details that give a project its finish.
M Code brings hosted routes and local connections into the same environment. Choose a connection to suit your project and workflow.
A configured hosted route for coding, planning, and conversations through the Nucleus gateway.
A configured hosted route for reasoning, project exploration, and creative direction.
Connect local Ollama models or your own OpenAI-compatible endpoint.
M Code is in active development for macOS Apple Silicon. Explore the interface here while public distribution and runtime validation continue.
A public installer is not yet available. Developer ID signing, Apple notarization, public sign-in, and hosted gateway access are release gates.
The Code workbench includes an editor, diff review, execution plans, run history, and rollback snapshots. Miku Personal includes conversations, memory notes, and a local daily checklist. The captures on this page were recorded on October 13, 2026; they show the interface, not a completed inference or desktop-control test.
Code sessions stay with their projects. Miku Personal stores conversations, notes, and plans separately in an encrypted personal vault. Messages and relevant context are sent to the selected model when you use it. Today’s plan is a local checklist and does not schedule background notifications.
The experimental macOS Accessibility bridge requires an explicit permission grant, a reviewed single-app connection, and approval for each action. End-to-end validation remains open; the previously recorded native trial was blocked by a permission/signature mismatch. The helper works with accessibility information, not screen pixels.
Genesis and Enigma are configured routes in the development build. Public account access and hosted personal-chat access still require release validation; the previously recorded native personal-chat trial returned HTTP 403. A configured route alone does not establish successful inference.