-
Notifications
You must be signed in to change notification settings - Fork 453
Insights: lavague-ai/LaVague
Overview
-
- 8 Merged pull requests
- 0 Open pull requests
- 0 Closed issues
- 6 New issues
Loading
Could not load contribution data
Please try again later
Loading
8 Pull requests merged by 3 people
-
Feat/gradio demo qa
#570 merged
Aug 14, 2024 -
run all scripts regardless of fail
#567 merged
Aug 13, 2024 -
Scroll by closest scrollable container size
#568 merged
Aug 12, 2024 -
add example for dropdownSelect
#566 merged
Aug 12, 2024 -
Add hover and relative scan and scroll actions
#562 merged
Aug 10, 2024 -
Adding/updating docs
#556 merged
Aug 8, 2024 -
feat: clear empty messages when disconnection or interruption happens
#559 merged
Aug 8, 2024 -
feat: refined ui & content script injected at install
#558 merged
Aug 8, 2024
6 Issues opened by 5 people
-
LaVague QA , Azure Open AI configuration file sample
#569 opened
Aug 13, 2024 -
Ollama package
#565 opened
Aug 11, 2024 -
Add action to support file upload.
#564 opened
Aug 10, 2024 -
ERR_HTTP2_PROTOCOL_ERROR on `WebAgent.get`
#561 opened
Aug 8, 2024 -
Add log_to_db option to `demo()`
#560 opened
Aug 8, 2024
4 Unresolved conversations
Sometimes conversations happen on old items that aren’t yet closed. Here is a list of all the Issues and Pull Requests with unresolved conversations.
-
Is it possible that the agent asks the question in case of form filling activity so that the user knows what what information they need to provide.
#445 commented on
Aug 14, 2024 • 0 new comments -
Enhance University Form-Filling Process with Conversational AI
#447 commented on
Aug 14, 2024 • 0 new comments -
LaVague QA - Gradio UI
#553 commented on
Aug 14, 2024 • 0 new comments -
Browserbase integration
#550 commented on
Aug 8, 2024 • 0 new comments