Engineering & deploys
OpenHelm agents that raise their findings in Linear.
Connect Linear through its MCP server or an API key and OpenHelm's agents can read and create issues in your workspace. When a job finds something that needs a person, such as a funnel stall or a bug it could not fix, the issue can land in the Linear team where you already plan, and agents can check existing issues before raising a duplicate.
What agents do with Linear. Recurring jobs, checked every run.
File findings as Linear issues
When a job turns up something that needs a human decision, create an issue in the team you choose, with the evidence the agent gathered attached.
Check before filing
Read open issues first, so an agent skips a problem your team is already tracking rather than adding another copy of it.
Context for engineering work
When an agent is working on a bug, it can read the related Linear issue for the reproduction steps and discussion your team has already added.
Connect Linear. A few minutes, once.
Connect Linear
Add Linear under Connections in the OpenHelm app and paste a scoped API key, or provision it programmatically with POST /v1/connections.
Describe the job in plain English
Tell OpenHelm what you want done and how often. It drafts a plan with a schedule, the tools it will use, and a clear definition of done.
Approve the plan
No job fires until you have reviewed the plan. Set the autonomy level to control whether writes execute directly or queue for your approval.
It runs, self-checks and reports
Runs execute in isolated cloud sandboxes on schedule. An independent evaluator scores each run against the goal, and results arrive as logs, emails or data-table rows.
Or provision it over the API (see the Connections API docs):
curl https://api.openhelm.ai/v1/connections \
-H "Authorization: Bearer oh_live_..." \
-H "Content-Type: application/json" \
-d '{ "name": "Linear", "type": "token", "secret": "<your Linear API key>" }'
# The secret is write-only: stored encrypted, injected only at run time.Questions
Does Linear replace OpenHelm's own tasks?
No. OpenHelm keeps its own Tasks and approvals, and anything risky still waits for you there. Connecting Linear lets a job also read or create issues in your workspace when you ask it to, so the work shows up where your team already looks.
How does OpenHelm connect to Linear?
With a scoped API key: create one in Linear, paste it into Connections in the OpenHelm app, or provision it programmatically with POST /v1/connections. The key is stored encrypted and injected only at run time inside an isolated sandbox, and you can rotate or delete it whenever you like.
Can the jobs run on a schedule without me?
Yes, that is the point. Jobs run once, on an interval, or on a cron expression. A scheduler fires them, a watchdog times out anything hung, and a separate evaluator checks each run actually advanced the goal. You approve the plan before anything runs for the first time.
Is my Linear data safe?
Each run executes in an isolated cloud sandbox with scoped, revocable credentials and no middle-layer copy of your data. Every action is logged per run, results come back with evidence, and the agent never fabricates data it could not verify.
Give your product a team that never clocks off.
Start free in the browser, or run it on your Mac with your own Claude Code or Codex plan.