[Desktop] Web Search on floating typed chat fails with unknown_realtime_invocation
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 78/100
Research direction
Start in GeneratedToolExecutors+SurfaceAware.swift and compare the existing main_chat and realtime_voice surface resolution with floating_chat. Verify that typed desktop surfaces use the chatToolExecutor path while realtime_voice remains on realtimeHub, then reproduce web_search from floating typed chat to confirm the unknown_realtime_invocation failure is gone.
Written by the indexing model from the issue text.
Description
Summary
Authorized web_search on the floating-bar typed chat surface (floating_chat) was routed to the voice-only realtimeHub executor instead of chatToolExecutor. That path expects a Push-to-Talk realtime invocation envelope, so the tool failed with unknown_realtime_invocation before the typed-chat public-web lane could run.
main_chat was already fixed to use chatToolExecutor; floating_chat was still using the manifest default (realtimeHub).
Environment
- Platform: macOS desktop
- Surface: floating / notch typed chat (
surfaceKind: floating_chat) - Tool:
web_search(desktop_chat / pi-mono)
Expected behavior
Web Search on floating typed chat uses the same ChatToolExecutor public-web path as main window chat.
Actual behavior
Tool execution hits RealtimeHub without a PTT invocation and returns unknown_realtime_invocation.
Fix direction
Extend surface-aware executor resolution in GeneratedToolExecutors+SurfaceAware.swift so typed desktop coordinator surfaces (main_chat, floating_chat) resolve web_search to chatToolExecutor; keep realtime_voice on realtimeHub.
Failure class
FC-advertised-tool-routed-to-wrong-surface-executor
Related
- Parent context: advertised real
web_searchon desktop chat (#12632) - Fix PR (fork): https://github.com/sirgawain0x/omi/pull/10
- Dominant language
- Python
- Stars
- 13.8k
- Forks
- 2.7k
- Avg merge
- 6h
- Merged PRs (30d)
- 604
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from BasedHardware/omi
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
BasedHardware/omi#23723 ·
Maintainers usually reply within 1 day
-
Python CLI: corrupt compressed responses hide an unknown write outcomePossibly taken @pranav440 claimed this 14 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
BasedHardware/omi#21295 · 1 comment ·
Maintainers usually reply within 1 day
-
chore(gateway): emit INFO budget reserved/settled logs for proactivity v2 (chip task_2855f4ec)Possibly taken @ahmedcompk claimed this 18 days ago. Openbackend
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
BasedHardware/omi#20940 · 1 comment ·
Maintainers usually reply within 1 day
-
Ray-Ban Meta: a failed audio start is swallowed and capture shows recording with no audioPossibly taken @ocakciomursel-pixel claimed this 3 days ago. Openbug capture flutter p1
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
BasedHardware/omi#20782 · 1 comment ·
Maintainers usually reply within 1 day
-
[Bug]: Memory non-active routes lack blank string validation and timezone normalizationPossibly taken @brandonstensby-dotcom claimed this 26 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
BasedHardware/omi#20084 ·
Maintainers usually reply within 1 day
All issues in BasedHardware/omi
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
btclib-org/btclib-node#2083 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Gathin23/cleanyourtv#2089 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
jxxghp/MoviePilot#7212 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
cli dx rust
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
NekomyaDev/nudge#278 ·
Maintainers usually reply within 1 day