Git · OneDrop

Every project is a git repository. The agent commits everything after each turn, with your message as the commit message (see Your code is saved after every turn). Tools → Git shows that history and lets you work with it without the Shell.

History

The history lists the project’s commits, newest first, with who made each one (the agent’s turns are marked Agent), how long ago, and its short id. The note under it shows when the history was last backed up outside the sandbox.

Search the history with the box next to History: it looks through every commit’s message and author (type agent for the agent’s turns), or finds a commit by its id. Show more lists older commits, 50 at a time.

Click a commit to see its full message, author and email, the exact date and time, and its full id (with a copy button), plus the files it changed with the lines added and removed. Click a file to see its diff: added lines in green, removed in red. Click the commit again to close it.

Restore an earlier version

Open the ⋮ menu on a commit and choose Restore this version. Every file goes back to how it was at that commit, and the app restarts.

A restore is saved as a new commit, so nothing is lost: to undo it, restore the version before it the same way. Any uncommitted changes are committed first, as Changes before restoring ….

Commit your own changes

Changes you make in the Shell or the Files panel, or that the agent made before you stopped it, show up under Commit with their state: M modified, A added, D deleted, R renamed, U new (untracked), ! conflicted.

Write a summary and click Commit all changes, or press ⌘/Ctrl+Enter. The commit is made as you. As with the agent’s commits, node_modules, vendor, .cache and .env files (except .env.example) are never committed.

To throw changes away, click the undo icon next to a file, or Discard all. Files go back to the last commit and new files are deleted. Ignored files like node_modules and .env are kept. This can’t be undone.

While the agent is working, committing, discarding, switching branches and restoring wait until it finishes.

Branches

The branch menu at the top shows the current branch. Pick another to switch to it, or choose New branch… to start one from the current commit. The app restarts on the new branch.

Push to GitHub or another git host

Connect a remote repository to push your commits to it and pull commits others made.

Connect GitHub

If your OneDrop has a GitHub App set up, click Connect to GitHub. A dialog walks you through it.

The first time, click Continue to GitHub. On GitHub, pick your account or an organization, choose all repositories or only the ones OneDrop may use, and approve. GitHub brings you back with the dialog open. If you end up back on the project without GitHub bringing you, open Tools → Git: the dialog asks Finished installing on GitHub? Click Continue to pick up the installation.

Then pick an owner (your account or an organization) at the top of the dialog, and either:

The name is suggested from your project, and OneDrop checks as you type that it’s free. Choose Private or Public.

In an organization, click Create and push. OneDrop creates the repository and pushes your project to it.
On your personal account, click Create it on GitHub. GitHub doesn’t let apps create repositories on personal accounts, so GitHub’s new-repository page opens with the name and visibility filled in. Create it there and come back: OneDrop finds it and offers Connect and push. If OneDrop only reaches the repositories you chose, give it access to the new one first; the dialog links to the right page.

The dialog opens on New repository when your project has commits, and on Existing repository when it doesn’t. Add account or organization installs the app somewhere else.

You only see repositories that both you and the app can reach. No token is stored for the project: OneDrop gets a short-lived one from GitHub each time it pushes or pulls. If your GitHub sign-in expires, the dialog asks you to reconnect.

Connect with a token

Without the GitHub App, or for another git host (Other git host), connect with an access token:

Click Create on GitHub. 2. Enter a repository name and a GitHub personal access token that can create repositories (a fine-grained token with Administration and Contents read and write, or a classic token with the repo scope).
Leave Private repository checked, or uncheck it for a public one.
Click Create and push. The repository is made on your account and the current branch is pushed to it.

Push sends the current branch to the remote. Pull brings in commits the remote has that the project doesn’t. Both run in the background; the card shows Pushing… or Pulling…, then how many commits there are to push or pull.

A push the remote refuses because it has newer commits says Pull first.
A pull only fast-forwards. If the project and the remote both have new commits, ask the agent to merge them.
Disconnect in the ⋮ menu forgets the remote and its token. The repository itself is untouched.

The token is stored encrypted by OneDrop and never shown again. It never goes into the sandbox: pushes and pulls run on OneDrop’s server, which carries commits in and out of the sandbox. Remotes must use HTTPS, and on the public internet unless your admin allows private networks (see configuration).