Skip to content

fix: a first run doesn't say refresh failed - #229

Merged
brtkwr merged 1 commit into
mainfrom
fix/first-run-refresh
Nov 4, 2026
Merged

brtkwr merged 1 commit into
mainfrom
fix/first-run-refresh

Conversation

@brtkwr

@brtkwr brtkwr commented Nov 4, 2026

Copy link
Copy Markdown
Collaborator

What changes for you

A brand-new user, who now gets an empty list instead of an exit since #222, no longer sees refresh failed in the header while they have no sessions yet.

A projects folder that vanishes under a list you already have still reports the failure, as does any other scan error.

Proof

With the built binary and an empty HOME the header says refreshed just now. Before, it said refresh failed, list from just now once the first background scan ran. The two cases that should still fail have tests.

🤖 Generated with Claude Code

https://claude.ai/code/session_01QUnP8k6tg8jgSku3uPCCjL

@brtkwr
brtkwr enabled auto-merge November 4, 2026 14:35
@brtkwr
brtkwr force-pushed the fix/first-run-refresh branch from b676208 to 4a0bdf2 Compare November 4, 2026 14:36
With no projects folder yet, every background scan reported a failure in the
header until the first session existed. No folder and nothing listed is just
an empty list.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QUnP8k6tg8jgSku3uPCCjL
@brtkwr
brtkwr force-pushed the fix/first-run-refresh branch from 4a0bdf2 to 802d2b1 Compare November 4, 2026 14:38
@brtkwr
brtkwr merged commit a28c097 into main Nov 4, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant