Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Bug] Chat landing machine picker stays loading until full doc-meta scan

Open Beginner friendly
  • Is something wrong?
#496 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

  • #498 by @slashdevcorpse — closed without merging

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
74/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
typescript
Domain
frontend

Research direction

Read getChatLandingInitialDataLoading in packages/components/src/components/chat/chat-landing-derived.ts: it returns true whenever !isDocMetaCacheReady even with hasSelectableMachine, unlike the visibility clause that fail-opens. Change that gate and the unit test "waits for local runtime and doc metadata prerequisites", which asserts true for isDocMetaCacheReady: false with hasSelectableMachine: true; useChatLandingDefaults should still wait on doc-meta. Done when the picker enables on a cached reachable machine and tests pass. Check closed PR #498 first.

Written by the indexing model from the issue text.

Description

Affected area

Desktop app

Installation method

Built from source

Lody version or commit

ac07385

Operating system

Windows 11 x64

What happened?

getChatLandingInitialDataLoading returns true for the entire doc-meta bootstrap whenever !isDocMetaCacheReady, even when hasSelectableMachine is already true. The machine picker stays disabled after local runtime is up and a reachable machine with an agent config is already in cache. Visibility loading already fail-opens in that case; doc-meta does not.

What did you expect?

Once a selectable machine exists, the picker should enable. Empty-state banners stay suppressed because hasSelectableMachine already means a reachable machine and an agent config. Defaults restore can still wait on doc-meta in useChatLandingDefaults.

How can we reproduce it?
  1. Read getChatLandingInitialDataLoading in packages/components/src/components/chat/chat-landing-derived.ts.
  2. Note if (isRuntimeInitializing || !isDocMetaCacheReady || !localMachineStateAttempted) return true.
  3. Compare with the visibility clause: return isVisibleMachinesLoading && !hasSelectableMachine.
  4. The unit test "waits for local runtime and doc metadata prerequisites" currently expects true when isDocMetaCacheReady: false and hasSelectableMachine: true.
How often does it happen?

Every cold start until buildDocMetaCache finishes scanning every session/machine/agent meta.

Additional context

This is time-to-usable-shell, not a new picker feature. https://github.com/LodyAI/Lody/pull/317 includes this gate plus a larger mobile sync ladder. This report is only the landing-selector condition.

Before submitting
  • I searched the existing issues and did not find a duplicate.
  • This report concerns an open-source component in this repository, not a hosted service, Web or mobile app, account, or billing issue.
  • This is not a security vulnerability; security reports follow the repository's security policy.
  • I removed credentials, private source, conversations, prompts, personal data, and other sensitive information.
Dominant language
TypeScript
Stars
1.2k
Forks
141
Avg merge
12h 35m
Merged PRs (30d)
664

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from LodyAI/Lody

All issues in LodyAI/Lody

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.