Let's get you
to your project.

Your first project

1. Install Buddy using the Windows download.
2. Install your agent and complete its sign-in: Claude Code setup or Codex setup. Buddy doesn't install these tools automatically.
3. In Buddy, select Open folder… to open a base terminal in your project. Start the installed agent there, or use Start a new chat in the chooser.
4. To revisit supported history, choose Pick a chat. Confirm the provider's own trust or approval prompts in the terminal.

Download & installation

The supplied builds are Windows x64. A phone can download the file, but cannot run this Windows application. No ARM-native or Store build is advertised here.

Downloads are hosted on the public GitHub release and need no GitHub account. If the download does not start, use the direct fallback link on the download page. Compare the listed SHA-256 hash if you need to check the file. If a future release is marked unavailable, no public URL has been configured for that release.

This build is unsigned. Windows may show an unknown-publisher warning. If Windows blocks the app or the file doesn't match the published checksum, stop and report the issue. Don't disable antivirus or SmartScreen.

If a terminal won't open, use Settings → Terminal → Default shell to select an installed shell. A missing agent command needs that agent's installation and PATH setup. A native module error may need a fresh, correct-architecture Buddy installation.

Saved chats & names

Buddy browses supported local Claude Code and Codex histories. The provider's installed CLI resumes the conversation. This does not convert Claude conversations into Codex conversations, and custom assistants handle their own history.

Names for unlinked terminals are local workspace labels. Renaming a terminal linked to a saved chat can update the provider's saved title too. Use Link chat to correct the history association when needed.

Quitting Buddy stops its running processes. Reopening can resume supported saved conversations, but does not bring back unsent input, the exact shell process, or arbitrary terminal state.

Tabs, grid, and focus

Choose Tabs for one session at a time or Grid for side-by-side terminals. Use the focus control to expand one pane and Escape to return to the layout. Separate agent sessions keep separate conversations and memory.

Notifications & input

Notifications and chimes start off. Opt in under Settings; Windows permissions and Do Not Disturb still apply. A pause alert follows eight seconds without output after submitted input and is rate-limited. It doesn't verify completion.

Click-to-position sends horizontal arrow keys to a compatible line editor. It is disabled in full-screen alternate-buffer programs and while viewing scrollback. Clicks requiring unrelated up/down movement are ignored.

Report a problem

Report an issue on GitHub ↗

For a useful report, note Buddy's version, your Windows version, which shell/agent was involved, and the steps that triggered the issue. Remove credentials, personal paths, and private conversation content from screenshots or logs.

Uninstall

Close running sessions when it is safe to do so, then use Windows Settings → Apps → Installed apps → Terminal Buddy → Uninstall. Uninstalling Buddy is separate from removing provider tools, their local history, or their accounts.

The portable launcher can be removed after it is closed. Removing it does not by itself erase preferences stored in the Windows user profile.