Helpin
Dark mode
Closed-loop agent delivery

Closed-loop agent delivery

Closed-loop delivery connects a task to the code that completes it. An agent works on the task's branch, Helpin opens a pull request, and pull request events flow back to the task so its delivery status and workflow state stay current without manual updates.

This relies on coding agents, which are not available in the Community edition.

How the loop works

  1. Work starts on the task. A coding agent runs on the task and works on the task's working branch.

  2. Changes are delivered. With Publish changes, the agent pushes its commits when the run succeeds, and Helpin opens a pull request for the branch.

  3. The task records the result. The commit and pull request are linked to the task. Its Delivery panel moves to Changes pushed and then PR open.

  4. Pull request events update the task. When the pull request is merged or closed, the task's delivery state changes to PR merged or PR closed without merging.

  5. The workflow state follows, if you map it. Helpin can move the task to the workflow states you choose for each pull request event.

Map pull request events to workflow states

  1. Go to Settings → Projects → Delivery.

  2. Under Team delivery defaults, select Configure or Edit for your team. The Delivery Defaults dialog opens.

  3. Turn on Auto-sync workflow state from PR events.

  4. Choose a state for each event in the table below, or leave Do not map.

  5. Save.

Field

When it applies

PR opened state

A pull request opens for the task's branch, for example a review state.

PR merged state

The pull request is merged, for example your done state.

PR closed state

The pull request is closed without merging.

Pull request events reach Helpin from your connected GitHub or GitLab repository. Tasks are matched by their linked branch or pull request.

Go further with flows

Flows can react to the same events. For example, a flow can start an agent when a pull request merges, or the Merge when done template can merge a task branch when the task reaches a done state. See Start a flow from GitHub events and Merge a task branch.

Where to check the loop

  • The task's Delivery panel shows the state, the last commit and the pull request.

  • Delivery progress on the task lists each run, commit, branch and pull request.

Things to know

  • A completed run means the agent finished. It doesn't prove the pull request opened. If opening it fails, the task shows PR publishing failed.

  • Preview changes runs don't push or open a pull request, so the loop doesn't continue for them.

  • Helpin updates the task from pull request events. It doesn't run your tests or confirm that a merged change works; use your repository's checks for that.

Was this article helpful?