bandicot

One script reaches the whole app

An agent's script can now use every part of Bandicot by name, and opening Team on your phone no longer freezes the Mac.

Engine

Every feature from one script

An agent's program can now reach anything the app can do: Team, Versions, models, the rack, profiles, memory, plugins, automatons, machines and usage. It calls each one by the same name the app uses, and none of them adds a word to what the agent reads at the start. Reading is immediate. A change runs under the agent's own permissions. Anything that reaches other people, starts paid work or replaces something waits for your OK in the window, and what only you may do, such as saving a key or allowing a checks file, is not offered to the agent at all.

Long agents stay light, safely

When a long agent has piled up old tool output, Bandicot swaps the big, older pieces for one-line notes in a single batch. Each note names the call that brings the full output back, whole or a page at a time, and the full output always stays in the agent's history. A gentler rule that leaves anything the agent has not answered yet is built and measured; it used more tokens for the same results, so it stays off until it earns its place.

The Usage journal counts every cut and the bytes it freed. The point you chose for compaction is kept, up to what the model can hold.

The phone keeps answering

Opening Team on your phone while an agent was placed in a team could lock the Mac's engine, and the phone said the Mac was not answering. The engine no longer waits on itself, so Team opens and the Mac keeps working.