Reliant workflows
Your harness for automation.
Turn a process into a workflow: what starts it, where agents use judgment, and which results decide what happens next. For software delivery and the work beyond it.
Run on your computer, your own server or a Reliant cloud machine.
One real example
From a labelled issue to a pull request
The agent does the work. The workflow decides whether it can proceed.
- id: implement type: workflow ref: builtin://get-it-right project: path: "{{nodes.branch.path}}" args: test_command: npm test- id: open_pr type: run condition: nodes.implement.strategy == 'pass'The condition is an execution rule, not a request in a prompt.
01
An event starts it
An issue gets the agent-ready label. The workflow creates an isolated git worktree.
02
An agent works it
Get It Right implements the change, runs checks and asks a reviewer to assess it.
03
The result controls it
Only a pass verdict enables the step that commits, pushes and opens a pull request.
Read the complete example
Example you can adapt, not a built-in. Requires a connected GitHub account, the GitHub CLI signed in on the run machine, and your own test command.
name: issue-to-prdescription: Turn an issue labelled agent-ready into a tested pull requestentry: [branch]inputs: issue_number: type: integer default: 0triggers: - name: agent-ready integration: integration: github events: [issues.labeled] match: label: agent-ready inputs: issue_number: "{{ trigger.payload.data.issue.number }}" prompt: "Implement #{{ trigger.payload.data.issue.number }}: {{ trigger.payload.data.issue.title }}"nodes: - id: branch type: create_worktree args: name: "issue-{{workflow.id}}" - id: implement type: workflow ref: builtin://get-it-right project: path: "{{nodes.branch.path}}" args: test_command: npm test - id: open_pr type: run condition: nodes.implement.strategy == 'pass' command: >- cd "{{nodes.branch.path}}" && git add -A && git commit -m "Fix #{{inputs.issue_number}}" && git push -u origin HEAD && gh pr create --filledges: - from: branch default: [implement] - from: implement default: [open_pr]Branch on results, retry a step, run agents in parallel or pause for a human. How routing works
Software and beyond
Automate the process. Not just the prompt.
Start on a schedule, a webhook, an event in GitHub, Gmail, Slack or Twilio, or when another run finishes. Then route the work to agents, commands, APIs and people.
Built-in · software
Keep pull requests moving.
Review code and security, work on issues, and respond to review feedback with the Autopilot workflows.
Explore the built-insBuilt-in · operations
React when production needs you.
Autopilot On-call responds to alerts and new, returning or spiking errors. With Forge, agents can investigate logs, traces and errors.
Read the on-call workflowWhat you can build
Turn incoming work into a brief.
Start from Gmail or Slack, gather context from an API, and draft a summary for a human to review. Research, reporting and follow-ups use the same building blocks.
Explore the building blocksHow we use it
Not just developer work.
One of our own workflows places stock trades every market day. A schedule, an agent and an API can automate work well outside a codebase.
Read about schedules
Make it yours
Start with a workflow.
Keep control of it.
Describe your process to an agent, connect steps in the visual builder or edit the YAML. It’s the same workflow, stored in your repo’s .reliant/workflows/ folder.
Read the workflow guide