lettabot onboard does not detect channels configured in project-local lettabot.yaml

[ezra-letta]

Summary

lettabot onboard shows "0 of 6 channels enabled" even when Telegram is configured and working. lettabot configure (TUI) correctly detects the Telegram channel.

Root Cause (likely)

lettabot onboard reads/writes ~/.lettabot/config.yaml (global config). If the user's channel configuration lives in a project-local lettabot.yaml, onboard doesn't see it.

lettabot configure uses resolveConfigPath() which searches the full priority chain:

1. LETTABOT_CONFIG_YAML env var
2. LETTABOT_CONFIG env var
3. ./lettabot.yaml (project-local)
4. ./lettabot.yml
5. ~/.lettabot/config.yaml (global)

lettabot onboard appears to only read the global config, creating a disconnect.

Impact

• Users who configured channels via project-local yaml see "0 channels enabled" in onboard
• Running onboard to "change settings" (a natural newbie instinct) could overwrite the global config without the project-local channel settings
• Confusing UX: two config commands show different state for the same agent

Reproduction

1. Configure Telegram in a project-local lettabot.yaml
2. Verify it works: lettabot configure shows Telegram connected
3. Run lettabot onboard
4. Observe: "0 of 6 channels enabled"

Expected Behavior

lettabot onboard should use the same resolveConfigPath() priority chain as lettabot configure, showing all configured channels regardless of which config file they're defined in.

Reporter

Community user stardust_supernova (Discord)

[RhoMancer]

Fixed in PR #697 — the root cause was that onboard, configure, and channels commands only read from top-level config.channels, missing channels defined under agents[0].channels (multi-agent format). The TUI editor already handled this correctly.