Get it for macOS

Run shell commands on your Mac on a cron schedule or a fixed interval, as launchd jobs that keep running while bb is closed. Each job is a LaunchAgent plist that launchd owns, so a missed fire runs once when the Mac wakes and a disabled job stays disabled across reboots. A sidebar page shows each job's launchd status, its last twenty runs with duration and exit code, and the tail of its log, which you can follow live. Run now, Enable, Disable, Edit and Delete do the launchctl work for you, and commands run through your login shell with your terminal's PATH. The sidebar row counts failing jobs, and a picker switches between the Macs connected to bb. An optional push notification tells you when a job starts failing, once per failure; it needs bb 0.48.1 or later with Push notifications on. Requires bb 0.47 or later and macOS.


Overview

View source

Every job is a LaunchAgent plist in ~/Library/LaunchAgents that launchd itself owns: it fires on schedule with bb closed, runs a missed fire once when the Mac wakes, and stays disabled across reboots once you disable it. One sidebar page is where you make, read and change those jobs.

What you get

  • Jobs on a five-field cron expression or a fixed interval, with the schedule shown in words as you type it.
  • The status launchd reports, the last twenty runs with duration and exit code, and the tail of the log.
  • Follow a log live while a job runs.
  • Run now, Enable, Disable, Edit and Delete, each doing the launchd part for you.
  • Commands run through your login shell with your terminal's PATH, so tools from Homebrew or a version manager are found.
  • The sidebar entry shows how many jobs are failing; opening a job clears it until it fails again.
  • Optionally, a push notification when a job starts failing, once per failure, through bb's Push notifications (bb 0.48.1 or newer).
  • With several Macs connected to bb, a picker chooses whose jobs you see.
  • Jobs made by the Paseo launchd-jobs plugin appear as they are, with their history, and are never moved.

What it needs

bb 0.47 or newer, and macOS on the Mac whose jobs you manage. Commands run as you, with your permissions; only plists under the plugin's own label prefix are ever listed or changed.

Not a replacement for bb automations

bb's built-in automations run scripts and agents from the bb server while it runs. Use this plugin for commands that must run on a schedule whether or not bb is open.

More from Gustavo Ambrozio

ChatGPT Realtime ConnectionRun Voice Mode's voice chats on your ChatGPT subscription instead of a separately billed OpenAI API key. It hands Voice Mode the ChatGPT sign-in that the Codex CLI already keeps on the machine running the bb server, reads it again for every chat, and never renews or rewrites it. Only the plugins you allow, Voice Mode to begin with, receive the token; the bb app, the command line and agents in threads never do. This is an undocumented use of the subscription that OpenAI could stop accepting at any time, nobody has checked whether OpenAI's terms allow it, and voice chats count against your ChatGPT plan. Requires bb 0.46 or later, Voice Mode 0.1.9 or later, and the Codex CLI signed in with Sign in with ChatGPT on a plan that includes Codex.26Diff ReviewComment on a thread's changes line by line, then send the comments to its agent, which fixes the code and answers each one. A Review tab beside the thread shows the diff of its uncommitted, staged or unstaged changes, its branch, one commit or a range, and each comment follows its code as the code moves. The same tab reviews a GitHub pull request: answer its threads, mark files viewed in step with GitHub, and submit your comments as one review, posted as the GitHub CLI's signed-in account. An AI review leaves comments of its own, @reviewer answers a question inside a comment thread, and Fix in a new thread hands the comments to another agent; these runs start as threads under the one being reviewed, in the permission mode set in the settings (bb's Approve for me by default, or Accept edits), and in full permission mode with a provider that lacks that mode, such as opencode. Follows the review loop of the open-source diffity, credited in the plugin's third-party notices. Needs bb 0.48 or later with bb's Git plugin on, and the signed-in GitHub CLI (gh) for pull request review only; it is built on experimental bb plugin APIs that may change between bb releases.NewDreamKeep every Claude Code project's memory consolidated overnight, as Claude Code's own auto-dream would if it ran in bb. Each dream is a hidden thread that can read anything but write only that project's memory files, and a project's first dream is a dry run you review as a diff, then apply or discard. The memory is backed up before every change, and the Dream page shows each project's memory, why it is or is not due, the dry runs waiting for you and the history of dreams. The schedule is off until you turn it on. Each dream is one model run on your Claude Code account; requires bb 0.49 or later, macOS or Linux, and Claude Code signed in on the machine dreams run on.NewFirstMate CrewHand one agent your to-do list and it runs a crew of worker threads, each in its own git worktree, until the work lands. The first mate is a pinned thread in bb's own chat that writes each worker's instructions, supervises it, and brings back branches, pull requests, findings and only the decisions that are yours. A FirstMate tab shows the crew as a board of Queued, Working, Blocked, Parked, Done, Failed and Idle, with Steer, Interrupt, Relaunch and End on every card. A built-in watch tells the first mate within about five minutes when a pull request is merged, reviewed or changes check status. Requires bb 0.47 or later, git, and the logged-in gh CLI for the pull request watch; a capable model such as Claude Sonnet is recommended for the first mate.14

More in Tasks & Workflows 67

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

View all