[paperclover]

Assisted-by: gpt-6.1-terra

Tested manually

[greptile-apps]

Confidence Score: 4/5

[Medium impact] The changes affect local desktop development and a bounded set of workspace controls.

Fix the single-run row before merging so a later run does not inherit a disabled Stop button.

Findings

1.  Stop stays disabled ▶
2.  Failed launch stops working session ▶

Fix with agent prompt

### Issue 1
ui/src/components/ExperimentRunBanner.tsx:56
If a cancelled run finishes and another run starts before the next refresh, the list can change directly from `[A]` to `[B]`. The single-run branch reuses the same `RunRow`, so B inherits A's `pending=true`. B then shows “Cancelling” with Stop disabled, even though nobody cancelled it.

Add `key={runs[0].run.id}` to reset the row when the run changes, as the multi-run branch already does.

```suggestion
  if (runs.length === 1) return <div className={BANNER_CLASS}><RunRow key={runs[0].run.id} item={runs[0]} onOpenRun={onOpenRun} onOpenExperiment={onOpenExperiment} /></div>;
```

### Issue 2
scripts/dev-slot.mjs:720-730
With a running `copy` slot, `start --db empty --desktop` now kills the desktop app and stops both servers before `reserveSlot` rejects the database-mode mismatch. Previously, the rejected command left the running slot alone.

Check the requested mode before stopping the existing app and servers so a failed launch does not interrupt the developer's session.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Summary

This PR ties the development desktop app to its servers and polishes workspace controls.

• The desktop development app stays tied to its dev-slot services.
• Active experiment runs show their time and controls in separate rows.
• Reveal controls name the file manager used on the computer.
• Maximized workspace tabs make room for the desktop window controls.
• The workspace toolbar has more room beside its controls.
• Chat controls take less space and hide tooltips when you press them.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart TD
  A[Launch development desktop] --> B[Stop previous desktop app]
  B --> C[Stop development servers]
  C --> D[Reserve slot and check database mode]
  D --> E[Start servers and build app]
  E --> F[Launch supervised desktop app]
  F --> G[Wait for desktop app to exit]
  G --> H[Stop development servers]

Loading

_{Reviews (1) · Last reviewed commit: "fix: polish desktop development and work..." · Reviewed by Greptile}

[greptile-apps]

Stop stays disabled

If a cancelled run finishes and another run starts before the next refresh, the list can change directly from [A] to [B]. The single-run branch reuses the same RunRow, so B inherits A's pending=true. B then shows “Cancelling” with Stop disabled, even though nobody cancelled it.

Add key={runs[0].run.id} to reset the row when the run changes, as the multi-run branch already does.

Suggested change

	if (runs.length === 1) return <div className={BANNER_CLASS}><RunRow item={runs[0]} onOpenRun={onOpenRun} onOpenExperiment={onOpenExperiment} /></div>;
	if (runs.length === 1) return <div className={BANNER_CLASS}><RunRow key={runs[0].run.id} item={runs[0]} onOpenRun={onOpenRun} onOpenExperiment={onOpenExperiment} /></div>;

Prompt To Fix With AI

This is a comment left during a code review.
Path: ui/src/components/ExperimentRunBanner.tsx
Line: 56

Comment:
**Stop stays disabled**

If a cancelled run finishes and another run starts before the next refresh, the list can change directly from `[A]` to `[B]`. The single-run branch reuses the same `RunRow`, so B inherits A's `pending=true`. B then shows “Cancelling” with Stop disabled, even though nobody cancelled it.

Add `key={runs[0].run.id}` to reset the row when the run changes, as the multi-run branch already does.

```suggestion
  if (runs.length === 1) return <div className={BANNER_CLASS}><RunRow key={runs[0].run.id} item={runs[0]} onOpenRun={onOpenRun} onOpenExperiment={onOpenExperiment} /></div>;
```

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

[greptile-apps]

Failed launch stops working session

With a running copy slot, start --db empty --desktop now kills the desktop app and stops both servers before reserveSlot rejects the database-mode mismatch. Previously, the rejected command left the running slot alone.

Check the requested mode before stopping the existing app and servers so a failed launch does not interrupt the developer's session.

Prompt To Fix With AI

This is a comment left during a code review.
Path: scripts/dev-slot.mjs
Line: 720-730

Comment:
**Failed launch stops working session**

With a running `copy` slot, `start --db empty --desktop` now kills the desktop app and stops both servers before `reserveSlot` rejects the database-mode mismatch. Previously, the rejected command left the running slot alone.

Check the requested mode before stopping the existing app and servers so a failed launch does not interrupt the developer's session.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.