Voice mode: no way to interact with or watch subagents
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
- Domain
- ai-infra-agents
Research direction
Start by tracing how voice mode dispatches subagents and how their status, progress, and results reach the conversation. The issue names no files or tests, so first locate those entry points and related coverage. Done means voice users receive subagent progress and completion; the broader request also asks to steer, question, and stop running subagents.
Written by the indexing model from the issue text.
Description
In voice mode, dispatched subagents are a black box.
Current behaviour
- A subagent starts, but nothing about it reaches the caller: no progress, no intermediate output, no completion notice that lands in the conversation.
- The user (talking on the phone) cannot ask "what is the subagent doing?", steer it, or cancel it — none of those work in voice mode the way they do in text chat.
Expectation
- At minimum: surface subagent status/progress and completion into the voice conversation so the agent can report it aloud (start, key milestones, result).
- Ideally: allow interaction with a running subagent from voice mode — ask questions about its progress, send follow-ups, stop it.
Why it matters
Voice mode is meant to be usable hands-free (phone). Right now anything delegated to a subagent silently drops out of the conversation until the user switches back to text chat.
- Dominant language
- TypeScript
- Stars
- 297
- Forks
- 81
- Avg merge
- 5h 30m
- Merged PRs (30d)
- 153
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 thecodacus/pithagoras
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
thecodacus/pithagoras#306 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
thecodacus/pithagoras#43 · 2 comments ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 6/100
thecodacus/pithagoras#361 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 32/100
thecodacus/pithagoras#347 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 54/100
thecodacus/pithagoras#344 ·
Maintainers usually reply within 1 day
All issues in thecodacus/pithagoras
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
earendil-works/pi-claude-code#36 ·
Maintainers usually reply within 6 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
Resources: New work of jabodetabekPossibly taken @rmt-svc claimed this today. Openresources
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
railmapgen/rmp-gallery#4167 ·
Maintainers usually reply within 2 days
-
documentation p1
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
microsoft/monaco-editor#5577 ·
Maintainers usually reply within 1 day