mutagen-remote-workflow

Automate local editing and remote builds with Mutagen sync and rexec execution.

1|Updated Dec 5, 2025
One-click install
npx skills add https://github.com/dukebw/dotfiles --skill mutagen-remote-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mutagen-remote-workflow
Source: https://github.com/dukebw/dotfiles/tree/main/.claude/skills/mutagen-remote-workflow
Command: npx skills add https://github.com/dukebw/dotfiles --skill mutagen-remote-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill enables developers to maintain a fast local editing experience while performing remote builds and execution on Coder workspaces using Mutagen file syncing. It eliminates latency when editing locally and simplifies the workflow for building GPU-enabled code remotely.

Core Features & Use Cases

  • Low-latency local editing: Edit with Neovim locally while syncing changes to a remote workspace.
  • Remote build & execution: Run builds/tests on remote GPUs within Coder workspaces.
  • One-way sync + quick commands: Use a simple wrapper and rexec tool to flush and run commands remotely with minimal setup.
  • Use Case: A developer iterates on a kernel, edits locally, then triggers a remote Bazel build and GPU tests without SSH back-and-forth.

Quick Start

Use mutagen to start syncing, then utilize the ./r wrapper or rexec tool to run remote commands. Example: mutagen project start; ./r ./bazelw build //path:target; rexec hostname

Frequently Asked Questions about mutagen-remote-workflow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I edit locally with Neovim but run builds on a remote GPU?

You can edit locally with Neovim and run builds on a remote GPU by using Mutagen file sync to push changes to a Coder workspace, then executing remote commands with the rexec helper tool.

What is the best way to automate remote builds without SSH back-and-forth?

Automating remote builds without constant SSH back-and-forth is best achieved by combining Mutagen file synchronization with the rexec remote execution tool to flush changes and trigger commands on a Coder workspace.

How does Mutagen file sync work with Coder workspaces for remote development?

Mutagen file sync works with Coder workspaces by continuously synchronizing your local files to the remote environment, allowing you to maintain a low-latency local editing experience while executing builds remotely.

Do I need Mutagen and SSH access to use remote build workflows?

Yes, you need Mutagen for file synchronization, the rexec helper, an r wrapper for flush and exec, and configured SSH access to Coder workspaces to enable seamless local editing and remote builds.

Can I trigger remote Bazel builds and tests from my local machine?

Yes, you can trigger remote Bazel builds and tests from your local machine by using the provided ./r wrapper or rexec tool to execute commands on the remote Coder workspace after Mutagen syncs your changes.

What are the limitations of one-way file sync for remote development?

One-way file sync focuses on pushing local changes to the remote Coder workspace for execution, meaning it is optimized for local editing and remote builds rather than bidirectional file synchronization.