The two that hurt
- Two chats on one repo never ran together, and the app showed the waiting
  one as "working". The server now allows several runs per repo (Settings
  sets how many), and a queued run says what it is waiting for, everywhere
  it appears.
- Deploy did nothing. CapRover rejects the call the app was making, so the
  button reported success and shipped nothing; the fix builds the head of
  the app's branch. Apps with no repository say so instead of pretending.

Runs
 1. Several runs at once, per repo and overall, both adjustable in Settings.
 2. A "running now" sheet: everything working or waiting, with why, and a
    stop button for each. The Chats tab carries a live count.
 3. Type while a run is going and the message queues — it sends itself the
    moment that run ends.
 4. Fork a chat: same repo, last prompt ready to edit, both run in parallel.

Chats
 5. Dictation, with a language picker on long-press (an Arabic sentence in
    an English recogniser is nonsense).
 6. A file picker that inserts a repo path into the prompt.
 7. Search inside conversations — titles, prompts and answers — not just
    titles, with the matching line shown.
 8. Each finished run shows how long it took, and its exit code if it failed.
 9. Pin a chat (long-press) to keep it at the top.
10. Tapping a finished-run notification opens that chat, even from cold.

Git
11. A commit message written from the actual diff, then edited before use.
12. The branch chip switches branch, and creates one.
13. Commit history, each commit openable as its own patch.

Files
14. Content search across the repo, opening the file at the matching line.
15. Starred files and recents per project.
16. "Diff vs HEAD" on the open file.

Deploy
17. Deploy = build the latest commit on the branch (the fix above).
18. Roll back to a version CapRover still has the image for.
19. Restart, and scale instances (zero is a deliberate stop).
20. Box health in Settings: CPU, memory, disk, and what is running.

Version 1.5.0+15.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>