RepoYeti

LunarWerxs18stars

Run git from your phone, safely. A self-hosted daemon + mobile PWA for any git host (GitHub, GitLab, Gitea, Cloudflare Artifacts): live repo grid, git-graph history, Monaco diffs and AI Smart Commit,

Cloud Infrastructure

Install Run on PlugMCP

GitHub Website

Run on PlugMCP

1# RepoYeti

README.mdMCP server

Transport: stdio
Status: Local

Power your agent

Add this server

Install from the publisher. Not a PlugMCP endpoint.

Run on PlugMCP

Host a copy with our keys and logs.

No packaged release in the registry yet. Follow the repository README.

RepositoryPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Local

Transport: stdio
License: NOASSERTION
Last checked: 2026-10-28

Stars: 18
Tools: —
Uptime: —

Overview

About RepoYeti

Run git from your phone, safely. A self-hosted daemon + mobile PWA for any git host (GitHub, GitLab, Gitea, Cloudflare Artifacts): live repo grid, git-graph history, Monaco diffs and AI Smart Commit, with guardrails (no force-push, fast-forward-only pulls).

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

How do I install RepoYeti?

Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does RepoYeti need an API key?

No required environment variable is listed on this record.

What transport does RepoYeti use?

RepoYeti runs locally over stdio.

When was RepoYeti last checked?

Last checked 2026-10-28. Run git from your phone, safely. A self-hosted daemon + mobile PWA for any git host (GitHub, GitLab, Gitea, Cloudflare Artifacts): live repo grid, git-graph history, Monaco diffs and AI Smart Commit, with guardrails (no force-push, fast-forward-only pulls).

From the publisher

Documentation

Every git repo on your machine, on your phone.

A self-hosted git dashboard: one small daemon on your computer, a live status grid, commit graph and real Monaco diffs on any screen you own.

A remote git client for an Android phone, an iPhone or any browser, and a self-hosted stand-in for GitHub Desktop when you are not at the machine. It drives your real local repos against any git remote: GitHub, GitLab, Bitbucket, Gitea, Forgejo, Cloudflare Artifacts or your own server.

⬇ Download · repoyeti.com · Features · Install · FAQ · Changelog

TL;DR

📡 Every repo on the machine, live. Branch, dirty, ahead/behind for all of them, updating the moment something changes on disk. Fetch all in one tap.
🌿 A real commit graph, with lanes and merges, lazily paged, each commit carrying its files-and-lines delta. Drag it taller to read more at once.
🔍 Real Monaco diffs, the actual VS Code editor: syntax highlighting, HEAD-↔-tree comparison, edit and save from the phone.
👀 Look before you pull. The incoming commits, the files they touch and the conflicts they would cause, without fetching or merging anything.
🤖 Smart Commit (AI) turns a messy working tree into clean, scoped commits. Bring your own key; a free Groq one takes three clicks.
🛡️ No force-push, no reset --hard, no rebase. A phone is a bad place to rewrite history, so RepoYeti simply cannot.
🏠 Self-hosted, one file. No cloud account, no runtime to install, nothing written into your repos. Delete the binary and it is gone.

Download for your platform → One file. Point it at a folder, open the QR code on your phone.

Features


📡 Live repo grid	Every repository under your roots, with branch, dirty count, and ahead/behind. Driven by a filesystem watcher, so it reflects a commit you made in a terminal a second ago. Fetch all sweeps the set with per-repo progress and a Stop button
🌿 Git-graph history	Lanes, merges and tags, paged lazily so a 40,000-commit repo opens as fast as a new one. Each commit shows its touched files and line delta; a commit-activity chart sits above it. Resizable, because a phone screen is short
🔍 Monaco diffs	The real VS Code editor, not a re-implementation: syntax highlighting for everything it knows, side-by-side or inline, HEAD-↔-working-tree, and an editor you can save from
👀 Preview a pull	See the incoming commits, the files they touch, and any conflicts they would cause before you pull. Nothing is fetched, nothing is merged, nothing is written by looking
🤖 Smart Commit (AI)	Hands a messy working tree to your chosen model and gets back scoped commits with written messages, which you approve, edit or throw away. Also writes single commit messages and resolves conflicts. Groq, OpenAI, Claude, Gemini, OpenRouter and DeepSeek, under your own key
☑️ Bulk actions	Select any number of repos (Shift-click a range, Ctrl+A for all) and pin, star, hide, remove, pull or push them at once. Pin, star, hide and remove undo
🪪 Per-repo identities	The right name and email per repository, applied at commit time, with rules that match by path. No more `--amend --author` the next morning
🔐 Per-repo accounts	Multiple GitHub accounts, pinned per repository, so a push from the work repo uses the work credential and never silently uses the other one
☁️ Cloudflare Artifacts	Repos whose remote is on Cloudflare Artifacts push, pull and fetch with no token in the remote URL. Save one Cloudflare API token in Settings; each operation gets its own short-lived token for that one repo, read-only unless it pushes
📱 A real PWA	Install it to the home screen. It reconnects after the phone sleeps, survives a backgrounded tab mid-operation, and asks the daemon what happened rather than spinning forever
🌐 Private tunnel	`--tunnel` opens a Cloudflare tunnel and prints a QR code. Your dashboard and git traffic go through your own tunnel, not through us
🤝 Agents (MCP)	`repoyeti mcp` exposes your repos to an AI agent with an approval gate on anything that mutates, so the agent asks before it commits (or asks your own policy service, which can approve, deny or rewrite the call). The full HTTP surface is at `GET /api/openapi.json`
🛡️ Safe by construction	Force-push, `reset --hard` and rebase are not implemented, not hidden. Pulls are fast-forward-only and stop rather than merge when a branch has diverged
🏠 Self-hosted	A single compiled binary with the dashboard inside it. Local state lives in `~/.repoyeti/`; your repositories are never written to except by the git commands you ask for

One daemon, a whole workaround gone

Managing git on a machine you are not sitting at usually means assembling something: a VPN, an SSH client, a tmux session, a second git host. RepoYeti is one binary that makes the working tree you already have reachable from the device already in your hand.

Instead of...	You already have it
GitHub Desktop, on a machine you are not at	A dashboard for every repo on that machine, opened from anywhere, in a browser
The GitHub mobile app, which browses github.com but never touches your working tree	Your actual local working tree: real status, real diffs, real commits
Tailscale + SSH + tmux + vim to commit one file	A tap, a Monaco diff, a commit message, done
Standing up a self-hosted Gitea/Forgejo just to see repo status remotely	No second git host, no mirroring, no second copy of anything to keep in sync
A cron job that auto-commits and hopes for the best	Auto-commit that you can watch, with a diff you can read first
Writing commit messages on a phone keyboard	Smart Commit writes them, you approve them

Nothing is mirrored, uploaded, or re-hosted. RepoYeti shells out to the same git you already use, in the same working tree, as the identity you configured for that repository.

⭐ Like it? Help it grow

Built in the open, free for personal use, no ads, and a once-a-day version check you can switch off. If RepoYeti earns a place on your machine, a few seconds goes a long way:

⭐ Star the repo - the clearest signal that this is worth maintaining.
💬 Join the Discord - feature arguments, early builds, and somewhere to shout when something breaks.
🐛 Open an issue - a good bug report is worth more than a star. #24 traced a broken release to the exact commit and got two fixes shipped.

Install

Download your platform - repoyeti-windows-x64.exe, repoyeti-linux-x64.tar.gz or repoyeti-macos-arm64.tar.gz.
Run it. The dashboard is compiled into the binary, so there is no web or node_modules folder to keep beside it.

repoyeti add-root ~/code   # point it at where your repos live
repoyeti start             # daemon on 127.0.0.1:7171

To reach it from your phone, which opens a Cloudflare tunnel and prints a QR code:

repoyeti start --tunnel

The tray icon comes with both downloads. The icon is drawn by a small separate launcher (misc\RepoYeti-Tray.exe); the zip ships it beside the exe, and since 1.0.2 the single-file repoyeti.exe carries it inside the binary and writes it out beside its own state on first run, so either download gets you the icon, Quit and the auto-restart supervisor. (Before 1.0.2 the bare exe had none, and this line said so as though it were a decision.) misc\Create-Shortcut.ps1 still makes a shortcut that launches through the tray host directly.

Signed. Starting with 1.0.1 the Windows executable, the tray launcher and the tray scripts are Authenticode-signed as LUNARWERX LLC through Azure Trusted Signing, and timestamped, so Windows names the publisher instead of warning about an unknown one. SmartScreen still rates new signing identities on reputation, so a very early download may show a prompt that now says who published it. Every release also publishes a SHA256SUMS.txt.

--tunnel needs cloudflared on PATH; it is not bundled, in a release or a clone. Check with cloudflared --version. If it is missing, RepoYeti says so and keeps serving locally. Sign-in over a tunnel returns through RepoYeti's registered callback at app.repoyeti.com; your dashboard and git traffic never pass through it. See Remote access.

Release binary vs. running from a clone

	Release binary	Clone
Single file, nothing beside it	✅	❌ (daemon deps + dashboard deps)
Dashboard already built in	✅	❌ (`bun run --cwd web build:fast` once)
Automatic self-update	✅	✅ (pulls and rebuilds)
Optional system-tray icon	✅ (the `-with-tray` zip)	❌
Needs Bun ≥ 1.1 installed	❌	✅
Edit the source and see it live	❌	✅

git clone https://github.com/LunarWerxs/RepoYeti.git
cd RepoYeti

bun run install:all             # daemon deps + dashboard deps (web/ is a separate package)
bun run --cwd web build:fast    # compile the dashboard into web/dist

bun run src/index.ts add-root ~/code
bun run src/index.ts start

The repo has two dependency sets and the dashboard is compiled into the release rather than committed, so a fresh clone has to build it once. Without that step the daemon starts and serves web app not built.

Update cooldown. Set autoUpdateCooldownDays (0 to 30, through PUT /api/settings or ~/.repoyeti/config.json) and the auto-update timer only announces or installs an update at least that many days old: a release's GitHub publication date, or a clone's newest remote commit date. A bad or compromised release then has that long to be caught before your machine takes it. A manual check or install ignores it. A clone waits for the branch tip itself to age, so a branch that moves every day never clears a long cooldown.

AI setup: a free Groq key in 3 clicks

Smart Commit and AI commit messages are bring-your-own-key. There is no bundled key, because Groq revokes any key committed to a public repo. Groq is the suggested provider: free, fast, about thirty seconds.

Open console.groq.com/keys and sign in.
Click Create API Key, then Copy.
In the app, open Settings → AI, expand Groq, and paste it in.

"Generate" lights up right away. Prefer OpenAI, Claude, Gemini, OpenRouter or DeepSeek? Add that key in the same place instead. Your key never leaves the daemon; it is kept in your OS keychain and sent only to the provider it belongs to.

How it works

   your phone  ──HTTPS──►  Cloudflare tunnel  ──►  ┐
                                                   │
   your browser  ────────────────────────────────► ├──►  repoyeti daemon
                                                   │      127.0.0.1:7171
   an AI agent  ──MCP (approval-gated)───────────► ┘      (one compiled binary,
                                                          dashboard embedded)
                                                              │
                                        bun:sqlite  ◄─────────┼─────────►  simple-git
                                     (~/.repoyeti/)           │           (your real git)
                                                              ▼
                                                    your working tree,
                                                    exactly where it already is

Bun, bun:sqlite, Hono and simple-git on the daemon; a Vue 3 + Tailwind PWA on the front end, compiled into the binary. Sign-in is "Sign in with Connections" (OIDC / PKCE, zero setup) and is entirely optional. A pluggable VCS backend also supports Lore behind REPOYETI_LORE=1.

The rules

No force-push, no reset --hard, no rebase - those live at your desk. Pulls are fast-forward-only. Everything runs as the git identity you set for that repository. Local state stays in ~/.repoyeti/; nothing is written into your repos.

Privacy

Nothing is mirrored or uploaded. Git traffic goes to your own remotes with your own credentials, and cloud sign-in and settings sync are off by default - core git management works fully self-hosted and offline, with no LunarWerx account.

The daemon pings Connections Studio for update checks, at most once a day. That ping carries a random install id, the running version, and a coarse OS tag (e.g. win11-26100). From that request the server also derives and stores a coarse location (country, region, city, timezone), your network's ASN, locale, and a truncated user agent - but never an IP address. It never sends a hostname, username, file path, account, or anything about your repos.

Set REPOYETI_NO_PING=1 to opt out entirely.

If you use AI Smart Commit, AI commit messages or AI conflict resolution, the changed file list and diff (or the conflicted text) goes to the AI provider you configured, under your key, and only when you press the button. Optional settings sync sends dashboard preferences - never code, credentials or paths - to Connections.

AI agents (MCP): repoyeti mcp exposes local repos, a blame-based "which unpushed commit does this change fix?" lookup (fixup_base), accepted collaboration status/diffs and guarded remote commit+sync; the full HTTP surface is at GET /api/openapi.json.
Buzz (experimental, Advanced): opt-in Git Smart HTTP compatibility, saved communities, and daemon-safe preflight diagnostics. Setup and security boundaries.
Open a local dev server from your phone (opt-in): turn on portProxy and /proxy/<port>/ opens whatever is listening on that port through the dashboard's own sign-in, owner only. How it is fenced.
Architecture, remote access, config: docs/ARCHITECTURE.md
Contributing & tests: docs/CONTRIBUTING.md
Working here with an AI agent: AGENTS.md - repo map, the enforced guardrails, and the traps that have cost a release.

FAQ

Free to download, self-host and run for any purpose the PolyForm Noncommercial License 1.0.0 permits - personal projects, research, education, and non-profit use.

Commercial use needs a licence: US$79 per installation, meaning per machine running the daemon (the phones and browsers you read it on are not counted). It is perpetual and includes 12 months of updates; after that your copy keeps working and new builds need a renewal. Checkout is handled by Connections, so that is the name on the receipt. Volume pricing for a team is available - ask on Discord. Full terms: repoyeti.com/pricing.md.

Nothing is ever time-limited or feature-gated, in either case. Your chosen AI provider may charge for Smart Commit usage.

Yes, for local repo work. Browsing repos, reading commit history and diffing need no internet connection and no account. Fetching or pushing still needs whatever network access that remote requires, and reaching the dashboard from your phone needs a Cloudflare tunnel.

Prebuilt binaries cover Windows, Linux, and macOS on Apple Silicon. On Windows the release is a single .exe with no runtime to install, plus an optional system-tray build. Running from a clone instead needs Bun 1.1 or newer and git on PATH. Remote phone access additionally needs cloudflared installed separately; RepoYeti detects and reports if it is missing.

GitHub Desktop is a desktop app, not something you open on a phone. The GitHub mobile app browses and reviews repos hosted on github.com, but never drives git in a local working tree. RepoYeti runs on your machine, shells out to your real local git via simple-git, and puts that same working tree on your phone.

Not to us. Git traffic goes to your own remotes with your own credentials. AI features send the diff to the provider you configured, under your key, only when you trigger them. Beyond that there is a once-a-day anonymous version check - see Privacy for the exact contents and the opt-out.

Some key is required, since RepoYeti ships none (Groq revokes any key committed to a public repo). Groq is free and takes about three clicks from Settings → AI. OpenAI, Claude, Gemini, OpenRouter and DeepSeek work too. Keys live in your OS keychain, are never shown to the dashboard, and are sent only to the provider they belong to.

By design. Force-push, reset --hard and rebase are not implemented at all - a phone is a bad place to rewrite history, and an accidental tap there is unrecoverable. Pulls are fast-forward-only and stop rather than merge when a branch has diverged. None of this limits your desktop git client; RepoYeti just will not run those commands remotely.

What it does offer for a wrong tap is Undo last git action (the repo card's ⋮ menu, or repoyeti undo|redo <repo> [--dry-run]). It reads the repository's reflog, so it also covers a commit or pull made outside the app: a branch switch is switched back, a commit is stepped back with its changes left staged, and a pull is stepped back only when no uncommitted edit would be touched. A commit that is already on a remote, or a rebase or cherry-pick, is refused rather than undone.

Yes, from 1.0.1 onward. repoyeti.exe, the tray launcher RepoYeti-Tray.exe and the tray PowerShell scripts are Authenticode-signed as CN=LUNARWERX LLC through Azure Trusted Signing and RFC-3161 timestamped, so the signature stays valid after the (deliberately short-lived) certificate expires. Right-click the exe, Properties, Digital Signatures to see it.

Signing is about who published the file. Integrity is handled separately and was already in place: every release publishes SHA256SUMS.txt, and the automatic updater fetches that manifest first, refuses a release that has no verifiable checksum, stream-hashes the download and deletes it on mismatch, and makes the new binary report the expected version before swapping it in.

More from LunarWerx

RepoYeti is one of the developer tools LunarWerx Studios builds. These are on GitHub too, most of them free for personal use and running on your own machine:

Product	What it does	Links
AgentHydra	Every local AI coding session in one tab: Claude Code, Codex and OpenCode, with each account's usage and a queue you can schedule	site · GitHub
DevWebUI	Start, stop and watch every local dev server across your projects, from a dashboard or an MCP server an AI agent can drive	site · GitHub
ReDesign	Drop in a UI screenshot and get self-contained HTML redesigns from ten AI models at once	site · GitHub
SageThumbs 2K	Windows Explorer thumbnails and previews for 360+ file types Windows can't show, from a crash-isolated Rust shell extension	site · GitHub
NormWind	A zero-config CLI and GitHub Action that rewrites bloated Tailwind CSS classes into canonical ones	site · GitHub
AnatomyOf	An interactive, annotated tour of what is actually inside a source file, for 48 languages	site · GitHub
QuickDictate	Hold a hotkey, speak, and it types into whatever Windows app has focus	site · GitHub
PyOverdrive	A drop-in NumPy accelerator: `enable()` swaps in proof-tested fast paths, call by call	GitHub

Everything else is at lunarwerx.com and github.com/LunarWerxs.

Credits

Monaco for the diffs · Bun and Hono for the daemon · simple-git for every git call · Vue 3 and Tailwind for the dashboard · cloudflared for the tunnel · file-type icons from vscode-icons (artwork under CC BY-SA).

License

PolyForm Noncommercial 1.0.0 © LunarWerx Studios, starting with RepoYeti 1.0.0. The source is available and free for noncommercial use; commercial use is US$79 per installation (buy · terms). Earlier MIT grants remain in effect for earlier copies - see licensing details.