Send your versions to GitHub with no git installed
Bandicot sends the folder's versions to its repository itself, after your checks pass, signed in to GitHub with a short code or a key you save once.
A folder that came from GitHub, GitLab or any git host now has a Send to git card under Versions, Team. For GitHub, tap Sign in with GitHub, approve the short code on github.com, and Bandicot keeps that sign-in itself; no GitHub program is needed on the Mac. If the GitHub command-line tool is already signed in here, Bandicot uses that until you sign in. For other hosts, paste an access key once and Bandicot keeps it in your keychain. Send versions compares with the repository first and says how much would go, then sends on your tap.
The card also shows what GitHub reports for the newest version there, such as your website's build, and keeps reading it after a send until the build finishes, so a deploy is followed without opening GitHub or Vercel.
Opening Versions with no project folder open now says to open one, instead of leading to a page about git, and Bandicot reopens the project you last had open when it starts.
Downloaded files no longer stop a folder from keeping versions: the mark macOS puts on a download is allowed on ordinary documents, while programs still must be clean.
If your checks file holds pushes until checks pass, sending waits for them and stops when they fail, the same rule a git hook used to enforce, now without one.
Agents get the same powers from the command line: bandicot vcs records chosen files as a version, lists what changed, reads history and old files, and publishes, all without the git program. Claude Code, Cursor and opencode working in Bandicot's own code are steered to it automatically.