DocsEveryday work
Helpi Agents
Coding agents that take a ticket and open a pull request: what they need, and how to start a run, follow it and review the result.
Updated 22 November 2026
Helpi Agents are Octopora's coding agents. Give one a ticket and it plans the change, writes it in your repository on its own branch, runs your checks and opens a pull request for you to review. It never merges its own pull request.
The agents and their roles
Each project starts with one agent, Helpi Engineer, switched off. A role changes how an agent works:
| Role | What it does |
|---|---|
| Engineer | Implements the ticket and opens a pull request for a person to review. |
| Reviewer | Reads the pull request already open for a ticket and posts its findings there. It changes and pushes nothing. |
| Designer | Does interface work, matching the existing design system. |
| Tester | Writes tests, without changing the code under test. |
| Docs | Writes documentation and comments only, never behavior. |
Whoever has Manage Helpi Agent sets this up in the project's Settings > Helpi Agent: Add agent, an on and off switch for each agent, and Retire. In Skills, they can write house rules that an agent reads when they apply, and assign up to 16 skills to each agent.
What a run needs
- The Business or Enterprise plan. The workspace owner can request it in
Settings > Plan & billing. - A repository connected to the project with write access. See Connect a repository.
- An agent that is switched on.
- The right role.
Use Helpi Agentlets you assign a ticket, start and cancel runs and answer the agent.Approve Helpi Planslets you approve its plans.Manage Helpi Agentlets you configure it. The Owner and Admin roles have all three; Manager can start runs.
The Helpi Agent page of a project only shows for roles that have at least one of these permissions.
What a run does
- The agent copies your repository into an isolated environment.
- It reads the ticket and submits a plan.
- You approve the plan or ask for changes.
- It writes the change and runs your validation commands.
- It pushes a branch named
helpi/<ticket key>-<title>and opens a pull request.
Run an agent again on the same ticket and it adds commits to that branch while it still exists. Start a fresh branch instead cuts a separate branch and opens a second pull request.
Start a run
- Open the ticket.
- Choose
Assign to Helpi Agentand pick the agent. Only agents that are switched on are offered. - In the ticket's
Helpi Agentcard, clickStart run. Add instructions if the ticket does not say everything.
Start LR-13 with the engineer agent
Helpi finds the ticket, picks the agent with that role (else the ticket's own agent, else the project's default), assigns it and starts the run, with your permissions. It starts at once, with no confirmation, and it costs no Helpi request. When it cannot, it tells you why: your role, no agent, the plan, no repository or one that cannot push, or the month's runs used up.
Follow a run
The ticket's Helpi Agent card shows the status, the Timeline, the Logs and the Previous runs. On the project's Helpi Agent page, Overview shows the active run and the month's runs, and Runs lists every run. A run moves through Queued, Provisioning, Cloning, Analyzing, Awaiting plan approval, Implementing, Validating and Pushing to Pull request opened and Completed. It can also end as Cancelled, Failed or Timed out.
Approve the plan and answer its questions
- When the status is
Awaiting plan approval, clickView plan. - Read the files it intends to create, modify or delete, and why.
- Click
Approve plan, orRequest changesand say what to do differently. The agent revises its plan, a limited number of times.
If the ticket changed after the plan was written, ask for changes so the agent plans again. When a run stops to ask something, the ticket shows Helpi Agent needs your input: click Continue to carry on from the branch and the files already written, or Stop run. Approving needs Approve Helpi Plans; answering needs Use Helpi Agent.
Review the pull request
Open the pull request from the ticket and review it like any other. You merge it: the agent never does.
- In the ticket's
Pull request commentscard,Check PR commentsloads the reviewers' comments, only when you ask.Make the fixon a comment starts aReview comment fixrun that pushes a fix for it. - For a second opinion, assign the ticket to a Reviewer agent and start a run. It reads the open pull request and posts its findings on it. Run an Engineer agent first: with no pull request there is nothing to review. Then
Fix the review findingsasks for them to be applied.
Limits
Coding agents are not in Starter or Team. Business and Enterprise include them, with plan approval and run logs. Only one run works on a ticket at a time. A person with Manage Helpi Agent sets each agent's limits under Helpi Agent policy:
| Setting | Range | Default |
|---|---|---|
Require plan approval | On or off | On |
Maximum run length (minutes) | 5 to 240 | 45 |
Runs per month | 0 to 100 | 20 |
Concurrent runs | 1 to 3 | 1 |
Validation commands | Up to 10, one per line | None |
When the month's runs are used up, the page shows Monthly run limit reached and the count starts again the next month.
Questions
I do not see Helpi Agent in the sidebar.
Your role has none of Manage Helpi Agent, Use Helpi Agent and Approve Helpi Plans. Ask the project's Owner or an Admin.
It says the repository token cannot push.
The repository token cannot write. Reconnect it with write access: see Connect a repository.
Can an agent write code before I approve?
Not while Require plan approval is on, which is the default. The agent waits for you to approve its plan.