isair/jarvis

Task 1a — Expose confidence score from listener.py when transcript is rejected

Open

#373 opened on May 5, 2026

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Python (201 forks)github user discovery
enhancementgood first issue

Repository metrics

Stars
 (1,090 stars)
PR merge metrics
 (PR metrics pending)

Description

Task 1a — Expose confidence score on low-confidence rejection

Part of Task 1: Low Confidence Voice Feedback.

What to do

In src/jarvis/listening/listener.py, find where Whisper transcripts are filtered out due to low confidence (currently logs 🔇 Low confidence (x.xx): ...).

  • Extract the confidence value and the reason for rejection into a structured object or named return value (e.g. a LowConfidenceEvent dataclass or a dict {"confidence": float, "transcript": str}).
  • Emit or return this event so downstream code (reply engine, output layer) can react to it.
  • Do not change any TTS or UI behaviour yet — this subtask is purely about surfacing the data.

Files to touch

  • src/jarvis/listening/listener.py

Acceptance criteria

  • Low-confidence rejection produces a structured event/value (not just a log line)
  • The confidence score and raw transcript are both accessible from outside the listener
  • Existing behaviour is unchanged (nothing new is spoken or displayed yet)

Contributor guide

Research direction
Locate the log line in listener.py that prints '🔇 Low confidence' and extract the confidence value. Create a data class or dict to hold the confidence and transcript, then return or emit it so other parts of the program can access it without changing current behavior.
Tech stack
python
Domain
backend
Issue type
Refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Python
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70