Command history is per-browser and worker dropdown/defaults don't persist #31

New Issue

2026-09-08T20:57:32-04:00

jared commented

2026-09-08 20:57:32 -04:00

Overview

Quick Command history lives in localStorage (50 items), so it differs per browser/device and is invisible to teammates; the selected worker and execution mode reset on every reload. Keyboard submit is Ctrl+Enter only, which is not indicated anywhere near the textarea.

Suggested fix

Persist last worker/mode in localStorage; optionally add a server-side "my recent commands" derived from executions; add a hint "Ctrl+Enter to run".

## Overview Quick Command history lives in `localStorage` (50 items), so it differs per browser/device and is invisible to teammates; the selected worker and execution mode reset on every reload. Keyboard submit is Ctrl+Enter only, which is not indicated anywhere near the textarea. ## Suggested fix Persist last worker/mode in localStorage; optionally add a server-side "my recent commands" derived from executions; add a hint "Ctrl+Enter to run".

jared added the enhancement ux frontend priority/low labels 2026-09-08 20:57:32 -04:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: LotusGuild/pulse#31