fix: use config.yaml name for default Local Config profile

[MumuTW]

Summary

• read the default profile title from ~/.continue/config.yaml when loading the global local profile
• keep the existing Local Config fallback when the file is missing, unreadable, or unparseable
• add a focused LocalProfileLoader regression test covering custom name plus fallback cases

Testing

• npm run -s vitest -- config/profile/LocalProfileLoader.vitest.ts (fails in this workspace due unresolved local package entry for @continuedev/config-yaml)

---

Continue Tasks: 🔄 7 running — View all

---

Summary by cubic

Use the name from ~/.continue/config.yaml as the default Local Config profile title. Falls back to "Local Config" if the file or name is invalid, and no longer falls back when an override file exists but is empty.

• Bug Fixes
  • Read profile title from global config; fallback to "Local Config" if missing, unreadable, malformed, or blank. Tests cover custom name and fallback cases.
  • Use a strict undefined check for override content so empty override files don’t trigger a global fallback.

^{Written for commit ac7cc66. Summary will update on new commits.}

[cubic-dev-ai]

1 issue found across 2 files

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="core/config/profile/LocalProfileLoader.ts">

<violation number="1" location="core/config/profile/LocalProfileLoader.ts:46">
P2: Falsy check on override content causes empty override files to fall back to global config and potentially assign the wrong profile title.</violation>
</file>

_{Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.}