Use cases
What people send Rush
Each recipe is named for what comes back. It shows how the work starts, what you watch while it runs and the fields you read when it ends, in the API's own shapes.
From your product
Your own product starts an agent per task, through the API.
Review every pull request
A review on the PR
Each pull request gets an agent that checks it out in its own sandbox, runs the tests and posts a review with the evidence.
Open the recipeFix a bug from an alert
A PR with checks
Your alerting posts to a webhook trigger; an agent reproduces the failure, fixes it and opens a pull request with the checks passing.
Open the recipeRun an agent per customer task
A typed answer, by webhook
Your backend starts one session per customer request with an org key, and Rush posts the result to your webhook when the turn ends.
Open the recipeProduce a report or file, no repo
A file you download
Send a request with no repository; the agent works in its own computer and returns a file as one of the session's artifacts.
Open the recipeYour own work
Work your company runs on a schedule or on an event.
Write the missing tests
A PR with passing checks
A nightly schedule starts an agent that finds untested code, writes the tests and opens a pull request by morning.
Open the recipeInvestigate an incident
A report with evidence
Hand the agent an incident and read access to its sources; it comes back with a report that cites what it found, and no code change.
Open the recipeTurn a Linear label into a PR
A PR linked to the issue
Label a Linear issue and an agent picks it up, does the work in the Project's repository and opens a pull request.
Open the recipeUpgrade dependencies weekly
A PR, or needs_review
Once a week an agent bumps your dependencies, runs the tests and opens a pull request, or stops at needs_review and says why.
Open the recipeDraft outreach from your CRM
A sourced draft, approval in Slack
For each prospect, an agent researches the company, saves a sourced first message in your CRM and asks you in Slack to approve it. A person sends it.
Open the recipeBy hand, as a team
Engineers and teams starting and steering runs themselves.
Hand off from your terminal
A run you pick up later
Start a run from the rush CLI, close your laptop, and pick it up from the console or the CLI where it left off.
Open the recipeSteer a run as a team
One run, many hands
A teammate starts a run; everyone in the org can read it as it works, and its starter or an org admin steers it with follow-ups or by taking control of its browser.
Open the recipe