mrkeyoor.comAsk

unstablebuild/runetested 02 Oct 2026commit 53a9d36

rune review

Consider a focused Rune trial if its integrated editor and terminals fit your work.

  • Install 157 s
  • Build 224 s
207/223passed, run exited non-zero
  • 785 packages
Dev Toolsevaluationupdated 31 Oct 2026
+32stars / 7d

Rune is an IDE and terminal multiplexer with a built-in agent and remote workspaces. Consider a trial if you want those tools in one application. MrKeyoor's stored run at commit 53a9d36 does not establish desktop readiness: the build command recorded success, but its retained output contains a compilation error.

Verdict

Consider a focused Rune trial if its integrated editor and terminals fit your work. MrKeyoor's October 2, 2026 run at commit 53a9d36 recorded installation success, contradictory build evidence and a nonzero test outcome. It does not support a recommendation to standardize on that checkout. Start by reproducing the build on a supported desktop and investigating the X11 diagnostic, then evaluate a representative project. Test remote access separately if that is your reason to adopt Rune.

We ran it

Lab card: what happened when we ran rune
Lab card from our sandbox run
Screenshot of rune (rune.build)
rune.build
Install✓ · 157s785 packages
Build✓ · 224s
Tests✗ · 494s207 passed · 16 failed of 223 (go test)
Repo2614 files~749,819 lines of source · 107.1 MB · 7 CI workflows

Answers from our run

Does rune build from source?

Dependencies installed in 157 seconds (785 packages), and the build succeeded in 224 seconds. We cloned commit 53a9d36 into a clean Debian container with 3 CPUs and no project-specific setup.

Do rune's tests pass?

No. The project's own test command finished in 494 seconds and reported 207 passed, 16 failed (go test).

Who should not use rune?

Developers who need documented Windows support now: the supplied prerequisites describe Windows as coming soon.

What are the alternatives to rune?

Zed, Helix, tmux. Consider a focused Rune trial if its integrated editor and terminals fit your work.

Setup3/5Installation completed in the stored sandbox run, providing an evaluation path, but recorded build success conflicts with a missing X11 header and vet-exit:1 in the retained output. The visible rubric treats this as material unresolved friction in that path.
Docs4/5The supplied prerequisites and network guide explain installation choices, platform boundaries, account requirements and remote operation. This supports the rubric's broad documentary-evidence rating; the recipes were not verified by execution here.
Community2/5Last push on 2026-10-02, 1,790 stars and 102 open issues and pull requests is a heavy backlog for its size.Editor’s note: The supplied primary extracts do not establish contributor responsiveness, sustained participation or issue-resolution history, so they cannot support a numerical community judgment.
Maturity3/5For this evaluation, completed installation provides a starting point, while contradictory build evidence and a nonzero test outcome leave material limits. The rating does not establish production reliability or rely on release numbering or repository age.

How we score

Who it’s for

Developers evaluating editing, terminals and an agent in one application.
Keyboard users interested in application-wide editing presets.
Developers considering remote projects on their own machines who accept Rune's account and coordination-service requirements.

Who it’s NOT for

Developers who need documented Windows support now: the supplied prerequisites describe Windows as coming soon.
Alpine users: the prerequisites explicitly exclude musl-based distributions.
Teams requiring a verified desktop launch, working remote session or fully green test run before adoption. The stored sandbox record establishes none of those outcomes.
Teams that cannot use an account-backed service for Rune's private network.

Setup reality

MrKeyoor's stored run on October 2, 2026, at commit 53a9d36 recorded installation success, exit code 0, after 157 seconds. The dependency count is 785; it is not a count of installed operating-system packages.

The build command recorded success, exit code 0, after 224 seconds. Its retained output nevertheless reports a missing X11/Xlib.h header, compilation termination and vet-exit:1. These conflicting observations do not establish a working desktop build.

The test command returned exit code 1 after 494 seconds. The stored parser summaries report 207 passed, 16 failed and 223 total. The raw measurement labels the corresponding success and failure figures packagesOk and packagesFail and separately records 31 packages without tests. These are package-level parser summaries, not verified counts of individual, unique or exhaustive tests. No complete-log reconciliation or new execution was performed.

The recorded environment was golang:1.24-bookworm with 3 CPUs and 8 GB of memory. The retained install output reports downloading Go 1.27.1, so the container image name does not establish the compiler version actually used.

Should you trial Rune?

Trial Rune if combining editing, terminals and remote projects would help your workflow, and you can evaluate it before relying on it. MrKeyoor's stored sandbox run concerns commit 53a9d36. It does not verify a graphical launch, interactive editing, agent execution or a working remote session.

The Rune README documents nine workspace slots, terminal panes, a built-in agent and native graphics. The current getting-started guide describes standard, Vim, Emacs and Helix editing presets that apply to terminals, input boxes and the file explorer as well as editor buffers. These are documented capabilities, not workloads exercised in the stored run.

What MrKeyoor's sandbox recorded

The October 2, 2026 run at commit 53a9d36 recorded installation success after 157 seconds. The build command recorded exit code 0 after 224 seconds, but its retained output includes fatal error: X11/Xlib.h: No such file or directory, compilation terminated. and vet-exit:1. The success flag alone cannot support a successful desktop-build claim.

The test command returned exit code 1 after 494 seconds. Its parser summaries report 207 passed, 16 failed and 223 total, with the raw record identifying the success and failure figures as package outcomes. Another field records 31 packages without tests. These figures have not been reconciled against complete logs and do not establish exhaustive unique test coverage.

The retained test tail names failures in TestComponentEditorSubscriber, TestSchemeReportsDisconnect and TestIntegrationManagerIsWorkspaceFile. The last includes two SSH-style path subcases. These are visible failures, not a complete failure inventory or a diagnosis. The missing X11 header does not establish why those tests failed.

The record contains no desktop or remote-workspace validation, runtime performance benchmark or security audit. The testing methodology provides context for MrKeyoor's measurements; its current wording does not prove which procedure version the October 2 run used.

Remote workspaces require an account and a running peer

The network guide requires a Rune account and Rune running on both machines, signed into the same account. A machine serves its workspaces only while Rune runs there. The free plan permits up to two registered nodes, including offline ones.

The guide describes discovery through Rune's coordination server, direct encrypted communication where possible and an encrypted relay fallback. Those are the project's descriptions, not security findings from MrKeyoor's run.

For an unattended machine, the network guide describes headless operation. The current README advertises a container image, while the recorded checkout scan found no Dockerfile. That scan does not establish how the published image was built or whether it deploys successfully.

Rune also documents SSH workspaces. Its guide recommends SSH for machines that are not yours or do not run Rune, and Rune's network for your own machines. The account-backed network is therefore one documented remote-access choice within Rune.

Check the platform and language tools first

The current prerequisites list macOS 13.3 or newer on Apple Silicon or Intel, or Linux on x86_64 or arm64 with glibc 2.28 or newer. The graphical application needs an OpenGL-capable driver and X11, with Wayland supported through XWayland. Alpine and other musl distributions are unsupported. Headless mode loads no graphical library.

These requirements come from current documentation. The supplied evidence does not map that documentation or a release tag to measured commit 53a9d36. It also does not establish language-support tiers for that checkout. Check the language servers, debuggers and build tools your representative project needs before committing to a trial.

Choose alternatives by the job you need done

Zed describes itself as a high-performance, multiplayer code editor. Evaluate it when collaborative editing is the main requirement. The supplied extract does not establish equivalence with Rune's remote-workspace network.

Helix documents modal editing, multiple selections, built-in language-server support and tree-sitter syntax tools. Evaluate it when you want a primarily terminal-based editor. The supplied extract does not establish a replacement for Rune's integrated remote service.

tmux documents terminal sessions that can detach and later reattach. Choose it when persistent terminals are the requirement, alongside your chosen editor.

What the editorial scores mean

These ratings are editorial judgments, not benchmarks. The rubric runs from 1 for a documented obstacle to the evaluated task, through 2 for substantial unresolved friction and 3 for an evaluation path with material limits, to 4 for broad supporting evidence and 5 for broad evidence corroborated by relevant hands-on checks. Unassessed dimensions receive no numerical rating.

Setup ease is 3: installation completed, but the build output needs investigation. Documentation is 4: the supplied guides explain platform requirements, installation choices and network operation, although their recipes were not verified here. Maturity is 3 for this evaluation: installation completed, while contradictory build evidence and a nonzero test outcome leave material limits. This judgment does not establish production reliability or infer maturity from repository age. Community is unassessed because the supplied extracts do not establish contributor responsiveness or sustained maintenance.

Alternatives

ProjectWhat it isPick it when
Zed gh↗A code editor whose README emphasizes performance and multiplayer editing.Evaluate Zed when collaborative editing is the main requirement; the supplied evidence does not establish an equivalent Rune network.
Helix gh↗A primarily terminal-based modal editor with multiple selections, language-server support and tree-sitter tools.Evaluate Helix when you want a terminal editor; the supplied extract does not establish an equivalent integrated remote service.
tmux gh↗A terminal multiplexer with detachable sessions that continue in the background.Choose tmux for persistent terminals alongside your chosen editor.

What people are saying

  1. [velocity-scout] unstablebuild/rune
  2. [hackernews] Rune is now open source

Sources

  1. Rune repository and README
  2. Rune prerequisites
  3. Rune network guide
  4. Rune headless guide
  5. Rune supported languages
  6. Rune v1.2.1 release
  7. Rune measured commit

More dev tools reviews