Some of our developers are travelling by train. So this is something they asked us for. No idea how this should work but sounds realy nice.

I would be very interested in this feature as well.

We are currently only using docker on our coder server, and wouldn't it be as easy as just assuming that my local pc is a server where I could deploy my workspace to? And making sure the network interface can pick up the direct connection.

After loading the workspace I could drop my network connection then. Or connect directly to the container.

This could also decrease server costs, because everybody with small projects or high performance pc's could use the local system as deployment target and not use a server for it.

But I also can see some issues with different terraform providers.

Reopening because this is something we're considering for the long-term future.

This may be possible with #14859, if we run a local provisioner on the client machine that should host the workspace infrastructure. It could make use of Docker Desktop or something like colima to run local workspaces. Yes, it will not provide sync with a remote workspace, but will still help give a working standardized dev environment in conditions with bad connectivity.

This may be possible with #14859, if we run a local provisioner on the client machine that should host the workspace infrastructure. It could make use of Docker Desktop or something like colima to run local workspaces. Yes, it will not provide sync with a remote workspace, but will still help give a working standardized dev environment in conditions with bad connectivity.

Just throwing it out there for reference, DevPod is an another example of client-side provisioning that allows switching back and forth between local and cloud development environments.

@lietryon I tried DevPod a few month ago, but the UI kept freezing on windows...

Instead I just vscode, and now even IntelliJ based IDEs can provision devcontainers anywhere including on a local daemon.
BTW the latest intelliJ now doesn't even need to manually install the gateway , remote development is included in the IDE.

In short, as said by @lietryon when using devcontainers the local issue is solved.
That's why it would be nice if coder would prioritize feature parity with codespaces. (not talking about envbuilder, but the coder agent/server/ui)
IMO daytona and GitPod currently have better support than coder do.
(workspace creation, ide feedback loop, user secret, prebuilds, reflecting the effective devcontainer config, ports forwarding, etc, and several other offtopic issues)