Desktop & extensions · Improve
Improve Desktop App
Fix the selected desktop app boundary across UI/native layers, IPC, local storage/files, backend integration, tests, and packaging/release config when directly affected.
MCP library 1.6.1 · Instruction library 1.6.1 · English technical instructions
← Back to searchUse this workflow
Connect Vibe Coding Library to a coding agent that supports MCP over Streamable HTTP. Choose Other / MCP agent for a neutral prompt, or a ready-made Codex or Claude Code invocation. Add your task details below.
Goal
Fix the selected desktop app boundary across UI/native layers, IPC, local storage/files, backend integration, tests, and packaging/release config when directly affected.
Scope selection
Use the selected desktop feature, OS integration, local data issue, auto-update problem, audit finding, failing test, or packaging failure. Do not rewrite the app shell or update system unless required by the selected fix.
Change targets
- Renderer/main/native process boundaries, IPC payload validation, OS permission requests, notifications, tray/menu/deep-link behavior.
- Local storage, secrets, file access, cache, logs, crash reports, offline/sync, migrations, and cleanup.
- Backend API integration, auth/session refresh, tests/manual scripts, packaging/signing/notarization config, docs/maps directly affected.
Implementation principles
- Validate all cross-process and external inputs.
- Protect tokens/secrets and avoid logging sensitive local data.
- Preserve platform compatibility and existing update/migration paths.
- Keep release and rollback gates explicit.
Validation
Run repository-native tests/builds and bounded manual/platform scenarios for the selected behavior, including offline/restart/update/permission states when relevant. Report unavailable signing/store/platform gates honestly.
Repair the owning IPC, native permission, local migration or lifecycle code and synchronize direct renderer/backend consumers. Replay the same operation and its denied control against synthetic files/state, then verify the affected restart/update path retains the correct identity and data. Feed this built/runtime evidence to the local-client check; fix remaining boundary failures before Patch Checking. Do not replace a missing platform test with a claim based on the development UI alone.
Workflow ID: desktop-app-polish · View the versioned source · Shared workflow and authority rules