2025-09-20 - 2026-09-20
Overview
3 Releases published by 1 user
Published
deploy-2026.09.09-61
Published
deploy-2026.09.09-52
Published
deploy-2026.04.14-16
2 Pull requests merged by 1 user
Merged
#36 fix: handle mysql2 >=3.23 returning JSON columns pre-parsed (Gandalf relay regression)
Merged
#35 Redesign the Pulse UI onto the LotusGuild Terminal Design System
1 Issue closed from 1 user
Closed
#2 Redesign UI to match web_template (LotusGuild Terminal Design System)
34 Issues created by 1 user
Opened
#1 Worker WebSocket connection goes zombie after server restart, never reconnects
Opened
#2 Redesign UI to match web_template (LotusGuild Terminal Design System)
Opened
#3 Executions waiting for user input are invisible in the list; 'Waiting' filter never matches
Opened
#4 Automated runs (gandalf/scheduler) crowd out manual runs – Manual tab can appear empty
Opened
#5 Quick Command shows no result inline – user is sent to another tab to find output
Opened
#6 Quick command to a disconnected worker leaves an orphaned 'running' execution and a generic error
Opened
#7 Executions can stay 'running' forever – no server-side timeout or reaper for quick/scheduled/internal commands
Opened
#8 Abort does not stop a workflow – engine keeps running and overwrites status to 'completed'
Opened
#9 Scheduled command silently skipped when target worker is offline – 'Last run' still advances
Opened
#10 Rate limiter is shared by all users behind the proxy and is exhausted by the UI's own polling
Opened
#11 Workflow authoring is an undocumented raw-JSON textarea with no validation
Opened
#12 Create Workflow modal wipes the example definition, leaving an empty textarea
Opened
#13 Dry run is impossible for workflows without parameters; confirm() text references a checkbox that isn't there
Opened
#14 Worker error details are dropped: failed commands show 'Failed' with no reason or exit code
Opened
#15 Execution list items don't show the command or worker for quick commands
Opened
#16 Execution search says it searches commands but never can – filters are client-side over one page
Opened
#17 WebSocket events trigger full list reloads that reset pagination, selection and scroll
Opened
#18 Re-run button on workflow executions re-runs only the first command as a quick command
Opened
#19 Scheduled commands cannot be edited, run on demand, or use cron from the UI
Opened
#20 goto to a non-existent step id ends the workflow as 'completed'
Opened
#21 Prompt timeout silently continues the workflow; prompt/wait steps bypass the global execution timeout
Opened
#22 Non-admins can create workflows but cannot view, edit or delete their own
Opened
#23 Workflow parameters: only free-text inputs, and the character restriction is discovered at runtime
Opened
#24 No mobile / narrow-screen layout
Opened
#25 Inconsistent feedback: native alert()/confirm() mixed with lt.toast; no in-app connection status
Opened
#26 Multi-target execution is sequential (quick command and workflow steps)
Opened
#27 Long command output is hard to read: no copy, wrap toggle, ANSI handling or truncation notice
Opened
#28 Documentation is out of date and worker onboarding path is wrong
Opened
#29 Worker: crash-loop on startup when server unreachable; no reconnect backoff
Opened
#30 Worker memory metric uses freeMem, overstating usage on Linux
Opened
#31 Command history is per-browser and worker dropdown/defaults don't persist
Opened
#32 Add a reduced-motion / effects-off option for scanlines, flicker and boot sequence
Opened
#33 Empty states give no guidance (no workers, no workflows, no schedules)
Opened
#34 Deleting a worker is undone by its next heartbeat