feat: Update Lighthouse UI to support multi LLM #8925
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
|
✅ All necessary |
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
Contributor
|
✅ Conflict Markers Resolved All conflict markers have been successfully resolved in this pull request. |
…gger background job
…r-aware credential handling
Contributor
|
Functional review:
|
alejandrobailo
requested changes
Nov 4, 2025
Contributor
alejandrobailo
left a comment
alejandrobailo
left a comment
There was a problem hiding this comment.
I've added a comment with some functional review changes that need to be addressed.
8 tasks
Contributor
Author
|
@alejandrobailo Did the changes as follows:
After the PR is merged, the message looks as follows: 
About this image: 
This error occurs when the workflow errors out. There's no correct way to handle the error and display it as of now (as the error originates inside langgraph supervisor workflow). I'll try to fix it as part of a different PR. |
alejandrobailo
requested changes
Nov 5, 2025
Contributor
alejandrobailo
left a comment
alejandrobailo
left a comment
There was a problem hiding this comment.
There are no input validation, credentials are passed as Record<string, any> with no schema validation.
Use Zod to validate:
- API key format/length
- AWS region validity
- Base URL format for OpenAI-compatible providers
ui/app/(prowler)/lighthouse/config/(connect-llm)/configure/page.tsx
Outdated
Show resolved
Hide resolved
- Migrates all lighthouse actions to use handleApiResponse/handleApiError helpers - Introduces strict LighthouseProvider type with LIGHTHOUSE_PROVIDERS const - Establishes consistent naming conventions (providerType for provider kinds, providerId for database UUIDs) across all lighthouse components
…atten nesting - Remove all uses of 'any' type for full TypeScript type safety - Create specific interfaces: LighthouseModelAttributes, LighthouseProviderAttributes, ProviderCredentialsAttributes, ProviderCredentialsResponse, ApiLinks - Flatten interface nesting to single level for better readability - Replace 'unknown' type with 'Record<string, string>' for credentials - Improve type hints and IDE autocomplete support
Chan9390
changed the title
alejandrobailo
added
the
has-conflicts
github-actions
bot
removed
the
has-conflicts
alejandrobailo
approved these changes
Nov 14, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Context
Lighthouse supports multiple LLM providers - #8772
Description
This PR updates the frontend to support integrating different LLM providers (OpenAI, Amazon Bedrock, etc). It also replaces react-markdown with streamdown that allows better rendering of markdown.
Steps to review
temp.mp4
Checklist
API
License
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.