RepoFox
Download VSIX
NewOpenAI Build Week · Developer Tools

Branch to PR
in one click

RepoFox kills the 20-minute Git grind. Branch, commit, push, and open a PR — one keystroke, done.

Download VSIXSet up locally →
VS Code 1.85+ · install without rebuilding the repository
Your workflow, visualized
feat/authadd loginfix/tokensmain✓ Draft readyyou approve ↑
VS Code
single supported surface
Review
before every mutation
History
persisted locally

Use RepoFox where you work

Visual Studio Code
REPOFOX
Branch → PR
groq · llama-3.3-70bfeat/auth
Operations history
Branch created
feat/add-jwt-middleware
Staged 3 files
auth.ts · middleware.ts
Committed
feat(auth): add JWT…
Pushed → origin
feat/add-jwt-middleware
src/auth/middleware.ts
1 import { verify } from 'jsonwebtoken'
2 import type { Request, Response, NextFunction }
3
+ 4 export function jwtMiddleware(
+ 5 req: Request, res: Response, next: NextFunction
+ 6 ) {
+ 7 const token = req.headers.authorization
+ 8 if (!token) return res.status(401).json({})
+ 9 try { verify(token, process.env.JWT_SECRET!)
10 next()

RepoFox in VS Code

The full branch → PR pipeline lives in the VS Code sidebar. One click. AI names the branch, writes the commit, opens the PR. Every step is recorded in Operations History with a revert button.

Download VSIXView on Marketplace →

Finish the change. RepoFox prepares it for review.

A guided Git workflow inside VS Code that keeps you in control from branch name to editable PR draft.

The pipeline

Every step is shown. Every step is snapshotted.

01
Build context from git historyAI
02
Suggest branch name from conventionsAI
03
Stage files and generate commitAI
04
Safe push with --set-upstream
05
Open an editable PR draftAI
Result
PR draft ready · review in VS Code Markdown editor
Operations History
Every step · snapshotted mid-session
Branch created
feat/add-jwt-middleware
Staged 3 files
auth.ts · types.ts · middleware.ts
Committed
feat(auth): add JWT middleware
Pushed
feat/add-jwt-middleware
PR draft ready
review before explicit submit
Snapshot storage
.git/refs/repofox/snapshots/
Context-aware AI

Learns how your team names branches and commits.

RepoFox reads your last 50 commits, 10 branch names, and recent PR titles before making any decision. It doesn't use a generic template — it pattern-matches against your actual repo history. The longer you use it, the better it gets.

repofox · context
# Reading repo history...
✓ Last 50 commits loaded
✓ Branch patterns: feat/, fix/, chore/
✓ PR style: conventional commits
→ Generating branch name...
feat/add-jwt-middleware
→ Generating commit message...
feat(auth): add JWT middleware and type guards
Snapshot system

Every step is snapshotted.

RepoFox captures a snapshot before every git mutation. Revert is available during an active session; support for reverting completed sessions is in progress.

Pre-branch snapshot
a3f2c1b4…
12:34:01
Pre-commit snapshot
b9e8d7c6…
12:34:18
Pre-push snapshot
c7d6e5f4…
12:34:22
Pre-PR snapshot
d8e7f6g5…
12:34:29
During an active session → restore branch ref + index + working tree from a snapshot
Privacy-first

Your code never touches a RepoFox server.

RepoFox is BYOK — Bring Your Own Key. Your API key is stored in your OS keychain (macOS Keychain, Windows Credential Manager, libsecret on Linux). All AI calls go directly from your machine to Groq, OpenAI, or Anthropic. No proxy. No logging. No trust required.

Your machine
Groq / OpenAI / Anthropic
AI calls direct
Your machine
GitHub API
PR creation direct
API keys
OS Keychain
Never on disk
RepoFox servers: not in the data path

Questions

RepoFox supports VS Code 1.85 and later, a Git repository, and an API key for an AI provider you choose. The extension stores keys in VS Code SecretStorage.

No. RepoFox can guide branch, commit, and push without one. A GitHub token is needed only when you want RepoFox to create a pull request.

RepoFox opens the generated draft in a VS Code Markdown editor. You can edit it, reopen it from the sidebar, and explicitly submit the parsed draft before RepoFox calls GitHub.

RepoFox does not proxy your repository through a RepoFox service. AI requests go directly from your machine to the provider you configure.

Yes, during an active workflow session. Reverting a completed session is coming soon.

The open-source code is licensed under AGPLv3. Read the repository licence before redistributing or operating a modified hosted version.

Ship the change
without losing control.

Install the VS Code extension, add an AI provider key, and review every proposed step.
GitHub is optional until you are ready to create a pull request.

Download VSIX View source and setup