continuedev
fix: warnings and errors for unresolved MCP secrets
- For CLI, add warnings for unresolved secrets, or throw error if in headless
- For extensions, make warnings more explanatory/up-to-date and move to mcp connection class
Summary by cubic
Detect unresolved MCP secrets and surface clear warnings in extensions; in headless CLI, throw an error to prevent misconfigured runs. Secret checks are now done at connection time for more accurate feedback.
-
Bug Fixes
- Warn when MCP server config has unresolved secrets and list their names.
- In headless CLI, treat unresolved secrets as errors and mark MCP status as error.
- Add guidance links for personal/org secrets and “Include in Env”.
-
Refactors
- Move secret validation from YAML load to MCPConnection and CLI service.
- Use getTemplateVariables and decodeSecretLocation to extract secret names from server config.
Written for commit 86ed8e964dfd37e5298b0072b78fffc14d0b2fe8. Summary will update automatically on new commits.
✅ Review Complete
Code Review Summary
⚠️ Continue configuration error. Please verify that the assistant exists in Continue Hub.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
:tada: This PR is included in version 1.31.0 :tada:
The release is available on:
Your semantic-release bot :package::rocket:
:tada: This PR is included in version 1.5.1 :tada:
The release is available on:
Your semantic-release bot :package::rocket:
:tada: This PR is included in version 1.35.0 :tada:
The release is available on:
Your semantic-release bot :package::rocket:
:tada: This PR is included in version 1.6.0 :tada:
The release is available on:
Your semantic-release bot :package::rocket: