eliott/openwork
1
0
Fork 0
mirror of https://github.com/different-ai/openwork synced 2026-04-25 17:15:34 +02:00
Code Issues Packages Projects Releases Wiki Activity

Fix workspace switching semantics and sticky local worker ports (#1166)

Browse Source 
* fix(app): decouple workspace selection from runtime state

Keep desktop workspace selection independent from backend activation so switching workers only reconnects when an action actually needs that runtime. Persist per-workspace local OpenWork server ports so long-lived local links stay stable without relying on a predictable default port.

* fix(app): resolve rebased workspace runtime references

* fix(test): auth opencode serve regression scripts

* docs(app): clarify workspace runtime and port behavior

---------

Co-authored-by: Omar McAdam <omar@OpenWork-Studio.localdomain>
Co-authored-by: Omar McAdam <omar@OpenWork-Studio.local>
This commit is contained in:
Source Open
2026-03-25 13:42:09 -07:00
committed by GitHub
parent 5598ef6c70
commit d6ee2fb7d9
36 changed files with 1204 additions and 547 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
ARCHITECTURE.md
View File

@@ -362,7 +362,7 @@ workspace C ----/
+-------------------------------+
| opencode-router |
| root: active workspace |
| root: runtime active workspace|
| clients: many dirs under root |
+-------------------------------+
```
@@ -373,6 +373,22 @@ Practical consequences:
- If workspaces live in unrelated roots, directories outside the active router root are rejected.
- OpenWork server is already multi-workspace aware.
- Desktop router management is still effectively single-root at a time.
- On desktop, the file watcher follows the runtime-connected workspace root, not just the workspace currently selected in the UI.
Terminology clarification:
- `selected workspace` is a UI concept: the workspace the user is currently viewing and where compose/config actions should target.
- `runtime active workspace` is a backend concept: the workspace the local server/orchestrator currently reports as active.
- `watched workspace` is the desktop-host/runtime concept for which workspace root local file watching is currently attached to.
- These states must be treated separately. UI selection can change without implying that the backend has switched roots yet.
- In practice, `selected workspace` and `runtime active workspace` often converge once the user sends work, but they are allowed to diverge briefly while the UI is browsing another workspace.
Desktop local OpenWork server ports:
- Desktop-hosted local OpenWork server instances do not assume a fixed `8787` port.
- Each workspace gets a persistent preferred localhost port in the `48000-51000` range.
- On restart, desktop tries to reuse that workspace's saved port first.
- If that port is unavailable, desktop picks another free port in the same range and avoids ports already reserved by other known workspaces.
```text
Shared-root case