Rune, a Pre-Release Rust UI Framework, Takes No Pull Requests and Asks for Issues Written by Your Agent

Rune, a GPU-rendered UI framework for macOS, Windows, Linux and the web written in Rust, reached 155 points and 112 comments on Hacker News on Nov. 6, 2026, a day after its repository passed 2,600 stars. The README calls it pre-release, licenses it under MIT, and says the project does not take pull requests.

Instead, the anomalyco/rune README tells contributors, in its own words, "We don't take pull requests. Have your agent open" an issue. That policy, more than the renderer, is what the Hacker News thread spent its time on.

What the README says Rune is

Rune ships its own renderer, text, layout and spring-based motion rather than wrapping native widgets. A companion crate, rune-kit, supplies components, and the README links examples, docs and a changelog.

The feature aimed squarely at coding agents is headless mode. An app can run without a window, render to PNG, dump its element tree and take scripted input, so an agent can check what it built. The README suggests handing an agent the repository and starting from examples/hello.

Installation is a git dependency. Because the project is pre-release, the README says to pin a revision of the dev branch, and says dev is never rewritten. There is no tagged release to pin instead.

1. Stars2600 count
2. Forks61 count
3. Watchers8 count

Source: github.com/anomalyco/rune, accessed 2026-11-07

Stars measure interest, not use. Sixty-one forks and eight watchers is the more telling pair for a project this new.

Where the Hacker News thread split

The submission came from the user mik3y. The criticism fell into four groups, and The Terminal has not run the code to test any of it.

Argument	Who said it	What the thread shows
The code is low quality	rvz: "zero tests"	anentropic and wuliwong replied that tests exist
Tests are not enforced	esafak: "They ain't running in CI."	Not answered in the thread
Text will look blurry	piker: fonts "fuzzy on various platforms"	nicoburns: sharp fonts are achievable but "you certainly won't get it out of the box"
Accessibility	bhouston asked about screen readers	sarabarasa100 questioned putting agent access ahead of disabled users

nicoburns, who described himself in the thread as maintainer of Dioxus Native and the Blitz engine, told readers to "skip this vibe coded project" in favour of established toolkits. Another commenter accused him of self-promotion, and he replied that his recommendations were made in good faith.

The README sample does use role("switch") and a label on a toggle. The page excerpt read for this story does not state an accessibility status, so whether a screen reader can drive a Rune app is the open question, and nobody in the thread answered it from the code.

The no-pull-request policy

Commenters were divided on the policy. atrokhymchuk found it sad for people who write code by hand. kodablah argued that when most contributions are generated, the idea becomes the valuable part. CSSer warned that issue-driven agent workflows could be exploited for attacks, and bhouston replied that issues are easier to screen than pull requests.

The same worry about agents and untrusted input appears in other open-source tooling this site has covered: Stroq's audit of coding-agent sessions says plainly that it is a filter and not a sandbox, and the Claude Code email fix checks shell flags only.

What is still unknown

The README excerpt gives no individual author names; the license credits Anomaly. Several comparisons in the thread, to GPUI, Iced, egui and Slint, were opinions from users, not measurements. cute_boi predicted the project would not be maintained for long, a claim the repository's changelog will confirm or refute.

The next checkable fact is whether the first tagged release arrives, since until then every user is pinned to a commit of dev.