Goals

Let an agent work toward an outcome across sessions, with a separate verification step.

Goals are opt-in under Settings → Feature flags (goals). They need project file storage and Loops (reminders). Open Goals in the project, describe the outcome and its completion criteria, and choose an agent.

State and files

Beeuni stores the goal’s state, limits, owner session and verification results. The folder Goals/<slug>/ in the creator’s My files holds GOAL.md for the brief, log.md for progress, and evidence/ for proof. Editing these files does not change the goal’s state or limits; use the goal page’s controls.

Work and verification

One owner session works on a goal at a time. A heartbeat normally wakes an active goal every four hours; answers, merged change requests and verifier findings can also wake it. A successor continues if the owner fails or fills its context. Waiting for your answer turns off the heartbeat.

A separate verifier checks every current criterion. A criterion reported complete by the owner is still unverified. Beeuni marks the goal done only when the verifier passes every criterion; a failed or inconclusive check sends it back to work.

Pause, stop and access

Pause prevents new turns; an existing turn can finish. Resume restarts the heartbeat and wakes the owner. Stop ends the heartbeat and stops the owner’s running turn. Start again reopens a stopped goal in the same folder.

The creator, the person the goal is for, and project admins can manage it. People with access only to the goal’s folder can read it without these controls. The agent’s own permissions still limit its work; a goal adds no access to connectors, secrets or other project resources.