Skip to content

From idea to production, in one room.

Helmturn is where product, design, QA, support and engineering ship with agents.

Nordlo shopProductsProduct pageDario is at the helm

Product page

Where shoppers decide.

Dario took the helm

Dario Developer09:12

Hi, I’m almost done with the product page redesign, could you have a look?

Paula Product09:14

Looking now. This is where people decide, so every detail counts.

Tessa Tester09:20
sizes-on-iphone.png
1On “Size (EU)”

On my phone the sizes are cut off after 43.

Suggested to DarioWaiting

You joined the room

/products/court-sneakerLiveAgent, on the shop’s boxAgent
Shoes / SneakersCourt SneakerColour Chalk

Nordlo, its team and the agent’s replies are made up for this demo. Helmturn is in development.

An idea at nine. Ready to ship by ten.

Another morning in the same room. Scroll to watch.

  • Sofia Support
  • Paula Product
  • Daniel Designer
  • Tessa Tester
  • Dario Developer
  • Your agent
  1. Bring the question

    A customer asks when an order arrives. The agent answers in plain words.

  2. Turn it into the idea

    She asks to show it on the page. Dario runs it, and the agent builds it.

  3. Shape it on the app

    He clicks the price in the running shop and says what’s wrong.

  4. Check where it runs

    She finds the sizes cut off on her phone. The fix lands minutes later.

  5. Ship, or pass the helm

    Each change lands in the team’s repository. When he leaves, Daniel steers.

A room for every feature and every bug.

Rooms sit in your projects, sorted the way your team already works.

Always on, on the project’s own box.

The agent works on a machine that is always there, so a room keeps going when every laptop is closed.

While the owner is away. A box runs other people’s requests only if its owner turns that on. They name who may ask, the agent only answers unless they allow changes, and they see a list of everything that ran.

Tools come with the room.

Set a tool once for the organisation, a project, a group or a single room. Every room shows which tools its agent has, and where each one comes from.

NordloTools
  1. NordloOrganisation Ticket system added here Error tracking added here
  2. Nordlo shopProject Payment provider added here Analytics added here
  3. BugsGroupAnalytics switched off here
  4. Total is off by one centRoom

Tools in this room

  • Payment providerFrom Nordlo shopReady on the shop’s box
  • Ticket systemFrom NordloReady on the shop’s box
  • Error trackingFrom NordloReady on the shop’s box
  • AnalyticsSwitched off in BugsOff here
Helmturn keeps the list. Access to each tool is signed in on the box, once, by its owner.

The project remembers.

What one room decided, and what someone kept for later, is there for the agent in the next room, weeks later, without anyone retelling it.

Bugs / Total is off by one cent21 Oct

Sofia Support21 Oct

Invoice is a third of my tickets too. Not for today, but we should look at it.

Sofia kept this for later

Room summary Rounding fixed and saved by Tessa. 61 orders refunded by Sofia, who answers those tickets.

Checkout / Pay by invoice13 Nov

Started from Sofia’s later-note

Paula Product14:05

What does pay by invoice touch in the shop?

Sent to the agentDone
Dario’s agentto Paula · 14:06

Sofia’s note from 21 Oct is in the project’s memory, and so is the one-cent room: refunds there went through her. In the shop, invoice touches the checkout and the order email.

Sofia, Daniel, Paula, Tessa and Dario around one laptop in a bright studio, talking and pointing at the screen.

For developers

The agent runs on the project’s box, with its owner’s own login.

How it works
Sign in with GitHub
Everyone sees their own organisation’s projects, and only those.
It runs on the project’s box
A Coder workspace, a remote box or a VM that is always on. Its owner pairs it with Helmturn once, signs their agent in and connects the project’s tools there; Helmturn stores none of it. A teammate’s computer works too, for working alone or pairing quickly.
Tools along the tree
Tool entries, MCP servers included, are set for the organisation, a project, a group or a room. The nearest level wins and any level can switch one off. Helmturn holds the list, not the access: each tool is signed in on the box by its owner.
Project memory
Room summaries and later-notes live with the project, and the agent gets an index of them when a session starts. .helmturn/ in a repository holds its setup: conventions, the folders that matter, how to run and check it. A readable copy can come as one standing pull request from the Helmturn GitHub app, the way Dependabot works.
Its real screen, shared
Anyone in the room can open the agent’s own screen and watch it work, live.
Changes signed by whoever saves
Each saved change is a git commit, signed with the key of whoever saves it, from their own app; no key lives on the box. Whoever asked, and earlier helms, are co-authors. Your git hooks run as on any commit.
Shipping stays yours
Helmturn saves changes to your repository. Your own pipeline takes them to production.
No secrets on our side
Helmturn never holds your logins, keys or tool access. The one credential it keeps is its own GitHub app’s, for the memory pull request.
Claude CodeOn the shop’s box
> On my phone the sizes stop after M. L and up are cut off. Screenshot attached.  Suggested by Tessa Tester, run by Dario Developer ● Read(sizes-on-iphone.png)● Update(app/domains/product/components/SizePicker.tsx)  └ Updated SizePicker.tsx with 1 addition and 1 removal      14 -   <div className="flex gap-2 overflow-hidden">      14 +   <div className="flex flex-wrap gap-2">● Bash(pnpm vitest run app/domains/product)  └ Tests  31 passed (31) ● Fixed. The sizes wrap onto a second line on small screens.
e41c07aWrap the size picker on small screens1 fileSigned by Dario DeveloperCo-author Tessa Tester

Bring your team in.

We’re letting a few product teams in early.