Pipeline and Automation

Stib can progress a card through columns, react to agent results, run scripts, call webhooks, and relaunch recurring work. These mechanisms are configured separately so you can automate only the parts you trust.

Auto mode

Enable Auto mode on a card to let it traverse the enabled pipeline columns. Each active column runs with its own type, agent/model defaults, prompt template, and completion action.

A conversational planning column can deliberately pause for approval. If full continuation is configured, Stib applies the column's auto-mode action and proceeds. Failure, cancellation, an unanswered question, a condition mismatch, or a permission problem stops automatic progress rather than guessing.

Per-card pipeline

The card can include or skip eligible columns without changing the board for everyone. Use this when a task does not need every standard stage. The visible pipeline indicators summarize the configured route; they do not guarantee future success.

Column automations

Column settings can define:

• status conditions for leaving or moving work;
• automatic answers with a maximum-response guard;
• automatic move rules;
• actions or webhooks on entry and exit;
• context reset or resume behavior;
• worktree cleanup, archive, read-state, and bulk cleanup behavior;
• deterministic sorting.

Start with a passive or approval-gated workflow. Add unattended transitions only after the relevant prompts, credentials, and scripts are reliable.

Scripts

Project scripts are named commands executed in the project working directory. They can validate, build, test, deploy, or perform maintenance. Configure them in Project settings → Scripts, then run them manually or from supported automation points.

Treat scripts as code: keep them reviewable, avoid embedding secrets, set timeouts, and make destructive commands explicit. A remote server runs the script on the server-side project path.

Webhooks and integrations

Column webhooks notify external systems about transitions. Board integrations can import and synchronize external issues. Audit webhooks export audit events. These are distinct configurations with different payloads and trust boundaries.

Use HTTPS, scoped credentials, and retries on the receiving side. Stib redacts configured webhook secrets from normal API responses, but the destination still receives whatever payload you configure.

Loops

A Loop keeps a card in its current column and relaunches it on a schedule or interval. It is suited to recurring maintenance, monitoring, or iterative goals. Loop controls can record standing notes, explicitly skip an iteration, or declare the goal complete.

Use a stop condition and a bounded schedule. A loop is not the same as Auto mode: Auto moves through columns; Loop repeats in place.

Review automation

Check card history, agent messages, script runs, audit events, and Git state. When automation appears stuck, determine whether it is waiting for a person, a condition, an agent credential, a script, an external integration, or the next scheduled loop before retrying.

Next: Kanban Board and Audit & Collaboration.