VibeKit
Enter App
AI Agent for GitHub
An AI coding agent that works on a real GitHub repo — your repo, in your account, with your branch protection rules. The agent commits, branches, and opens PRs like a teammate. VibeKit hosts the running app; GitHub owns the source of truth.
Why a real GitHub repo matters
- You own the code. The repo is under your GitHub account from minute one. Cancel VibeKit tomorrow and you still have everything.
- Real git history. Every change the agent makes is a commit you can read, blame, revert, or cherry-pick.
- Branch protection works. The agent respects your repo's required reviewers, status checks, and CI gates. It opens PRs against them like any contributor.
- Hand-off to a developer is trivial. Clone the repo, run
npm install, and a human can pick up where the agent left off.
What the agent does in your repo
- Edits files via Edit / Write tools — same surface as Claude Code or Cursor's agent mode
- Stages, commits, and pushes with descriptive messages ("agent: fix /api/users 500 from missing await")
- Branches off main for non-trivial changes and opens a PR via the GitHub API
- Pulls before each turn so it never works against a stale tree (when you've pushed from your laptop)
- Reads README.md and AGENTS.md before reasoning so it picks up your conventions
Auto-deploy on push
VibeKit installs a webhook on your repo. Push to main from your laptop, GitHub Actions, or another agent — VibeKit detects the push, pulls the new commit into the container, runs the build, and replaces the running app. No separate CI to wire up.
# Your laptop
git push origin main
# 5–15 seconds later: yourapp.vibekit.bot is on the new commitBring your existing repo
Already have a project? Pick "Connect existing repo" when you create a VibeKit app. The agent gets repo access (you control scopes), provisions a container, and deploys your code. From there it works on your existing repo the same way it would a fresh one.
Permissions and security
VibeKit asks for the minimum GitHub scopes needed: repo on the specific repos you select (we use GitHub Apps, not personal access tokens). You can revoke access at any time from github.com/settings/installations and the agent immediately loses ability to commit. Tokens never leave VibeKit's infrastructure and are encrypted at rest.
FAQ
Does VibeKit's AI agent commit to my real GitHub repo?
Yes. When you create an app, VibeKit creates a brand-new repo under your GitHub account (or connects an existing one). The agent pushes commits to that repo on every change — same git history a human teammate would produce. You can browse the repo on github.com, clone it locally, branch off it, and revert anything the agent did with normal git commands.
Will the AI agent open pull requests?
Yes. By default, larger changes get committed to a feature branch and opened as a PR rather than pushed straight to main. You review on github.com, request changes in chat, and merge when ready. Small or hot-fix changes can be configured to push straight to main — VibeKit honors whatever workflow your repo's branch protection rules enforce.
How does deployment from GitHub to VibeKit work?
VibeKit installs a GitHub webhook on your repo. Every push to your default branch triggers an auto-deploy to your live domain at yourapp.vibekit.bot. There's no separate CI to wire up, no Dockerfile to write — VibeKit detects the framework (Next.js, Vite, Express, FastAPI, etc.) and runs the right build + start command in the app's container.
Can I use my existing GitHub repo with VibeKit?
Yes. During app creation, choose "Connect existing repo" instead of letting VibeKit generate a starter. The agent gets read+write access (you control which scopes), provisions a container, and deploys your repo to a new VibeKit subdomain. The agent then works on your existing code the same way it would on a fresh project.
What if I want to leave VibeKit later?
You walk away with the repo. The canonical source of truth is the GitHub repo under your account — VibeKit hosts the running app and the agent, but the code itself never lives only on VibeKit. Cancel your account and you keep everything that matters. The build commands and dependencies are all in package.json / requirements.txt — runnable anywhere.