Feat: add back and forward buttons to navigation

[sethwebster]

Problem

T3 Code has no visible way to retrace app navigation. After moving between threads, project settings, and other primary views, the user must find the previous location again through the sidebar.

This request is for the main app navigation, not the Back and Forward controls in the browser preview.

Proposed behavior

Add Back and Forward buttons to the main navigation chrome.

• Back opens the previous app location.
• Forward reopens the next location after the user goes back.
• Each button is disabled when its direction has no history entry.
• Navigation does not add duplicate entries or create a loop when the user moves backward or forward.

The history should cover threads, settings, and other primary views. The exact placement can follow the existing responsive navigation on web, desktop, and mobile.

Keybindings

Use the shortcuts proposed in #4764:

• Cmd+[ and Cmd+] on macOS
• Ctrl+[ and Ctrl+] on Windows and Linux

The buttons and keybindings should use the same navigation history.

Examples

1. Open Thread A, then Thread B. Back returns to Thread A, and Forward returns to Thread B.
2. Open Settings from a thread. Back returns to that thread.

Related

#4764 proposed broader navigation history, buttons, and keybindings. GitHub closed that issue when it was converted to a Discussion. This issue tracks the visible Back and Forward controls.

[t3dotgg]

Note

🤖 GPT-5.6 Sol responding on behalf of Theo

Thanks for the proposal. This request is tracked in Ideas discussion #6822.

I added the missing cross-client requirements there before closure. The same shared navigation history and Back and Forward controls, including disabled states and Cmd or Ctrl bracket keybindings, must work across responsive web, desktop, and mobile. Moving backward or forward must not add duplicate entries or create a navigation loop.

I'm closing this as a feature request tracked in Ideas as part of an automated pass on all open issues. The discussion is a proposal. This feature has not been implemented or fixed by this policy move.