Safety

Your repositories are the one thing here that is genuinely irreplaceable. Meshvy treats them as read-only except where you have explicitly said otherwise, and there are only two places where that applies.

What it never does

• push
• merge
• rebase
• rewrite history
• commit for you

The guarantees behind that

• Two write commands, both of which you ask for

  The only git that writes is worktree add and worktree remove. Everything else Meshvy does to a repository is reading.

• Inspection never contends with an agent

  Reads run with GIT_OPTIONAL_LOCKS=0, so looking at a tree cannot block the agent working in it — or be blocked by it.

• Closing a workspace keeps its checkouts

  Archiving takes it off the board and leaves every worktree registered and every branch where it is. Deleting is a separate choice, and it asks.

• The uninstaller refuses to lose work

  It leaves alone any checkout holding uncommitted or unpushed work, and tells you which and why.

What an agent can still do

Meshvy does not write to your repositories, but the agents it runs are Claude Code, and they do what Claude Code does: edit files, run commands, and commit if you have asked them to. The permission mode on an agent card is what governs that, and it is fixed when the session launches — ⇧⇥ cycles it inside the session, or restart the agent from the same menu.

Licence

Source-available, not open source. You may run Meshvy and fork or modify it for your own use, including at work — you may not redistribute it or a derivative, or offer it to others as a service. The full terms are in the LICENSE.