Mirafold
Run and supervise your local coding agents from a browser.
- Source repo
- mirafold/mirafold
- Stars
- ★ 19
- Last updated
- 1mo ago
- License
- MIT
- Primary language
- TypeScript
- FA score
- 87/100 · Good
At a glance
- How it runs
- Works with
- Universal · cross-platformCodex · Claude Code
- Cost
- Free tier plus a paid hosted plan
- Setup effort
- Low · running in minutes
- You'll need
- Typical use
- A developer who already uses Codex, Claude Agent, OpenCode, or Gemini CLI and wants a browser-based, structured view of the same native agent.
- Not a fit if
- Teams that need fully offline or air-gapped operation; remote pairing relies on the vendor relay
- Users unwilling to buy a Mirafold Pro license for remote browser and phone pairing
- Teams needing production-stable tooling and no public-beta rough edges
- Source review
- 87/100 · Good
What does this agent do, and when should you use it?
Mirafold is a browser interface for Claude Agent, Codex, OpenCode, and Gemini CLI, not a generic replacement agent placed between the user and those tools. A local daemon adapts each agent's native event stream, while a React client renders streamed Markdown, tables, charts, diffs, task lists, diagrams, images, and other interactive output. The selected agent continues to use its local engine, credentials, configuration, permission model, filesystem, and shell. The interface adds persistent sessions, multiple attached browser views, mission control, an in-session Cockpit, read-only file browsing, and Git change review. It also supplies a real PTY for interactive commands and optional remote browser or phone access through an end-to-end-encrypted relay. The code is MIT-licensed, although remote pairing requires an active Mirafold Pro license key.
On startup, the local daemon uses the current directory as the default workspace, and AgentPicker lets the user choose a supported agent, a detected backend, and a working directory. Per-agent adapters convert native event streams into the shared protocol defined in server/protocol.ts; a session registry owns warm sessions, replay history, and browser attachments. The React client separates shell-owned controls from the agent-controlled output zone, where validated registry components and sandboxed artifacts are rendered. Ordinary prompts go to the agent, ! commands run through an interactive PTY and expose their transcript to the agent as a turn, and !! commands run as shell-only operations that the agent never sees. Files and Changes inspect the current directory and its Git working-tree changes, while mission control and Cockpit can preview, prompt, stop, end, or switch sessions. If no usable live backend is detected, Mirafold runs its built-in scripted demo without model traffic.
- A developer who already uses Codex, Claude Agent, OpenCode, or Gemini CLI and wants a browser-based, structured view of the same native agent.
- An engineer supervising several coding sessions who needs mission control or Cockpit to inspect, switch, stop, and end them.
- A reviewer who wants read-only workspace navigation and Git working-tree inspection beside the agent conversation.
- A command-line user who needs interactive programs or password prompts to retain real PTY behavior inside a coding session.
- A team evaluating the interface without configuring a live model backend or generating model traffic, using the scripted demo.
- A Mirafold Pro subscriber who wants to pair a remote browser or phone with the machine running the local daemon.
How do you install or deploy this agent?
Node.js 22 or newer is required. Install Mirafold globally, enter a project you are prepared to expose to the agent, and launch it:
npm install --global mirafold
cd /path/to/trusted-projectmirafold
The command binds a server to loopback, opens the browser, and treats the current directory as the default workspace. Supported options include mirafold --help, mirafold --no-open, and mirafold --verbose. Use npx mirafold only in a project you already trust because npx exposes project-local executables to launched commands. A live session also requires a detected supported agent backend and authentication accepted by that agent; otherwise Mirafold starts its scripted demo.
How do you use this agent?
After running mirafold, use AgentPicker to select an agent, one of its detected backends, and a working directory. Enter normal requests in the prompt box. Prefix a command with ! to run it in Mirafold's interactive shell and make its transcript visible to the agent as a turn; use !! for a shell-only command the agent never receives. Open / for mission control or /s/<session-id> for a specific session viewport. Cockpit, available from the activity bar, can preview, prompt, stop, end, and switch among live sessions; Files and Changes expose the current directory and Git changes. The show details control expands reasoning, routine calls, inputs, and retained output for the current browser tab. Remote access is paired through the ⧉ pair status-bar control and requires an active Mirafold Pro license key.
What are this agent's strengths and limitations?
- It uses a dedicated adapter for each of Claude Agent, Codex, OpenCode, and Gemini CLI, preserving the native engine, authentication, configuration, and permission model.
- MCP tools can produce live tables, charts, diffs, task lists, diagrams, images, and other interactive components in addition to streamed Markdown.
- Persistent sessions, multiple attached browser views, mission control, and Cockpit provide concrete controls for supervising several sessions.
- The real PTY supports interactive programs and password prompts, with a clear distinction between agent-visible ! commands and shell-only !! commands.
- The scripted demo makes the complete interface explorable without a usable live backend or model traffic.
- The project is explicitly in public beta, so adopters should expect bugs and rough edges.
- It requires Node.js 22 or newer, and live operation also depends on an installed, authenticated, supported agent backend.
- Because it drives a real agent with filesystem and shell access, users must review permission prompts and restrict it to directories they are willing to expose.
- Remote browser and phone pairing requires an active Mirafold Pro license key rather than being fully included with the MIT-licensed code.
- Reattached browsers may lack history that has fallen out of the daemon's replay buffer, and large outputs retain only their beginning and end.
How does this agent compare with similar options?
Compared with using Claude Agent, Codex, OpenCode, or Gemini CLI directly in a terminal, Mirafold keeps the native agent and its local permission model while adding a browser UI, structured generative components, multi-session supervision, and adjacent file and Git views. It is not a unified proxy agent and does not replace those CLIs with its own generic implementation. Each supported agent has a separate adapter, so live availability still depends on that backend and its authentication.
Key facts side by side with the most closely related agents.
| Agent | Source review | Form / cost | Stars | Updated | Language | Full support on |
|---|---|---|---|---|---|---|
| Mirafold This agent | 87 · Good | CLIFreemium | ★ 19 | 1mo ago | TypeScript | Codex · Claude Code |
| zerostack | 69 · Some gaps | CLIFree + model costs | ★ 1.7k | 4d ago | Rust | OpenAI API · Claude API |
| pitwall | 81 · Good | — | ★ 21 | today | Go | Codex · Claude Code |
| nca Native AI Coding CLI | 59 · Major gaps | CLIFree + model costs | ★ 205 | today | Rust | OpenAI API · Claude API |
How does FollowAgents rate this agent?
Why each dimension lost points
The security materials give concrete evidence for loopback binding, opt-in remote relay, browser CSP, server-side credentials, an allowlist for project environment settings, checkpoint decoding limits, and CI permissions, supporting high scores for least privilege and sensitive-data handling. The README and security policy disclose that agents have filesystem and shell access and that `!` uses a real PTY; they tell users to review permission prompts and choose directories carefully. The packet does not show Mirafold independently confirming every action, so user confirmation and external effects are not full marks. Checkpoints are atomically replaced and a disclosure route is documented, but a general operation rollback mechanism is not evidenced, so rollback is deducted. Adapter, protocol, and `notice.source` rules clearly attribute engine-originated content, earning full marks for attribution. Dependency versions and some pinning practices are shown, but the static packet cannot establish complete vulnerability monitoring or remediation coverage, so dependency security is deducted.
The README, architecture description, package scripts, and CI corroborate the main test tiers and mock/live boundaries. However, CLAUDE.md and the README/script disagree about the development server port (3000 versus 3100), reducing self-consistency. Node requirements, install commands, and package dependencies are documented, but the packet omits the lockfile and any fallback dependency acquisition plan, so dependency availability is only partly supported. Startup problems, weak pairing codes, crashes, and unsafe configuration have explicit logging or user-facing messages, supporting a high failure-message score.
The README covers several terminal agents, authentication and model backends, desktop use, and remote browser scenarios, with a local-model guide. The security policy clearly describes boundaries around loopback, the real PTY, relay access, and local-model discovery. Agent selection and `!`/`!!` command triggers are explained, but the excerpt does not fully establish trigger rules for every context, so trigger precision is deducted. Node 22, npm/Yarn, development and packaged launch paths, and port configuration are documented, supporting a high environment-fit score.
The README separates installation, first run, development, architecture, and documentation, and its documentation index states each document’s purpose. Requirements, install commands, and the `npx` risk are specific. Version 0.10.0, latest-release-only support, plan/archive documents, and a release guide provide some version and change-process evidence; the packet does not include a complete changelog, and naming stability and FAQ/example coverage are not fully established. The MIT license and third-party license notice are explicit. The security policy gives a vulnerability contact, response timeframe, and support rule, but ongoing maintenance ownership is not sufficiently independently established, so maintenance responsibility is deducted. Per the publisher rule, publisher identity remains unknown.
The product combines terminal-agent sessions, readable output, interactive components, session overview, and read-only file/Git views in a browser. The README gives concrete workflows and transcript behavior, supporting full marks for output usability and marginal value. Global npm installation requires Node 22, and agents still run locally; remote features also have a Pro entitlement condition. Costs and benefits are not quantified, so cost-benefit receives partial credit.
README claims can be cross-checked against package scripts, adapter entry points, the component registry, CI, and the security policy. Security design claims have corresponding source or workflow descriptions. CI and test tiers are presented as repository configuration, not as results from this review; the assessment remains static and low-confidence and does not claim independent verification. The packet is a sample, so unseen files are treated as unknown rather than missing.
- Mirafold drives agents with local filesystem and shell access; real PTY commands run with the current user’s privileges. Review permission prompts and choose a workspace suitable for agent access.
- Remote access uses an optional relay subject to Pro entitlement. The security policy says local model servers cannot be authenticated; a malicious local endpoint could receive conversation content.
- Development port documentation is inconsistent: CLAUDE.md says 3000, while the README and package script use 3100.
Maintain this project? Add the FARS badge to your README
[](https://followagents.com/en/agents/mirafold)<a href="https://followagents.com/en/agents/mirafold"><img src="https://followagents.com/badge/mirafold.svg" alt="FARS review"></a>Recent releases
Latest entries from the project's GitHub Releases. Notes are quoted from upstream as written, not rewritten or tested by FollowAgents.
-
v0.9.1 mirafold v0.9.1
Release notes excerpt
Bug fixes and reliability improvements following v0.9.0. - Session switches show replayed history at its end. Phone prompts wait for a tap before taking focus. - Painting file links open in Files. Question detail links remain independent of answer buttons and usable after answering. - Unfinished turns keep their work state across reconnects. Encrypted messages retain their order, stale socket work is discarded, and an unserializable action cannot block later reconnects. …View on GitHub ↗ -
v0.9.0 mirafold v0.9.0
Release notes excerpt
Secure Desktop relay foundation. Highlights: - Added the private Desktop-to-Shell credential handoff so a permanent Mirafold Pro key does not enter process environment, command arguments, child processes, logs, or viewport messages. - Added an additive local-only Desktop host identity and the activation return path while preserving older Desktop and ordinary terminal launches. - Hardened entitlement expiry and refresh behavior, malformed token handling, relay setup and reconnect failures, billing redaction, subscription claim validation, and persistent relay logging. …View on GitHub ↗ -
v0.8.4 mirafold v0.8.4
Release notes excerpt
Architecture and development-reliability release. Highlights: - Clarified code ownership with stable domain folders for server adapters, session persistence and workspace services, test infrastructure, and client-side transport, transcript, input, and workspace logic. - Fixed yarn dev port coordination so an occupied daemon port fails the whole development stack instead of leaving Vite connected to an unrelated listener, while preserving source reloads across native and portable file watchers. - Preserved the active PTY controls when an overlapping ! or !! command is rejected. …View on GitHub ↗
FAQ
Do I need model credentials to try Mirafold?
Does Mirafold move my agent or filesystem into the cloud?
Is remote phone access included in the open-source package?
Will a reconnected browser always receive the complete transcript?
What is the main security consideration?
Thanks — we use this to improve the page.