[Bug] Desktop 0.2.0-rc.2 (Windows x64): expanding the "ungrouped" sessions section crashes the renderer

[wenzhetristan-commits]

Environment

DeepSeek Harness Desktop, version 0.2.0-rc.2 (official build from the nightly feed)
Windows 11 x64 · Electron 44.0.0
Reproducible: 4 out of 4 attempts
Summary

Sessions created externally through the bundled ACP entry (dsh --profile acp) show up in the desktop UI under an "ungrouped" section. Expanding that section crashes the renderer process.

Steps to reproduce

Create a session via ACP using the stock acp profile: initialize → session/new → session/prompt (standard ACP flow).
Open the desktop app — the session appears in the sidebar under an ungrouped group.
Click to expand that ungrouped group.
The renderer crashes (the app shows its crash view).
Observed

The crash is a renderer process exit. The shell log records:

Error: Desktop renderer exited: crashed
at WebContents. (file:////resources/app.asar/lib/main.js:12067:107)
No error-level renderer console output was captured.

Workaround (works for us)

Registering the session IDs into a workspace (sessionIds in workspace.json) makes those sessions render normally and behave fine. The crash is specific to the ungrouped section holding unregistered sessions.

Notes

During part of our testing the desktop profile also had two trivial local test plugins installed (a heartbeat log-writer and a small UI banner); they were later removed. If useful for triage, we can attempt a clean-environment reproduction with the current stock profile.
Sanitized crash logs from all four occurrences are available on request.
Ask

Is this a known issue? If renderer crash reports are usually handled elsewhere (e.g. Discord), happy to move this there.

[slyyr]

The fact that registering the session IDs into a workspace makes the crash disappear is a strong clue.

It suggests the renderer may assume that every session belongs to a valid workspace/group, while the ungrouped path is passing an undefined or incomplete group object.

I'd compare the data passed to the renderer for:

1. a normal workspace session,
2. an ungrouped session,
3. the same session after registering it into workspace.json.

If the renderer expects a workspace/group object to always exist, the fix should probably be to explicitly handle the ungrouped case rather than allowing the renderer to access properties on a missing group.

I'd also add a regression test for an externally-created ACP session with no workspace membership and verify that expanding the ungrouped section renders normally.

Since the crash is reproducible and disappears once the session is assigned to a workspace, the workspace/ungrouped state transition seems like the most useful place to investigate first.

If this clears up the issue, please consider marking the answer as accepted so others who run into the same problem can find the solution more easily.