FrameBuff

Docs / AI & GPU

Agents and approvals

AI is useful when it can act. FrameBuff lets agents and apps act inside limits you set, and asks you before anything that matters.

Agents

An agent works on a project, one step at a time, inside one folder. You start agents on the Agents page, and the page shows what each one wants to do next. You can approve, reject or stop it.

  • A script is your own list of steps, taken in order. It stops at the first step that fails. Saved scripts start with one click, such as "Run tests".
  • A local model works toward a goal you type and proposes one step at a time.

The guard

Every step passes a rule-based guard before it runs. The guard is not an AI model, and no setting turns it off. It checks each step again just before it runs, in case the rules changed while the step waited.

By default every step also waits for your yes. New agents run free in Settings → Agents changes only whether you are asked. The guard still checks every step.

When the guard blocks a step, you get one notification, the agent's history records it, and the agent stops.

Containment

  • An agent works only inside the project folder. The folder picker cannot leave it. Only you can widen it, from a confirm card on the Agents page.
  • Every step runs inside the operating system's containment. It can reach only the project folder, has limits on memory and processes, and starts with a clean environment.
  • If containment cannot be set up, nothing runs. There is no fallback.
  • A step that runs longer than the time limit, 10 minutes by default, is stopped.
  • When FrameBuff stops, every agent stops with it.

Agents need Linux with Landlock and a logged-in user session.

The guard's rules are on the Rules page. The rules that would let an agent loosen its own limits cannot be switched off.

The approval bar

When an app wants to do something that needs your yes, such as delete, post, share, install or change a schedule, the ask appears in the approval bar under the top bar. You have three answers:

  • Allow once
  • Allow for 7 days
  • No

The same asks are listed on the Approvals page.

  • Only FrameBuff's own top bar draws the approval bar. No app can draw it inside its window, and no tool can answer it.
  • An app always asks under its own name. It cannot ask for another app.
  • An approval never lets an app run a tool it could not already call.
  • If one app asks more than 5 small things in an hour, the rest wait in one summary ask. You can change the number.
  • A scheduled entry that an app made is checked again when it fires. If what it runs has changed since you approved it, it waits for you.

Things that always ask

Posting or sending something online, spending money, deleting and using an online service always ask first. A scheduled run cannot ask, so these never run unattended.

Everywhere in FrameBuff, a request with a countdown that nobody answers counts as no. That includes pairing, device requests and guests.

The Companion

The Companion is the assistant you chat with about your work. It runs on the model you pick. Anything it wants to write waits for your yes on a confirm card.