Your desk is
no longer the boundary.
Keep multiple computers under one account. Stay connected to your coding workspace from your phone.
THE WORKSPACE ABOVE YOUR TOOLS
Your IDEs, CLIs, and computers. Together in one workspace. Stay in control, wherever you are.
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" },
]; // Make the destination explicit.
- const computer = computers[0];
+ const computer = computers.find(
+ ({ id }) => id === target.computerId
+ );
+ if (!computer?.online) {
+ return { status: "offline" };
+ }
// Your project. Your chosen machine.
return {
computer,
+ provider: target.provider,
+ project: target.project,
};Keep the tools you love.
Bring them all together.
A better model helps with a task. A connected workspace helps with everything around it.
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 workspaceYOUR DIRECTION. EVERY MACHINE.
Pick a computer. Pick a tool. Always know where your work is going.
Direct work on your studio computer without losing sight of the rest.
~/Projects/websiteOnline. Work runs on this computer.
An illustrative workspace. No account or connection required to explore.
Stay close to the details without getting pulled into another window.
Keep multiple computers under one account. Stay connected to your coding workspace from your phone.
Keep files, search, editing, and Git beside your conversations. Less window hunting. More forward motion.
Use different providers for different work. Your workflow can evolve as the tools do.
Follow output, review changes, and respond to supported approvals. Each tool’s capabilities stay visible.
BUILT AROUND YOUR EXISTING STACK
Keep native conversations attached to their providers. Bring the bigger picture into Helmlane.
Your editor, its agents, and the conversations already in motion.
Follow threads, review requests, and keep work moving from the same workspace.
Continue native sessions with streamed output and supported approval controls.
Bring your configured providers and shared OpenCode conversations with you.
See native conversations, with controls matched to each integration’s capabilities.
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.
Work runs through your installed tools, in the local folders you approve.
Projects and chats stay organized across machines. Every conversation keeps an explicit target.
Computers connect outward. Enroll your machines and control their access from your account.
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.
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.
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.
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.
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.
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.
One place for the way you already code.
Explore Helmlane