band-loop

Band Loop

Recurring agent tasks via band cronjobs. The agent fires on a cron schedule against a target workspace — dispatching each iteration to the workspace's chat pane (default) or the agent's terminal CLI (--via terminal) — optionally checks a stop condition each iteration, and deletes its own cronjob when the condition is met.

This is the native answer for users who reach for Claude Code's built-in /loop: that command is gated behind scheduledTasksEnabled, which is always false in SDK / Band sessions. band cronjobs runs server-side and survives session restarts.

This skill is focused on the scheduled-loop pattern. For broader operations see the sibling skills:

• band — workspaces, projects, tunnel, settings (also documents band cronjobs for general CRUD).
• band-start — create a new workspace and kick off the first agent task.
• band-chat — chat panes inside a workspace (the loop's prompt is dispatched to a chat).

Prerequisites

• The Band server must be running (started by the Band dashboard app).
• A target workspace must exist (use band-start to create one first if needed).

JSON Output

All commands support --output json (or BAND_OUTPUT=json env var) for structured output.

• Success: JSON object to stdout, exit code 0
• Error: {"error": "message"} to stderr, exit code 1

Workflow

1. Resolve the loop target

A cronjob is scoped to either a project or a workspace. For an agent loop you almost always want workspace scope so the prompt fires into the same chat over and over:

# Auto-detect the workspace ID from cwd
ws_id=$(band workspaces list --output json \
  | jq -r --arg cwd "$PWD" '.workspaces[] | select(.path == $cwd) | .id' \
  | head -1)

If the user is outside a workspace cwd, ask them which workspace to target (or run band workspaces list and pick one).

2. Parse the interval into a cron expression

Accept human durations (5m, 10m, 1h, 6h, 1d). Default is 10m. Map to a standard 5-field cron expression in the server's local timezone: