UltraGoal

Braedon SaundersTasks & Workflows32
Get it for macOS

Keep long-running agent work moving without losing the plan when a thread ends. UltraGoal schedules dependency-ready slices across isolated workers, records defects and owner decisions durably, and can require an independent verifier before work closes. Each goal pins worker and verifier execution settings, reports host substitutions, and can replace idle clean workers one at a time. Repository integration, worktree cleanup, and local provider-data reads stay off until you enable them. Requires BB 0.39+ and Plugin SDK 0.4.8+.

Overview

View source

Turn a BB root thread into a durable, provider-neutral orchestration workspace. The root plans and coordinates while a deterministic scheduler assigns dependency-ready work to isolated worker threads. Optional independent verifiers inspect completed slices before they close.

What it provides

  • A durable objective, dependency plan, findings register, owner decisions, and completion evidence.
  • Automatic one-slice-per-worker staffing with file-scope conflict avoidance and bounded concurrency.
  • Provider/model/reasoning/service-tier selection for workers and verifiers, with safe worker defaults and verifiers locked to auto permission mode.
  • Global defaults plus per-goal overrides, launch revisions, requested-versus-actual execution reporting, and controlled rolling replacement.
  • Exact repository/ref validation before managed worktree allocation, pinned to an immutable commit SHA.
  • Streaming audit findings that coalesce by concrete file, mint dedicated remediation work safely, and block premature completion.
  • Optional squash integration, worktree cleanup, and local provider accounting, all off by default where they affect repositories or private local data.

Typical workflow

Start an UltraGoal from the pane, /ultragoal, or bb ultragoal set. Add or update work through the ultragoal_patch tool. The scheduler staffs ready slices; workers report structured evidence; verifiers return VERIFY_PASS or actionable findings. The pane keeps current work, upcoming dependencies, execution provenance, defects, and owner decisions visible without retransmitting the full history.

UltraGoal supports Codex, Cursor, OpenCode, Claude Code, and Pi. It requires BB 0.39 or newer and Plugin SDK 0.4.8 or newer.

More from Braedon Saunders

Audio PreviewPlays .m4a and other audio files in BB's file panel, including audio/mp4 that the built-in preview refuses.25BallastKnow which thread is eating your RAM before the machine starts paging. Reads vm_stat page classes rather than the free percentage macOS reports, which counts inactive pages as free and stays reassuring while the box holds gigabytes of swap — pressure is graded on headroom, paging rate, compression and the kernel's own verdict, and the banner names the signal that decided. Consumers roll up by process tree and by BB thread, matched through worktree paths, so a 2.4GB row names a thread you can steer instead of six identical node processes. A guard can throttle BB concurrency, ask the hungriest threads to release memory, stop orphaned processes, or hand the problem to an agent — every one of those is off until you turn it on. Nothing is stopped unless nothing can still be waiting on it, and the apply step takes only ids the plan minted, re-checked against the live process table. macOS and Linux, no account or external service.NewMuse CodeAdds Meta's Muse Code as a bb provider over its own session protocol: streamed timeline, approvals, subagents, model picker, health, and the plan's own 5-hour and weekly usage limits as Muse reports them.46Provider UsageShows how much of each provider's plan is left — every rate-limit window, percent remaining, and when it resets, including Muse Code's 5-hour and weekly limits — plus a 7/30/90-day token chart covering every provider, from local transcripts and BB's own usage events.93

More in Tasks & Workflows 46

Plan, track, route, schedule, or automate work.

View all