Bandicot Beta

Bandicot Beta is the next release of Bandicot, installed beside it as a separate app, for Business and Enterprise plans.

Both apps are built from the same release. Beta carries new screens first while they settle. Bandicot's icon has two eyes of different heights; Bandicot Beta's has three. Each app has its own engine and updates itself from its own feed.

Download Bandicot Beta from your dashboard while signed in on a Business or Enterprise plan, then install it like Bandicot.

The download checks your plan first: signed out, it asks you to sign in; on another plan it refuses. The archive is named Bandicot-Beta-macOS-arm64.tar.gz and needs an Apple silicon Mac.

1. 1Sign in on the website and open your dashboard.
2. 2Download Bandicot Beta.
3. 3If you downloaded with a browser, run xattr -c ./Bandicot-Beta-macOS-arm64.tar.gz in Terminal.
4. 4Unpack it: tar xzf Bandicot-Beta-macOS-arm64.tar.gz.
5. 5Move Bandicot Beta.app to Applications and open it.

Bandicot Beta opens on the Lab, a start screen with Open full Bandicot, the Branches list and a link to the design lab.

Choose Open full Bandicot to use everything currently switched on for Beta. The link under it opens the Beta component lab and shared canvas, where new screens are tried before they ship. A window opened straight to a page skips the Lab. The Lab is only in Bandicot Beta; Bandicot opens on Home.

Branches lists each line of development with its own desktop build, read from this Mac and its git remote. It needs a repository: outside one it says there is no branch list and points you to the Lab in Bandicot Beta. Each row gives the branch name, a main checkout tag for the main one, whether its build is built, not built or bundle gone, a short commit and a note when its source checkout was removed. Choose Open to launch a built app, or Build to copy the command that builds it. A branch only on the remote reads as on the remote, not on this machine. Refresh reads the list again, and an empty list reads No branches yet.

In Bandicot Beta only, Versions has an extra Engine page that shows the engine's raw answers.

The page is headed Raw engine answers and is marked as Beta only. Use it to see exactly what the engine returned when you report a problem. Bandicot does not show it. Versions covers the pages every app has.

Both apps read the same chats, settings and projects, and the first one open owns the data and runs automations, setup and recovery.

The other app works on the same data but leaves that background work to the owner. Asked to do it, it says another Bandicot app manages this data. The apps never take ownership from each other by themselves: quit the owner and the other takes over.

Your phone and your other Macs reach whichever app owns the data.

Add --beta to bandicot rpc to talk to Bandicot Beta instead of Bandicot.

Without it, bandicot rpc talks to Bandicot. Command line lists every option.