What
When an API call fails and is being retried (rate limit, network error), show a brief message to the user instead of silently waiting.
Why
Without feedback, users think the app is frozen. A simple Retrying (attempt 2/3)... message improves UX significantly.
How
- Open
crates/ember-llm/src/retry.rs
- Find the retry loop
- Before each retry attempt, print a status line to stderr:
eprintln!("Retrying request (attempt {}/{})...", attempt, max_retries);
- Use
stderr so it doesn't interfere with piped stdout output
- Respect a
--quiet flag if one exists
Reference
The retry logic is in crates/ember-llm/src/retry.rs. Keep it simple — one line of output per retry.
What
When an API call fails and is being retried (rate limit, network error), show a brief message to the user instead of silently waiting.
Why
Without feedback, users think the app is frozen. A simple
Retrying (attempt 2/3)...message improves UX significantly.How
crates/ember-llm/src/retry.rsstderrso it doesn't interfere with piped stdout output--quietflag if one existsReference
The retry logic is in
crates/ember-llm/src/retry.rs. Keep it simple — one line of output per retry.