Empty states give no guidance (no workers, no workflows, no schedules) #33

New Issue

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

jared commented

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

Overview

"No workers connected", "No workflows defined yet", "No scheduled commands yet" are dead ends. A first-time user has no pointer to how a worker registers (env vars, API key), what a workflow looks like, or that Quick Command is the quickest way to try the system.

Suggested fix

Add one-line next-step hints and links (e.g. "Install a worker → README section", "Create your first workflow" button) in each empty state.

## Overview "No workers connected", "No workflows defined yet", "No scheduled commands yet" are dead ends. A first-time user has no pointer to how a worker registers (env vars, API key), what a workflow looks like, or that Quick Command is the quickest way to try the system. ## Suggested fix Add one-line next-step hints and links (e.g. "Install a worker → README section", "Create your first workflow" button) in each empty state.

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

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: LotusGuild/pulse#33