DEDUPED Hot AI repos, turned into use cases Get the Monday 5

How to check and fix self-hosted runners across your machines with Muxin

See which runners are busy, idle or offline, then install or restart them from one place.

Short answer: Run muxin --demo to explore simulated machines first; nothing real is touched; then run muxin add-machine --name "Mac Studio" --host [email protected] to add a real machine; run muxin watch acme to see live runner status and jobs for the acme org. All steps.

Authorization notice. Muxin is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.

Credentials. Installing runners registers them with your GitHub organization, so use an account and org you control and keep ssh keys limited to machines you own.

Who it is forA developer or DevOps engineer who runs GitHub self-hosted runners on several machines and gets jobs stuck in the queue.

The problemRunners on different machines fail quietly, and it is hard to tell which one is offline or which queued job no runner can take.

The outcomeYou see the state of every runner and the queued jobs no runner can take, and you can install, start, stop or remove runners on the machine you pick.

What you need first

  • A Mac, Linux or Windows 11 machine to run Muxin on, with the app installed from the latest release or built from source
  • SSH access to each target machine using your system ssh, keys or ~/.ssh/config aliases
  • A GitHub login through the gh tool if you want GitHub inbox, issue and runner features
  • For self-hosted runners, a GitHub organization you can register runners with

Steps

  1. Run muxin --demo to explore simulated machines first; nothing real is touched.
  2. Run muxin add-machine --name "Mac Studio" --host [email protected] to add a real machine.
  3. Run muxin watch acme to see live runner status and jobs for the acme org.
  4. Run muxin install mac-studio --count 2 to install two runners registered with acme as services.
  5. Run muxin status and check that each runner shows as working, idle or offline.

Prompt for your agent

Using the Muxin repo at LumaryLabsLLC/muxin, add the machine <machine-host> with the Muxin CLI, then run `muxin status` and report which runners are working, idle or offline. Verify that the output matches what the Overview and Jobs pages show in the app.

Caveat. Muxin reaches machines first with your system ssh, so each machine must accept your ssh key before any runner command can work.

Use this in your AI agent

Ask your agent

Using the Deduped MCP, get the setup steps for LumaryLabsLLC/muxin and "Check and fix self-hosted runners across your machines"

Add Deduped to Claude Code once

claude mcp add --transport http deduped https://dedupedai.com/mcp

Cursor, ChatGPT, others

Share: X LinkedIn Hacker News Email Copy link

Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer