feat: implement terminal style chat history

[PratyushChauhan]

closes #1777

What Changed

Pressing ↑/↓ in the composer input navigates through previously sent user messages, shell-style. The live draft is saved when you first press ↑ and restored when you ↓ back past the most recent message. History index resets on send.

Why

Retyping or slightly tweaking a previous prompt is a common workflow. Every terminal does this — it's muscle memory. The composer already had the full message history available; this just wires ↑/↓ into onComposerCommandKey (where Enter/Tab/menu-navigation already live) using two refs. No new files, no new state, no re-renders.

UI Changes

No visual changes — interaction only. Navigation only activates when no autocomplete menu is open, so @-mention and /-command menus are unaffected.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes
• I included a video for animation/interaction changes

---

Note

Low Risk
The provided diff contains no file changes, so it should have no runtime impact. Risk is limited to potential mismatch between the PR description and the actual contents submitted.

Overview
No code changes were present in the provided diff (+++ /dev/null only), so this PR currently does not implement the described terminal-style ArrowUp/ArrowDown chat history behavior.

If this is unexpected, re-check that the intended commits/changes were pushed and that the PR branch contains the updated ChatView (or equivalent composer) key handling.

^{Reviewed by Cursor Bugbot for commit b96308f. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Add terminal-style chat history navigation to the composer with ArrowUp/ArrowDown

• Adds ArrowUp/ArrowDown key handling in ChatView.tsx to navigate previously sent user messages in the active thread.
• Saves the in-progress draft when entering history mode and restores it when navigating back to index -1.
• Resets history state whenever the composer is cleared (after send, slash command, or thread cleanup).
• Navigation is disabled while activePendingProgress is truthy.

^{Macroscope summarized cb52514.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: cbfff649-abcd-4056-8b09-adee638a4298

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[PratyushChauhan]

Video:

2026-04-06.14-55-36.mp4

[macroscopeapp]

Approvability

Verdict: Needs human review

This PR introduces a new user-facing feature (arrow key navigation through chat history) that changes how users interact with the chat composer. While self-contained and straightforward, new interaction patterns warrant human review to ensure the UX meets expectations.

^{You can customize Macroscope's approvability policy. Learn more.}

[cursor]

Cursor Bugbot has reviewed your changes and found 2 potential issues.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 7d90559. Configure here.}

[PratyushChauhan]

addressed potential issues.

[sashaduke]

I would like this feature, I actually just came here looking to see if anyone had implemented this after being frustrated it wasn't a feature yet. +1 from me

[PratyushChauhan]

Merge conflicts introduced, will replicate this in a new PR.