Troubleshooting

Resolve installer, runtime, terminal, browser, project-tool, and diagnostics problems in current Cordy Desktop builds.

Windows installer warning

The published 0.3.0 installer is unsigned. Windows SmartScreen may show Windows protected your PC. Confirm the expected release asset, then choose More info → Run anyway.

Runtime states

Click the runtime or CPU/memory status to inspect details.

  • binary missing: for a source checkout run pnpm runtime:build; for a packaged build reinstall the matching package or set CORDY_RUNTIME_BIN.
  • incompatible: the app and runtime protocol versions differ. Rebuild from the same source or reinstall a matching package.
  • crashed: Cordy restarts the runtime with exponential backoff from 1 second up to 30 seconds. Repeated crashes appear in runtime history and logs.

Manual Restart runtime ends every current terminal and agent session, so Cordy confirms when sessions are live.

Terminal input

  • Shift+Enter submits instead of adding a line: Windows keyboard-protocol support is in source/tag 0.4.0, which is not yet a published Release. The published 0.3.0 build does not include that change.
  • Copy inside a mouse-aware TUI: hold Shift while dragging, then press Ctrl+C or Ctrl+Shift+C. On macOS, Option-drag also forces selection.
  • Ctrl+C interrupts: with no selection it is an interrupt in a plain shell. In a CLI that requests kitty keyboard mode, the CLI receives and interprets the key event.
  • Chinese IME or dictation: current input handling accepts composition and codeless-paste events. If an older published build fails, update to a published build containing the 0.1.3 fixes or run matching newer source.
  • Previous session restored: after a full quit, this banner marks locally restored terminal history above a new shell. The prior process is no longer running.

Browser

  • Permission denied: Cordy asks only for clipboard read/write and fullscreen. Camera, microphone, geolocation, and unlisted permissions are denied by policy.
  • A site stayed signed in: use Settings → Site data → Sign out for that host, or clear all browser data.
  • Password fill unavailable: activate a built-in browser tab whose scheme, host, and port exactly match the saved credential.
  • Download went to the wrong folder: check Settings → Downloads, including Ask where to save each file.

Project tools

  • Search tool not available: install rg (ripgrep) where the app can find it, then retry.
  • Commit is disabled: stage at least one file and enter a commit summary.
  • Changes list is truncated: hidden rows cannot be staged or discarded from the panel; use Git in a terminal or reduce the working set.
  • History moved while loading: refresh Graph to restart from the current branch tip.

Diagnostics

The compact performance overview offers 2-minute, 10-minute, and 1-hour charts and a View details action. The Workload half is Windows-only.

Open Settings → Diagnostics for logs and storage usage. Its log-bundle export creates a ZIP from a selected time range—one hour, 24 hours, seven days, or everything—and any selected main log, runtime log, diagnostic events, and system information. All four content types are selected by default.

The full performance monitor has a separate export. It writes a timestamped local folder containing:

  • application and environment information, metrics, and runtime restart history;
  • recent structured events;
  • tails of main.log and runtime.log.

Both exports redact absolute and path-like values. Cordy does not upload either package. Attach one to a report yourself after reviewing its contents. Logs live under logs/, events under diagnostics/, and native crash dumps under Crashpad/ in the user-data directory.