Aias00 opened a new issue, #975: URL: https://github.com/apache/rocketmq-dashboard/issues/975
## Problem\nStudio allows and engines to pass configuration validation without an HTTP API key because those tools authenticate through their own runtime login state. After a restart, however, derives only from the provider's API-key requirement.\n\nA saved CLI configuration with no API key can work until restart, then returns and the UI disables chat even though the CLI provider can still authenticate.\n\n## Evidence\n- : validation requires a key only for HTTP engines.\n- The same class reconstructs from , without considering the configured engine.\n- accepts CLI engines without HTTP credentials once enabled.\n\n## Expected behavior\nPersisted CLI engine configurations remain enabled and ready after restart when their executable/runtime login is available.\n\n## Proposed fix\nDerive enabled/key-required state from the selected engine, and add restart-style regression tests for HTTP, Claude Code, and Qoder configurations.\n\n## Scope\nTrack 3 / AI Native provider configura tion. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
