TUI: show a "still waiting on model" indicator during long Altimate Base header waits

Open
#1,262 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
68/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
go
Domain
cli

Research direction

Start by locating the TUI (Go) tree and the code that waits for the first Altimate Base response headers. Add a visible "waiting for Altimate Base to respond…" indicator after roughly 15–20 seconds without headers, and verify that it distinguishes prolonged waits from a frozen terminal.

Written by the indexing model from the issue text.

Description

Found during the v0.11.0-beta.4 release review (CTO P2 + Chaos Gremlin P2). Deferred — TUI (Go) tree, genuine follow-up.

beta.4 raises the Altimate Base header timeout to 5 minutes so healthy cold-start/queue/reasoning requests are not aborted early. Trade-off: while waiting for the first response byte, a genuinely wedged gateway now looks like a frozen terminal for up to 5 minutes instead of erroring at 10s.

The single highest-leverage support fix is a visible "waiting for Altimate Base to respond…" indicator that appears after ~15–20s of no headers, so a long-but-healthy wait (and a genuine hang) are distinguishable from a crash. This is cheaper and higher-impact than further timeout tuning.

Related: #1261 (auto-retry design for HeaderTimeoutError).

Dominant language
TypeScript
Stars
813
Forks
134
Avg merge
2d 5h
Merged PRs (30d)
62

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from AltimateAI/altimate-code

All issues in AltimateAI/altimate-code

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.