THE WORKSPACE ABOVE YOUR TOOLS

Many agents.
One helm.

Your IDEs, CLIs, and computers. Together in one workspace. Stay in control, wherever you are.

One connected workspaceCode illustration
type Target = {
  computer: string;
  provider: string;
  project: string;
};

// Different tools. One place to steer.
const workspace: Target[] = [
  { computer: "Studio Mac",
    provider: "Cursor", project: "Website" },
  { computer: "MacBook Pro",
    provider: "Claude Code", project: "Website" },
  { computer: "Build Mac",
    provider: "Codex", project: "Website" },
];
One project
CursorHelmlaneClaude CodeCodex
Many possibilities

Keep the tools you love.
Bring them all together.

And more

The next upgrade
is how you work.

A better model helps with a task. A connected workspace helps with everything around it.

Choose your tools.
Own the whole picture.

Let each agent do what it does best. Keep your attention on the project, with one place to see and direct the work.

Meet your workspace
Working inside one tool With Helmlane
Your work revolves around its agent Choose the right tool per chat
A separate view for each environment One view across your computers
Context scattered across windows Projects, chats, files, and Git together
Check each tool to follow the work Follow progress from one workspace

YOUR DIRECTION. EVERY MACHINE.

A wider view.
A clearer next move.

Pick a computer. Pick a tool. Always know where your work is going.

Your workspace
Interactive example
Computers
Website / Launch experienceSample project

Same project.
Your preferred tool.

Direct work on your studio computer without losing sight of the rest.

Your selected target
Studio MacCursor
~/Projects/website

Online. Work runs on this computer.

Same project. Explicit targets.Switch computers above

An illustrative workspace. No account or connection required to explore.

Everything around the code.
Finally, around you.

Stay close to the details without getting pulled into another window.

Your desk is
no longer the boundary.

Keep multiple computers under one account. Stay connected to your coding workspace from your phone.

Context belongs
with the project.

Keep files, search, editing, and Git beside your conversations. Less window hunting. More forward motion.

Let the task
choose the tool.

Use different providers for different work. Your workflow can evolve as the tools do.

Stay in the loop.
Keep the controls.

Follow output, review changes, and respond to supported approvals. Each tool’s capabilities stay visible.

BUILT AROUND YOUR EXISTING STACK

Good tools deserve
a shared workspace.

Keep native conversations attached to their providers. Bring the bigger picture into Helmlane.

Cursor

IDE + agent

Your editor, its agents, and the conversations already in motion.

Codex

Coding agent

Follow threads, review requests, and keep work moving from the same workspace.

Claude Code

CLI agent

Continue native sessions with streamed output and supported approval controls.

OpenCode

CLI + desktop

Bring your configured providers and shared OpenCode conversations with you.

Antigravity

CLI + IDE

See native conversations, with controls matched to each integration’s capabilities.

ZCode

Coding agent

Keep sessions, follow-ups, and supported interactions within reach.

Also connects with Gemini CLI, Muse CLI, and Claude Desktop.
Controls vary by provider. Desktop-only actions stay in their native app.

Your machines.
Your tools.
Your direction.

Execution stays on your computer.

Work runs through your installed tools, in the local folders you approve.

The workspace brings it together.

Projects and chats stay organized across machines. Every conversation keeps an explicit target.

Connection follows your boundaries.

Computers connect outward. Enroll your machines and control their access from your account.

A few things
you might be wondering.

Is Helmlane another AI coding agent?

Helmlane is a workspace for the coding tools you already use. Your chosen provider handles the model and execution. Helmlane brings projects, conversations, files, Git, and machine targets together so you can direct the work from one place.

Can I connect more than one computer?

Yes. One account can have multiple enrolled computers. Projects can have working folders on different machines, and every chat has an explicit computer, folder, and provider target. You can see where work belongs before you send it.

Does every tool support the same controls?

No. Helmlane follows each provider’s actual capabilities. History, follow-ups, stopping, steering, models, and approvals vary by integration. For example, Claude Desktop history is visible, but its execution controls stay in the Desktop app.

Where does my code run?

On the computer you select, using its installed tools and the local folders you approve. The hosted service coordinates your account, projects, chats, and work. Your machines connect outward to the service; you do not need a public port for each computer.

What happens when a computer goes offline?

Machine status stays explicit. Local operations require that machine to be online. Hosted history and drafts remain available, and work is only queued when you explicitly choose a supported queueing flow. Helmlane does not silently send it to another computer.

Does switching tools move my entire project?

Your chat stays attached to its native provider and machine. A handoff brings selected context into a destination draft for review; it does not silently move your files or turn one provider’s session into another’s.

Keep your tools.
Take the helm.

One place for the way you already code.

Explore Helmlane