@mafredri Yes. Thanks for the idea. I faced this as this will automatically invalidate existing auth for any other coder deployment. I guess going the agent way will need some backend work to be done first.

@mafredri Yes. Thanks for the idea. I faced this as this will automatically invalidate existing auth for any other coder deployment. I guess going the agent way will need some backend work to be done first.

Maybe, but there may be another option, for instance:

1. Update coder CLI to support fallback [config]/.workspace_session, [config]/.workspace_url
2. Write these files from terraform

When the user runs the coder command inside the workspace, it will first look for session and url, not find them, then look for .workspace_session and .workspace_url.

Step 2. can be automated by agent, if we want, but that may require introducing an option like agent_dont_auto_login_the_user since not everyone may want this feature.

@mafredri writing [config]/.workspace_session, [config]/.workspace_url from terraform will likely need updating coder terraform provider if we want it to be a native feature.
Something like

resource coder_agent {
	auto_login = true
}

And this will enable coder agent to automatically create the above session files given, we support fallback in cli.

As @mafredri suggested, this change would mess up my workflow where I'm usually authenticated to my development deployment.

That said, automatically logging in the user is a nice default since most of our users aren't developing Coder itself. The auto-login default should apply without template modifications. Using some kind of hierarchy of session token locations where the agents' is last is a good idea.

resource coder_agent {
auto_login = true
}

I don't think we should add configuration until there's a clear need.

@ammario sure. Let us close this and move the discussion to a new issue.