Session hangs silently while tool calls appear to do nothing
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 52/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- typescript
- Domain
- cli, developer-experience
Research direction
The issue names no files, tests, or entry points. Start by reproducing the silent behavior with a long-running file read, web fetch, or bash command, then trace the session and tool-call output path. Done means users see progress, streaming output, or an explicit narration while such operations run.
Written by the indexing model from the issue text.
Description
During an extended conversation, the session repeatedly appeared to hang — no output was shown to the user while tool calls (file reads, web fetches, bash commands) were executing in the background. The user had to prompt "Are you still there?" and "Why did it fail?" multiple times to confirm the session was still active. From the user's perspective, there was no visible indication that work was in progress.
This creates a poor experience where users cannot tell whether the agent is thinking, executing tools, stuck, or has crashed.
Expected behavior: some form of visible progress indicator or streaming output should be shown while long-running tool calls are executing, or the agent should narrate what it's about to do before executing silent operations.
Reported on: Wed Jul 08 2026.
Metadata
| Field | Value |
|---|---|
| CLI Version | 0.8.10 |
| Platform | darwin |
| Architecture | arm64 |
| OS Release | 25.5.0 |
| Category | bug |
| Working Directory | chore-fusion-upgrade |
| Session ID | ses_0bfee0ceeffepgBy6AzUpyUPuM |
- Dominant language
- TypeScript
- Stars
- 813
- Forks
- 134
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 62
Contributor 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 AltimateAI/altimate-code
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
AltimateAI/altimate-code#1323 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
AltimateAI/altimate-code#1288 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
AltimateAI/altimate-code#1285 ·
-
privacy: Altimate Base consent dialog no longer discloses persistent per-installation identifier Open
Difficulty 1/5 Under an hour Newbie friendliness 88/100
AltimateAI/altimate-code#1284 ·
-
Difficulty 2/5 Under an hour Newbie friendliness 72/100
AltimateAI/altimate-code#1283 ·
All issues in AltimateAI/altimate-code
Similar issues
-
Browser Waiting for: Product Owner
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
getsentry/sentry-javascript#24577 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
agilepathway/label-checker#640 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
copse-dev/agent-pane#2953 ·
-
agentic-workflows
Difficulty 1/5 Under an hour Newbie friendliness 85/100
githubnext/rig#534 ·
-
automation missing-model model-sync provider:pioneer
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
anomalyco/models.dev#7701 ·