One engine, a pipeline per job
Each of these is a pipeline you can import today, documented from import to first run. Some ship code; others handle support, product updates and sales. When none of them fit, build your own out of agent, shell and approval steps.
For engineering
Issues → pull requests
Hand off a Linear, Jira or GitHub issue. Agents plan, build and review it, and you approve the PR.
See how it runs →Schedule → Pull requestNightly maintenance
A schedule updates dependencies overnight, fixes what breaks, and opens a PR only if something changed.
See how it runs →GitHub → CommentSpecs from vague issues
A fuzzy issue gets a spec with acceptance criteria and open questions, posted back after you approve it.
See how it runs →Beyond engineering
Support reply drafts
New tickets are triaged and answered in your voice, within your policies. You approve before anything is sent.
See how it runs →Schedule → SlackWeekly product updates
Every Friday the week’s changes become a customer-facing “What’s new” post, ready to approve and publish.
See how it runs →Webhook → CRMInbound lead research
Each contact-form lead gets a cited research brief, a fit rating and a first reply before you’ve opened the email.
See how it runs →Build your own
Agent, shell and approval steps in a DAG, started by an issue, a schedule or a webhook. Or describe it and let Jimothy draft the pipeline.