this post was submitted on 08 Sep 2026
-73 points (13.9% liked)
Open Source
49043 readers
214 users here now
All about open source! Feel free to ask questions, and share news, and interesting stuff!
Useful Links
- Open Source Initiative
- Free Software Foundation
- Electronic Frontier Foundation
- Software Freedom Conservancy
- It's FOSS
- Android FOSS Apps Megathread
Rules
- Posts must be relevant to the open source ideology
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
- !libre_culture@lemmy.ml
- !libre_software@lemmy.ml
- !libre_hardware@lemmy.ml
- !linux@lemmy.ml
- !technology@lemmy.ml
Community icon from opensource.org, but we are not affiliated with them.
founded 7 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments

I went the other direction on this and made the runner something you host instead of making the agent portable. That's a project I'm working on, TaskHandoff (https://docs.thandoff.com/), so flagging it as self-promo up front.
The reasoning: with a portable folder the environment moves, but the machine you're sitting at still has to trust whatever the agent does there. With a self-hosted workbench you register your machines as workspaces once, then dispatch a task from the web UI and the session runs on the box you picked - local or remote. Sessions, credentials and task history stay on your side, and "moving between machines" becomes opening the UI from any of them rather than carrying the folder.
It doesn't replace the offline USB-stick case, that one still has no good answer. But for "same agent environment on three machines" the registered-workspace model is what actually stuck for me.
Out of curiosity - did you hit provider key sync issues when moving between machines? That was our other pain point, and it's part of why we kept credentials in one place.