Skip to content

fix(desktop): align thread RPC and simplify themes - #119

Merged
sanchitrk merged 5 commits into
canaryfrom
fix/desktop-rpc-compat-prem315
Nov 1, 2026
Merged

sanchitrk merged 5 commits into
canaryfrom
fix/desktop-rpc-compat-prem315

Conversation

@prem315

@prem315 prem315 commented Nov 1, 2026

Copy link
Copy Markdown
Contributor

Desktop conversations must address individual threads after the RPC thread-model changes. Update the mirrored schemas, thread addresses, subscriptions, snapshots, prompts, queue edits, configuration and interruption so sibling threads stay separate. Preserve stored message parts while applying live deltas, read queue before history, and allow a compatible running server without a local CLI executable.

Keep only neutral Light and Dark themes in settings, the command palette and syntax highlighting. Dark is the default, including for removed saved themes. Forward development arguments to Electron for isolated profiles and remote debugging.

Validation:

  • vp check
  • vp run typecheck
  • cd packages/codework && vp test test/desktop.test.ts — fork history and prompt/configuration isolation, with a repeatable artifact under __artifacts__/.
  • Electron with agent-browser: GPT-5.6 Luna through a ChatGPT subscription passed initial/follow-up prompts and reload persistence.
  • Electron theme checks: only Light/Dark choices, switching, reload persistence and removed-theme fallback passed; no renderer errors reported.

sanchitrk and others added 3 commits November 1, 2026 15:12
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@sanchitrk
sanchitrk merged commit 33702b6 into canary Nov 1, 2026
2 checks passed
@sanchitrk
sanchitrk deleted the fix/desktop-rpc-compat-prem315 branch November 1, 2026 09:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants