Continue on another computer, or work together with your team. Each person uses their own AI to work on the same project, with shared files and version history.
All repositories are private to your organization.
Start on the computer where your project is. Once your AI has added it here, you can continue on another computer or bring a teammate into the project.
The copied instructions include the destination and temporary access to your organization. Share them only with your AI. You do not need to connect MCP first. A browser chat cannot work with your local project files.
Your AI starts from the saved project files and history. Previous AI conversations are not included.
Share the repository page link with teammates. The copied AI instructions are for your own AI and include temporary access to your organization.
About organizations and invitations
Before you start, ask your AI to get the latest changes from the same repository while preserving your unfinished work. When you finish, ask it to save your changes so your other computer and your teammates can pick them up.
We recommend using your own name for new commits so teammates can recognize your work. Ask your AI to check the author name before saving. If it does not know which name to use, it should ask you.
Changes reach the shared repository when you ask your AI to save them. They do not sync automatically as you type. If two people change the same part, your AI helps combine the work and asks you when a decision is needed.
If the temporary access has expired, click Copy for your AI in Collaboration to get fresh instructions. Tell your AI to keep using the same repository.
Saving changes makes them available to your team. Publishing or updating your app is a separate step.
Want to see what your teammates have saved? Open the commit count, such as 5 Commits, in the repository. The history page groups commits by date so you can see who saved each change and what they wrote about it. Switch branches or tags to see their history, and choose Load more for earlier commits.
Continue → Download ZIP downloads the files from the version you are viewing. It does not include change history. Use Copy for your AI when you want to continue working with that history. Copy Git URL is also available for an AI that already has access.
Browse folders and supported text files to check your saved source. The website does not edit files or make commits. If a newer version arrives while you are reading a file, choose View latest when you are ready.
Last uploaded tells you when source arrived here. Dates beside files describe when the code changed, which can be earlier.
A branch lets you try an idea separately from your team’s main work. Ask your AI to use one when you need it, and to bring the changes together when you are ready. If you only have one branch, you can keep using it.
To delete a branch, select it, open the ⋮ menu on the right, and choose Delete branch. Deleting main, master or the default branch requires reading the warning and typing its name. Choose a new default if other branches remain. There is no undo button; code kept only on the deleted branch may become unavailable.
All organization members can read the source. Your AI can assign members who may save changes; without an assignment, all members can save. These assignments prevent mistakes, not access to confidential data within the organization. Assigned repositories require a managing member’s personal connection to save changes.
Repository deletion immediately blocks new access. Source is retained for 7 days before automatic removal; daily backups can retain it for up to another 7 days. Organization deletion includes repositories. Deleting an app deployment leaves repositories intact. There is no self-service undelete action.
Start with get_repository_guide over MCP, or GET the repository guide endpoint with your existing API authentication. The guide covers creation, safe temporary Git credentials, verification, managers, limits and recovery.
GET https://api.justdeploy.net/organizations/<organizationId>/repositories/guide
list_repositories / create_repository / get_repository
update_repository / delete_repository / create_repository_access
list_repository_managers / set_repository_managers
set_repository_default_branch / delete_repository_branchMCP and the API manage the repository and issue short-lived Git access. Git transports source and history. Keep access passwords out of remote URLs, command arguments, logs and source files. With GIT_ASKPASS, use git -c credential.helper= to prevent cached credentials from overriding temporary access.
An organization can keep 20 repositories including those within the deletion retention period. Each repository supports 1 GiB of Git data, files up to 25 MiB throughout the uploaded history, pushes up to 100 MiB and 100 branches plus tags. ZIP snapshots support up to 256 MiB of uncompressed source. Text previews stop at 128 KiB.
Repository usage is currently included without a separate charge. Paused organizations can still read and download their source. Backups are taken daily and retained for 7 days; operators verify recovered Git data in separate storage before replacing source.
Repository names use 1–64 English letters, numbers, dots, hyphens or underscores and start with a letter or number. The deleted__ prefix is reserved regardless of capitalization. Your AI can choose a name such as my-shop and keep your own wording in the description.
ZIP follows Git archive attributes and does not include external submodule contents. To work with the full history, use Git clone. If a write response is lost, inspect the saved refs before retrying; preserve the original creation key and input when retrying repository creation.