Skip to content

[AFK] Surface local server and save failures in the desktop app #6

@liangming99

Description

@liangming99

What to build

Handle common local failure states in the desktop workflow so users get clear recovery options instead of a blank window or failed save. Cover port conflicts, missing files, invalid selections, and write failures.

Acceptance criteria

  • If the preferred local port is unavailable, the desktop app either chooses another safe port or shows a clear recovery message.
  • If the selected file is missing, not an HTML file, or cannot be written, the app shows an actionable error and does not start a broken editing session.
  • Save failures from the local save endpoint are surfaced in the desktop UI or editor status area.

Blocked by

Triage

Type: AFK
Intended label: ready-for-agent

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions