Skip to main content

​
Organization

One Bellows GitHub App installation. It owns the list of repos and keeps its data apart from every other organization.

​
Task and job

A task is one thread of work: your request and everything that follows it. Each attempt in the thread is a job. Follow-ups, retries and edits all add jobs to the same task.
Queued → Running → Waiting for review → Done
Along the way:
  • Needs answer the agent asked you something
  • Stopping you pressed stop
  • Failed · Needs review a gate, timeout or config error
Every status and failure is explained in Task lifecycle.

​
Gate

A check command from .bellows.yaml, such as build, test or lint. Gates run at the end of every job, and the job succeeds only if all of them pass. An on-demand gate is one the agent may run while it works. See Gates.

​
Executor

The coding agent that does the work. Bellows ships Claude Code and OpenCode, and you can build custom executors on them: an executor profile with your own model and settings, for yourself or for the whole organization. See Executors.

​
Skill

A versioned bundle of instructions (SKILL.md) the agent can load. Bellows ships built-in skills for fixing, reviewing and publishing. Your organization, workspace or repo can add its own. See Skills.

​
Connection

A stored third-party credential, such as Jira, that you choose to attach to a task so the agent can use it. See Connections.

​
Question and follow-up

A question is the agent asking you something mid-run. A follow-up is you asking for more after a run ends. Both continue the same task. Every term in one place: Glossary.