RepoFox

AI transformed how code is written. RepoFox is how it ships.

Comment

The missing AI shipping layer

AI transformed how code is written. RepoFox is how it ships.

RepoFox turns the handoff from a finished change to a Branch → PR into one guided journey. Instead of making a developer plan Git commands or fill blank forms, it reads repository context, proposes the likely branch name, commit message, and PR details, then asks the developer to edit or confirm at consequential steps.

The unlock: an atomic Snapshot Engine

This is not only commit-message generation. RepoFox protects the full shipping journey with a repository-local receipt and Snapshot Engine:

  • trigger a Branch → PR workflow;
  • review AI-generated suggestions instead of starting from blank prompts;
  • explicitly confirm protected Git actions;
  • retain a durable receipt of branch, stage, commit, and push; and
  • restore eligible local snapshots later without deleting the original receipt.

The same receipt model is portable: developers can work from the terminal, VS Code, or Cursor. Editor support is first-class; the CLI remains available for developers who prefer it. A restore is explicit and local—it never silently deletes remote Git history.

What we built for OpenAI Build Week

RepoFox had a pre-Build-Week baseline. The Build Week work, developed with Codex and GPT-5.6, adds:

  • a repository-scoped session ledger stored in Git metadata;
  • CLI status, history, and guarded restore paths;
  • receipts and snapshots for branch, stage, commit, and push;
  • shared VS Code and Cursor adapters backed by the portable ledger; and
  • a cold-start test path and versioned VSIX artifacts.

BUILT_WITH_CODEX.md separates the baseline from the Build Week contribution.

How judges can test it

Clone the public repository, run pnpm install --frozen-lockfile, pnpm build:cli, then node apps/cli/dist/index.js status --json. For a live disposable-repository workflow, configure a supported provider key and follow the README. The public demo shows the complete credentialed flow and the completed-receipt restore path.

Privacy

RepoFox stores its ledger in local Git metadata. Provider keys and GitHub tokens are stored by the host surface and are not committed to source control.

Built With

Share this project:

Updates