Skip to content

Local vad service#2

Open
thestumonkey wants to merge 275 commits intoappDataPrivacyfrom
local-vad-service
Open

Local vad service#2
thestumonkey wants to merge 275 commits intoappDataPrivacyfrom
local-vad-service

Conversation

@thestumonkey
Copy link
Member

No description provided.

mdmohsin7 and others added 30 commits May 12, 2025 15:48
…versation function. Updated prompt to clarify criteria for keeping or discarding snippets, enhancing decision-making process.
…r to get milk”) (#2362)

This PR refines the memory-filter prompt so that length is no longer a
discard factor.
Key points:

Bug / Gap: Short but critical directives like “Remember to get milk”
were being flagged as unimportant and discarded.

Fix: Added explicit KEEP rules for any task, request, decision,
follow-up question, personal detail, or key insight—regardless of
snippet length.

Output unchanged: Still returns exactly discard = True|False, so
downstream parsing stays intact.

Expected impact: Reduces false-negative discards, ensuring brief but
actionable statements are saved for later summarization and reminders.
…ty. Updated Tailwind classes to enhance text appearance and maintain consistency with design standards.
…364)

- Updated styling for Markdown-rendered content within the "Plugins"
section on the memory detail page.
- Ensured headings and paragraph text are clearly visible against the
dark background.
- Aligned font sizes of plugin content with other UI elements for better
visual consistency.
- Includes minor cleanups to the memory page component.
…yielding 1s when processing the old conversation for socket acceptance (#2370)
- [x] better track chat usage
- [x] track persona usage
- [x] track app filters usage
- [x] track summarised apps sheet usage
- [x] track voice message usage in chat
0xrushi and others added 30 commits June 1, 2025 15:22
These files didn’t get included in
BasedHardware/omi#2488 sorry about that
…… (#2462)

## Problem
Chat notifications clear existing messages when tapped, causing users to
lose their conversation history.

## Root Cause
A race condition in `HomePageWrapper.initState()` was prematurely
resetting `selectedChatAppId` to `null` before notification route
processing completed.

## Solution
Remove the premature `setSelectedChatAppId(null)` call that was causing
the race condition.

## Testing
✅ Verified that tapping chat notifications now preserves existing
messages
✅ No regressions in normal app functionality

## Impact
- Fixes #2442: Chat notification tapping clears messages
- Improves user experience by preserving conversation history
- Minimal, targeted fix with no side effects

**Files changed:** 1 file, 3 lines removed

## Technical Details
The issue occurred because
`context.read<AppProvider>().setSelectedChatAppId(null)` was being
called in the `initState()` callback, which would execute before
notification navigation completed. This caused the MessageProvider to
clear messages when notifications tried to navigate to specific chats.

By removing this premature reset, notifications can now properly
navigate to chat without interfering with existing message state.
Changed port so it doesn't run on same one as server

changed to using a docker image to build CUDA

updated vad to have correct modal endpoint and fix the silero fallback if not set

added flag to disable translation as often not needed in dev

updated docs for the vad service
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.