e2e-test
Skill2.4k starsChanged todayApache-2.0View on GitHub
Run Muxy's end-to-end release tests in fresh SwiftVM guests (macOS, Ubuntu Wayland, Ubuntu X11), driven visually by parallel low-cost tester subagents. Use before a release, after a risky change, or when the user runs /e2e-test [macos|wayland|x11|linux].
27 other projects use a version of this.
Trending
More talk lately.about the whole repository
Most recently taken up by
- eyssette/js-templatetheir own version, first seen Nov 1, 2026
- korya/swd-skillstheir own version, first seen Nov 1, 2026
- liaohch3/claude-taptheir own version, first seen Oct 25, 2026
- maximhq/bifrosttheir own version, first seen Oct 20, 2026
- DongDuong2001/pudo-code-systemtheir own version, first seen Oct 13, 2026
- Vasallo94/Claquetatheir own version, first seen Oct 13, 2026
Who's talking about muxy-app/muxy
- A Hacker News story“Muxy is a lightweight terminal for Mac with a mobile app for remote control”Hacker News · May 20, 2026 · 3 points
- A Hacker News story“Muxy – A macOS terminal built with SwiftUI and libghostty”Hacker News · Apr 22, 2026 · 3 points
- @tom-doerr.bsky.social“https://github.com/muxy-app/muxy”Bluesky · Apr 20, 2026 · 1 likes
- A Hacker News story“Ghostty, but with Vertical tabs, lightweight and native”Hacker News · Apr 3, 2026 · 1 points
- sudosubin/agents.nix“agent-skills.github.muxy-app.muxy: 2.3.0 → 2.4.0”GitHub · Nov 7, 2026
The biggest 5 of 19 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 19
Talked about on GitHub, Hacker News and Bluesky (19 times).
On GitHub · 15
- Nov 7, 2026agent-skills.github.muxy-app.muxy: 2.3.0 → 2.4.0 — sudosubin/agents.nix0 reactions
- Oct 31, 2026agent-skills.github.muxy-app.muxy: 2.2.0 → 2.3.0 — sudosubin/agents.nix0 reactions
- Oct 29, 2026Add Muxy — AppImage/appimage.github.io0 reactions · 1 comment
- Oct 17, 2026agent-skills.github.muxy-app.muxy: 2.1.0 → 2.2.0 — sudosubin/agents.nix0 reactions
- Oct 14, 2026wr-agent: page scrollback to reattaching clients instead of repainting it whole — joelmoss/workroom0 reactions · 3 comments
10 more on GitHub
- Oct 14, 2026agent-skills.github.muxy-app.muxy: 0-unstable-2026-08-28 → 2.1.0 — sudosubin/agents.nix0 reactions
- Oct 3, 2026agent-skills.github.muxy-app.muxy: 1.6.1 → 0-unstable-2026-08-28 — sudosubin/agents.nix0 reactions
- Sep 30, 2026agent-skills.github.muxy-app.muxy: init at 1.6.1 — sudosubin/agents.nix0 reactions
- Jul 29, 2026Feature Request: Native Terminal AI Agent Support (ACP Integration & Third-Party CLI Orchestration) — github/app0 reactions · 3 comments
- Jul 10, 2026github 0.1.1 — muxy-app/extensions0 reactions · 6 comments
- May 26, 2026Fix Pi notification pill showing wrong provider name — maxschulmeister/muxy0 reactions
- May 21, 2026https://github.com/muxy-app/muxy — weihubeats/Asuna0 reactions · 1 comment
- May 14, 2026Custom project picker for adding/opening projects — sadiksaifi/muxy0 reactions
- Apr 11, 2026佈局持久化(Daemon Layout API + Restore Reconciliation) — zac15987/zplex0 reactions · 3 comments
- Apr 6, 2026Add Muxy to Terminal section — iCHAIT/awesome-macOS0 reactions · 1 comment
On Hacker News · 3
- May 20, 2026Muxy is a lightweight terminal for Mac with a mobile app for remote control3 points
- Apr 22, 2026Muxy – A macOS terminal built with SwiftUI and libghostty3 points · 1 comment
- Apr 3, 2026Ghostty, but with Vertical tabs, lightweight and native1 point · 1 comment
On Bluesky · 1
- Apr 20, 2026https://github.com/muxy-app/muxy — @tom-doerr.bsky.social1 likes and repost
Used with
Projects with it also use unit-test, design-md and 6 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
kevinaimonsterSkillunit-test
单元测试生成助手。帮用户编写单元测试、集成测试、Mock 设计、测试覆盖率提升。当用户说「帮我写单元测试」「写个测试用例」「怎么测这个函数」「mock怎么写」「测试覆盖率」「写测试」「unit test」「test case」「jest测试」「pytest」「vitest」「testing」时触发。关键词:单元测试、测试用例、测试覆盖率、mock、stub、spy、jest、pytest、vitest、mocha、junit、testing-library、断言、边界测试、异常测试、集成测试、e2e测试、测试驱动、代码覆盖率、coverage、test runner、describe、it、expect、assert、fixture、parametrize、测试金字塔
Also in 4 projects that use this
klauswgSkilldesign-md
Analyze Stitch projects and synthesize a semantic design system into DESIGN.md files
Also in 3 projects that use this
HashiCorpSkillchangelog
Add a `.changelog/<PR_NUMBER>.txt` entry for a GitHub Pull Request, commit, and push.
Also in 3 projects that use this
MicrosoftSkillplaywright-cli
Automate browser interactions, test web pages and work with Playwright tests.
Also in 3 projects that use this
BlockSkillplan
Draft a TDD, PRD, or lightweight plan in the conversation without committing it.
Also in 3 projects that use this
GoogleSkillimprove-codebase-architecture
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
Also in 3 projects that use this
Other versions27 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 27
- metabase/metabase★ 50ksame name
- dataelement/bisheng★ 12ksame name
- maximhq/bifrost★ 9.6ksame name
- liaohch3/claude-tap★ 3.3ksame name
- Nexus-Mods/Vortex★ 1.6ksame name
- nwiizo/tfmcp★ 373same name
- divinevideo/divine-mobile★ 265same name
- rabble/nostrvine★ 265same name
- coleam00/link-in-bio-page-builder★ 229same name
- bifrost-proxy/bifrost★ 168same name
17 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository8 other files it gives its agents.
- AGENTS.mdAGENTS.md
- code-and-architecture-improvementSkill
- implementSkill
- issues-triageSkill
- release-highlightsSkill
- report-taskSkill
- reviewSkill
- visual-testingSkill
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 4 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 23 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 20
Read first: docs/product/README.md, docs/tech/README.md, and the tester protocol (you hand it to every tester).
- Distinctive: line 76
Never let two testers touch the same VM at once.
- Very specific: line 89
Start batch A for every platform in one message.
- Very specific: line 111
Read the summary block. Any FAIL, BLOCKED or INSTRUCTION row needs your review.
- Distinctive: line 146
Ask the user before cleaning up: Ask whether they want any of the run's VMs kept to inspect a failure or reproduce a fix, and wait for the …
- Distinctive: line 151
Clean up: When the user is done, delete every VM of the run and confirm none are left:
- Very specific: line 184
Not covered: remote servers and pairing (need a second machine), mobile, muxy worktree checkout-pr (needs a GitHub remote), Quick Terminal …
- Distinctive: line 192
Write steps a model can follow without judgment: one action per step, exact keys for both platforms, an exact expected result, and a check …
“Common” is measured: kept by at least 6 in 10 of the 23 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Muxy E2E tests
You are the coordinator. You never drive a VM yourself. Low-cost tester
subagents boot the guests, build the current working tree, and run the
suites in suites/ through Agent Desktop (keys, typing, clicks, screenshots)
and Muxy's CLI. You plan the run, dispatch testers, review their evidence,
and report.
Other skills reuse this harness for one scenario: write the steps as a suite file in the same format, and hand it to testers with the prompt in step 4. The tester protocol carries every rule for driving the VM, including Agent Desktop, so don't write VM rules into a tester's prompt.
Read first: docs/product/README.md, docs/tech/README.md, and
the tester protocol (you hand it to every tester).
1. Scope
| Argument | Platforms |
empty, all | macos, wayland, x11 |
linux | wayland, x11 |
macos, wayland, x11, windows | that one |
Anything else: stop and show this table.
2. Prepare (host only, two commands)
.agents/skills/e2e-test/scripts/e2e preflight
.agents/skills/e2e-test/scripts/e2e prepare # prints the run id, e.g. r10302015preflight fails when a template is missing: follow
references/templates.md before testing. It also
fails when the host DHCP pool for SwiftVM is full. Each new VM takes a lease,
and macOS never gives an expired lease to a new MAC, so the pool runs out after
about 250 VMs. A guest then gets no IPv4 address, and its build can't reach
github.com. Ask the user to run e2e dhcp-prune in their own terminal, because
it needs sudo. up also stops with ENV: when a guest has no network. up
also fails with ENV: when Agent Desktop is missing, not ready, or can't
take screenshots in the clone; that is a template defect, fixed by
refreshing the template. If preflight lists VMs from an earlier run, ask
the user whether to clean them up (e2e clean <old run>) before starting;
they hold host memory and disk.
prepare exports the working tree (tracked edits and new files included) to
target/e2e/<run>/source.tar; prepare <run> <checkout> exports another
checkout, such as a worktree. If you edit source later, run a new
prepare and a new run; never mix sources within a run.
3. Pick the tester model
Choose the cheapest model that has a shell and can read PNG images; the tests are mechanical and need no reasoning beyond comparing what is seen with what is written. Prefer, in order:
| Harness | Tester |
| Claude Code | model: "haiku" on a general-purpose subagent |
| Codex / ChatGPT agents | gpt-6-luna (or the cheapest listed mini model), low reasoning effort, fork_turns: "none" |
| Anything else | the cheapest available model that has shell and image input |
Set the model per subagent; never change the user's global settings. If no cheaper model exists, use your own model for testers, but still delegate.
4. Dispatch
Each platform has its own VM and runs its batches in order; the three platforms run in parallel. One tester per batch, fresh context each time. Never let two testers touch the same VM at once.
| Batch | Suites | Notes |
| A | boot, S01, S02 | Boots the VM with e2e up |
| B | S03, S04 | |
| C | S05, S06 | |
| D | S07, S08 | |
| E | S09, S10 | |
| F | S11 | |
| G | S12, S14 | Terminal UI and terminal images |
| H | S13, S15 | Extensions, AI and agent dialogs, language packs |
Start batch A for every platform in one message. When a platform's batch
finishes, start that platform's next batch right away; don't wait for the
other platforms. If batch A reports BOOT: FAIL, stop that platform. However
a run ends, finish with step 6.
Give each tester exactly this prompt, filled in:
You are a Muxy E2E tester. Work only through the commands in the tester protocol.
Read and follow: .agents/skills/e2e-test/references/tester.md
Run id: <run> Platform: <macos|wayland|x11|windows> VM: muxy-e2e-<run>-<platform>
Batch: <A-F> Boot first: <yes for batch A, otherwise no>
Suites, in order: .agents/skills/e2e-test/suites/<file>.md, ...
Return your report as your final message.
Do not spawn agents, edit repository files, or debug Muxy's source.5. Review
Testers' verdicts are evidence, not conclusions. Save each returned report
as target/e2e/<run>/<platform>/report-<batch>.md. For every report:
- Read the summary block. Any
FAIL,BLOCKEDorINSTRUCTIONrow needs your review; aPASSrow with no evidence path is treated asBLOCKED. - For each problem row, open its screenshots and log excerpts yourself and
classify it:
- Product bug: Muxy behaved against the suite's expectation and the docs. Keep it.
- Environment: VM, template, or tooling failure. Fix the template or script if it is routine (see templates.md), otherwise report it.
- Test defect: the suite's steps or expectation are wrong. Fix the suite after the run, and say so in the final report.
- Flaky: re-run only that test once with a new tester (same VM, after its batch) and keep both results.
- Spot-check one
PASSscreenshot per suite to keep testers honest.
6. Finish (mandatory)
A run is not finished until its VMs are gone. Do these steps in order, every time, even when the run failed or was stopped early.
Stop the VMs. Once every batch has reported, stop each platform's VM. This keeps its disk for inspection and frees the host:
.agents/skills/e2e-test/scripts/e2e down muxy-e2e-<run>-<platform>- Report to the user:
- Source: commit, dirty file count, archive digest (
target/e2e/<run>/source.txt). - A platform × suite table: pass / fail / blocked counts.
- Each confirmed product bug: test id, platform(s), expected vs actual, the key screenshot and log paths, and how reproducible it was.
- Environment problems and test defects, separately, with what you changed.
- What is not covered (see the coverage table below).
- The run's VMs, from
e2e vms <run>.
- Source: commit, dirty file count, archive digest (
- Ask the user before cleaning up. Ask whether they want any of the run's VMs kept to inspect a failure or reproduce a fix, and wait for the answer. Don't delete anything before they reply. If they want some kept, say which VMs remain and ask again once they say they are done.
Clean up. When the user is done, delete every VM of the run and confirm none are left:
.agents/skills/e2e-test/scripts/e2e clean <run> .agents/skills/e2e-test/scripts/e2e vms <run>cleancopies the logs intotarget/e2e/<run>/first, so the evidence stays. Tell the user the VMs are deleted (they are in the Trash). Delete only this run's VMs; never another run's, a template, or a VM the run didn't create.
Coverage
| Suite | Feature |
| S01 | Build identity, first launch, server auto-start |
| S02 | Terminal I/O, Unicode and color, Ctrl+C, scrollback, find, paste, shell integration, copy, font size |
| S03 | Splits, focus, zoom, close confirmation, tabs, rename, detach and Existing Terminals |
| S04 | Add project, Git status, CLI sessions in the app, rename, switch, delete |
| S05 | Terminals outlive the app, restore on launch, server stop and reconnect, End All Sessions and Quit |
| S06 | CLI input into a visible terminal, terminal UI, shared sessions, program status, agent activity |
| S07 | Project layouts, worktrees from CLI and UI |
| S08 | Settings window, saved preferences, theme picker, sidebar, command palette |
| S09 | Built-in browser, CLI automation, address bar, back |
| S10 | Composer send |
| S11 | Worktrees end to end: discovery, form and CLI creation, setup and teardown commands, location templates, register, switch, rename, dirty and clean removal, lost folders, hiding, removing the parent |
| S12 | Terminal UI: isolated server, idle output limit, splits, suspend and resume, detach and restore, resize, two windows sharing one layout |
| S13 | Extensions: store listing, load, enable, panel, reload, broken package, disable and unload, floating panels |
| S14 | Terminal images: Kitty, iTerm and Sixel, file and temp-file transfers, the named-pipe guard, DA1, restore after restart, scrolling |
| S15 | Commit dialog, Create Extension with an agent, Linux install of the muxy command, symbol language packs |
Not covered: remote servers and pairing (need a second machine), mobile,
muxy worktree checkout-pr (needs a GitHub remote),
Quick Terminal (needs a recorded global shortcut), dictation, extensions
marketplace (network), updates, AI commit/PR (needs signed-in tools),
Windows.
Changing the suites
Write steps a model can follow without judgment: one action per step, exact
keys for both platforms, an exact expected result, and a check that doesn't
rely on typed text (see "Markers" in the tester protocol). Click with
$E click-element $VM <name>, using the control's accessible name (its
aria_label, or the English text of its tr! label), and use $E click only for what
isn't a control, saying why in that step. Never click by accessibility ID
(project-row-alpha, settings-toggle-...): swiftvm control reports only each
control's role, name and position, not Muxy's IDs, so an ID never matches. When
a name repeats, add --role <role> (as look prints it: button, toggle,
textfield, item, tab, ...; use the Linux names: toggle also
matches macOS's checkbox, and tab also matches macOS's radio) or --nth <n> (the nth match in tree order),
and say in the step why. --right finds the control by name and right-clicks it with the
pointer. click-element fails and lists the matches when a name is ambiguous. For a native dialog on macOS, ask
for $E desktop $VM look --app muxy-app as well as a shot (swiftvm control
has no snapshot action). Verify new steps
in a guest before committing them. Keep references/tester.md the single
place for shared rules.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

