feature: Automatically select server created with `server.start`

[allisnulll]

Did you check the docs?

• I am using the latest plugin version
• I read the plugin docs
• I read the opencode docs

Is your feature request related to a problem? Please describe.

Whenever I try to send text and another server is open it sends it there. If there are multiple serves open it asks which I would like to send it to. My problem is that I usually want to create a new server which means I have to manually start a new server, but then if I try to send text to it, it still sends it to the other server because its still selected.

Describe the solution you'd like

Change the server.start behavior to automatically select the server it starts.

Describe alternatives you've considered

I see a few other ways to improve this:

1. Add an option to start a new server in the Select an `opencode` server menu
2. Add a configuration option to change the default behavior to prefer creating a new server to send text to instead of looking for servers that were already open before the current NeoVim instance

Additional context

No response

[nickjvandyke]

Thanks for your thoughts! I like your suggestions. Similar: #164

Change the server.start behavior to automatically select the server it starts.

This should be a pure win? But I've put it off because it's tricky. Naively, we'd:

1. Change server.start to optionally return a port. Server discovery would connect to it specifically. Additional difficulty: polling.
2. Add a function to terminal.lua that goes terminal job -> PID -> port, to fulfill the above. However I'd have to hack together a PID -> port function for Windows.
3. Generalize the above function to support arbitrary embedded terminals (e.g. snacks.terminal), similar to require("opencode.terminal").setup()
4. NTH: Now we could always explicitly target the embedded terminal's server in its keymaps commands.

Add a configuration option to change the default behavior to prefer creating a new server to send text to instead of looking for servers that were already open before the current NeoVim instance

Re server discovery defaults: I chose to only call server.start when none are found because sometimes I use opencode in another terminal instead. But perhaps it's a better tradeoff to always use the configured server, and require manual selection otherwise. Idk the popular workflows so I'm just best-guessing these defaults, but I'm open to changes there.

I've thought a lot about configurable server discovery, but haven't landed on something I feel great about yet. Particularly balancing flexibility and simplicity.

When server.port is configured, we only check that, and call server.start on failure. So I think you/we could achieve your desired behavior by setting server.port to the function described for "Change the server.start behavior to automatically select the server it starts."

Add an option to start a new server in the Select an opencode server menu

This could be an easy win with little downside! I foresee an "Enter remote server URL" option in this menu sometime too, so that'd be consistent. However it's no help when only one external server exists. Unless we change server discovery to always prompt, which is also an idea.