feat: Support external OpenCode servers#1179
Open
thisisryanswift wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Linked issue
Closes #1178
Type of change
What does this PR do
Adds explicit support for attaching Paseo's OpenCode provider to an already-running
opencode serveinstance.A new
agents.providers.opencode.serverUrlconfig field can point Paseo at an external OpenCode HTTP server:{ "agents": { "providers": { "opencode": { "serverUrl": "http://127.0.0.1:4096" } } } }When
serverUrlis configured, Paseo uses that URL for OpenCode SDK requests and does not initialize its managedOpenCodeServerManager, so it will not spawn, rotate, or shut downopencode serve.The existing managed-server behavior remains unchanged when
serverUrlis not set.This also:
serverUrltohttp/https/global/healthfor external-server availabilityserverUrlthrough provider overrides/runtime settingsHow did you verify it
Ran focused tests:
Ran lint:
Ran server typecheck:
Also smoke-tested local Paseo 0.1.81 dev startup using a direct daemon/app setup:
127.0.0.1:6777localhost:4421ws://localhost:6777/wsafter enabling dev CORSFull workspace
npm run typecheckis currently blocked by unrelated app/CLI type errors in this checkout, including@testing-library/reacttest export errors inpackages/appand stale CLI/server declaration errors. The touched server code passes targeted tests, lint, and server typecheck.Checklist
npm run typecheckpassesnpm run lintpassesnpm run formatran (Biome)