This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
Hot Desk
Local Linux desktops for AI agents, with human takeover
Hot Desk gives each AI agent its own local Linux desktop. The home directory and Chromium profile persist, so a site you sign into once stays signed in for later sessions. Your agent connects over MCP and receives the browser, computer and workspace tools directly, with no tokens and no model API key in the config. When it gets stuck on a login or a CAPTCHA, you open the viewer, take over the same desktop, then hand control back. Runs on Docker on your own machine. MIT licensed.
I kept handing browser tools to coding agents and watching them stall in the same place: a login screen. The session ended, the cookies went with it, and the next run hit the sign-in wall again or quietly made the answer up.
Hot Desk is what I built to stop that. Every desktop is a Docker container with its own home directory and Chromium profile, both persistent, so signing in once holds. You set one up once:
hotdesk up
hotdesk open research
Sign in to X and Google in that Chromium window, then hit "Return control to agents". After that the whole prompt is:
"Use the Research Hot Desk desktop for this task. Research browser agents on X and save a Google Doc with 3 sources and 3 product takeaways."
The agent arrives already signed in and does the rest. It connects over MCP to that one workspace and receives the browser, computer and workspace tool schemas at connection time, along with the handoff and clone rules. No tokens and no model API key go in that config, and the manager binds to 127.0.0.1.
When it gets stuck, you open the viewer, take over the same desktop, do the human part, and hand control back. The demo above is Claude Code running exactly that prompt, with me stepping in mid-task.
Where it actually is: early, no stable release, macOS or Linux with a local Docker daemon. Desktops are containers sharing the host kernel, not VMs, so give an agent the same trust you would give it on your own machine.
Two things I would like your read on:
1. How much should an agent be allowed to do inside a profile that is already signed in as you?
2. One long-lived desktop per task, or a fresh clone from a checkpoint per run?
No comment highlights available yet. Please check back later!
About Hot Desk on Product Hunt
“Local Linux desktops for AI agents, with human takeover”
Hot Desk was submitted on Product Hunt and earned 5 upvotes and 1 comments, placing #42 on the daily leaderboard. Hot Desk gives each AI agent its own local Linux desktop. The home directory and Chromium profile persist, so a site you sign into once stays signed in for later sessions. Your agent connects over MCP and receives the browser, computer and workspace tools directly, with no tokens and no model API key in the config. When it gets stuck on a login or a CAPTCHA, you open the viewer, take over the same desktop, then hand control back. Runs on Docker on your own machine. MIT licensed.
Hot Desk was featured in Open Source (68.8k followers), Developer Tools (519k followers), Artificial Intelligence (478.1k followers) and GitHub (41.4k followers) on Product Hunt. Together, these topics include over 246.4k products, making this a competitive space to launch in.
Who hunted Hot Desk?
Hot Desk was hunted by Jaume Alavedra. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how Hot Desk stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Jaume Alavedra
I kept handing browser tools to coding agents and watching them stall in the same place: a login screen. The session ended, the cookies went with it, and the next run hit the sign-in wall again or quietly made the answer up.
Hot Desk is what I built to stop that. Every desktop is a Docker container with its own home directory and Chromium profile, both persistent, so signing in once holds. You set one up once:
hotdesk up
hotdesk open research
Sign in to X and Google in that Chromium window, then hit "Return control to agents". After that the whole prompt is:
"Use the Research Hot Desk desktop for this task. Research browser agents on X and save a Google Doc with 3 sources and 3 product takeaways."
The agent arrives already signed in and does the rest. It connects over MCP to that one workspace and receives the browser, computer and workspace tool schemas at connection time, along with the handoff and clone rules. No tokens and no model API key go in that config, and the manager binds to 127.0.0.1.
When it gets stuck, you open the viewer, take over the same desktop, do the human part, and hand control back. The demo above is Claude Code running exactly that prompt, with me stepping in mid-task.
Where it actually is: early, no stable release, macOS or Linux with a local Docker daemon. Desktops are containers sharing the host kernel, not VMs, so give an agent the same trust you would give it on your own machine.
Two things I would like your read on:
1. How much should an agent be allowed to do inside a profile that is already signed in as you?
2. One long-lived desktop per task, or a fresh clone from a checkpoint per run?
Code and issues: https://github.com/jamalavedra/h...