How to add an app development agency to your v0 project
In v0, open the project menu (...), then Settings → GitHub → Connect, and create the repository. Then add @the-app-agency as a collaborator on GitHub.
Without GitHub, invite aios@theappagency.com to the one chat.
Verified on
On this page
Before you start
Don’t add us through Manage Members or your Vercel team settings. That makes us a member of your team, not a guest on one chat.
On some plans, an invite can use one of your seats, and anyone who sends prompts in your project can use your credits. We don’t send prompts, so we won’t use your credits. Check your plan’s seat rules before you invite us.
Connect GitHub and add us
Open the project menu (...) and choose Settings, then GitHub, then Connect.
Screenshot: v0 project Settings, GitHub, with Connect
Screenshot coming
Under Git Scope, choose your account or organization. Enter a Repository Name and click Create Repository. v0 creates a private repository and pushes the code to it.
Screenshot: v0’s Git Scope and Repository Name fields with Create Repository
Screenshot coming
On GitHub, open the new repository and go to Settings, then Collaborators (under Access in the sidebar), and click Add people.
Screenshot: a GitHub repository’s Settings, Collaborators page, with Add people
Screenshot coming
Type the-app-agency, pick it, and confirm with Add the-app-agency to your repository. GitHub emails us the invitation, and we accept it.
Screenshot: GitHub’s Add people dialog with the-app-agency selected
Screenshot coming
If the repository belongs to a GitHub organization rather than your personal account, access works differently. Email hey@theappagency.com and we’ll walk you through it.
How we work together on GitHub
v0’s own advice for working with a developer is to connect the project to the same GitHub repository: when they push changes, you pull; when you merge a pull request from v0, they pull.
v0 works on a branch for each chat. When we push to the repository, click Pull Changes to bring our work into v0.
When you Publish, v0 opens a pull request (or reuses one), merges it into the base branch and deploys. We then pull your changes.
If v0 reports a conflict, use Fix Conflicts.
Screenshot: a GitHub-connected v0 chat showing Pull Changes and Publish
Screenshot coming
Or invite us to the chat
This gives us the chat inside v0, without GitHub.
Pick the lowest role that lets us see the code. If your plan offers Viewer or Read-only, choose that. If it doesn’t, choose Editor. We won’t change anything. Never make us a workspace owner or admin.
Open the chat and click Invite.
Screenshot: v0’s Invite dialog for a chat
Screenshot coming
Enter aios@theappagency.com, choose a role (see the role note above), and click Invite.
Screenshot: v0’s Invite dialog with an email, a role selected and Invite
Screenshot coming
Keep the chat’s visibility at “Only people with access”, so the invite is the only way in.
Good to know
Already have the code on GitHub? Import from GitHub goes the other way: v0 can work on a repository you already have.
Guides that show a share popover in the header are out of date: since August 28, 2026, sharing is a centred Invite dialog.
Guides that mention personal accounts are out of date too: since October 6, 2026, personal accounts are team workspaces.
On the Plus plan, your team members need access to the repository to work in a GitHub-connected chat, unless Allow v0 to Act on Behalf of Members is on.
Removing our access
When your audit is done, we remove ourselves where your platform lets us. You can remove us any time, too.
GitHub: in the repository’s Settings → Collaborators, remove the-app-agency. v0’s connection to the repository stays as it is.
v0: open Invite on the chat and remove aios@theappagency.com.
Questions people ask
Can I connect v0 to a GitHub repository I already have?
Yes. Use Import from GitHub to bring an existing repository into v0. To start from v0 instead, open the project’s Settings, then GitHub, and create a new repository.
How do I work on a v0 project with a developer?
Connect the v0 project to a GitHub repository the developer can reach. When they push changes, you pull them into v0. When you publish from v0, it merges a pull request, and they pull.
Is the repository v0 creates private?
Yes. v0 creates a private repository under the account or organization you pick in Git Scope, and pushes the project’s code to it.
Have a product already?
Apply to invite us to one repository for the free aiOS Codebase Health Report: a private report on what’s solid, what’s fragile, and what to fix first. No sales call. You keep the report either way.
