Codeshi 0.47.0

Install

macOS

Run this in Terminal. It picks the right build for your Mac, verifies its checksum and installs it in Applications:

curl -fsSL https://raw.githubusercontent.com/AhmedNavaz/codeshi/main/install.sh | sh

Or download the zip for your Mac:

Mac	File
Apple Silicon (M1 and later)	Codeshi-0.47.0-mac-apple-silicon.zip
Intel	Codeshi-0.47.0-mac-intel.zip

Unzip, move Codeshi to Applications and open it. Use your own configured Claude Code or Codex CLI connection, or connect Gemini through Google Antigravity in Settings (Install Google connection, then Connect account). Local continuation needs Codex CLI, Ollama and a downloaded tool-capable model. See the setup guide in the repository for authentication and billing details.

The app is not notarized by Apple yet, so the first time you open a browser download macOS says it cannot verify the developer. Open System Settings › Privacy & Security and click Open Anyway. You only need to do this once. If macOS instead says the app is damaged, run xattr -cr /Applications/Codeshi.app and open it again.

Windows

Run this in PowerShell. It downloads the Windows build, verifies its checksum, installs it for your user account and adds it to the Start menu:

irm https://raw.githubusercontent.com/AhmedNavaz/codeshi/main/install.ps1 | iex

Or download Codeshi-0.47.0-windows-x64.zip, unzip it and open Codeshi.exe in the Codeshi folder. The app is not signed yet, so the first time you open a browser download Windows may say it protected your PC: click More info, then Run anyway. On Windows, connect Claude Code or the Codex CLI; installing the Google connection from Settings is not available on Windows yet. Updates install from inside the app on macOS; on Windows, run the installer again.

The private-link service for Ask a Friend is published as a container image: docker pull ghcr.io/ahmednavaz/codeshi-sharing:0.47.0

What's new

Added

• Commits in Timeline (#20). Timeline now shows each folder's commits on its current branch among the checkpoints, in time order, from the oldest checkpoint on (or the latest 15 before there is one), up to 30 per folder. Each commit says who made it as far as Codeshi knows: From the Git panel for a commit made there, During Claude's run (or another agent's) for one made while a run was working, and otherwise its author. Clicking a commit's message opens its files and lines read only. A merge shows what it brought into the branch, and Open on GitHub appears when the folder's origin is on GitHub. Nothing in Git is written, and restoring files still goes through checkpoints.
• An evaluation task for each starter skill (#86). npm run eval has six new tasks, one per starter skill, for running with and without it: a view that handles every state, an endpoint that checks who may call it, a migration that works on existing data and can be undone, an accessible toolbar, a review that has to find two seeded defects, and tests that must catch four realistic slips. A failed check now lists which of its parts failed, by the check's own names, without storing the agent's code or reply. Results so far are in evals/README.md.
• Hear replies on your phone (#23). On a connected phone, the speaker under a finished reply reads it in the phone's own voice, a paragraph at a time, leaving out code and tables. Tap it again to stop. Read replies aloud, at the bottom of the workspace list, reads each reply as its run finishes while Codeshi is open on the phone. It's off by default. It works on Same Wi-Fi too, and stops when you hide the page, move to another conversation or tap the microphone.
• Open one of your GitHub repositories as a workspace (#159). New workspace has a From GitHub tab listing the repositories your GitHub CLI login can see: your own, your organizations' and those you collaborate on, most recently pushed first, with search. Click one and it's cloned into the folder under Clone into and opened as a workspace. A repository already on this computer, in a workspace or in that folder, says Open and opens its existing folder instead. The first time, Codeshi suggests the folder most of your workspaces are in, then remembers the folder you clone into. It uses gh and your own git: Codeshi asks for no sign-in, stores no token and never pushes. The list is read only when you open the tab, and shows up to the 500 most recently pushed repositories. Signing in without gh, and GitHub Enterprise, aren't supported yet.
• Move Codeshi to another computer (#160). Export Codeshi Backup… in the File menu, or Settings › General, saves your workspaces, their conversations, memory, skills, board cards and tasks, and your settings to one file locked with a passphrase. Checkpoints can go too. Import Codeshi Backup… on the other computer, also offered on the setup guide's first screen, asks where each workspace folder is there: a folder already there (found by its GitHub address or its path), a fresh clone through gh, another folder, or none. Folder IDs and paths in Codeshi's own records are rewritten to match. Importing into a workspace that already exists merges with it. A conversation that changed on both computers is replaced only if you choose, and this computer's copy is kept. Sign-ins, the GitHub login, phone pairings, always-allow approvals and tasks' working copies never move. Nothing goes through a server; moving directly between computers without a file isn't built yet.

Changed

• Alerts are set up by moment, with Try it. Settings › Alerts now has a card for each moment, Needs you first, then Finished and Stopped, each with a chip for each way: banner, sound, Dock bounce, Dock badge and phone. Try it shows the real thing. It plays the sound and, in the desktop app, shows the banner or panel and the Dock badge, then says what happened, including when macOS refused the banner and how to allow it. The Dock bounce comes if you switch to another app within a few seconds. Needs you suggests turning on a sound while it has none. Your alert choices carry over unchanged.
• Live status in one place. The menu bar status and the pill under it now sit together under While agents work at the top of Settings › Alerts. They're described as quiet status, apart from the alerts, and Show the pill shows the pill for a few seconds. Agent › Alerts and the menu bar's own Alerts menu can turn the pill on or off too, and their ticks match what Settings shows.
• The setup guide asks about alerts. A last step, Know when an agent needs you, shows the Needs you card with Try it and, on a Mac, the pill with Show the pill. Choices save as you make them, and the rest stays in Settings › Alerts.
• One focus ring in Settings search. The search box drew two rings while you typed in it.

Fixed

• The progress pill's × hides it instead of opening Codeshi (#75). On macOS, pressing × on the pill under the menu bar brought Codeshi forward and left the pill on for next time. It now hides the pill and puts you back in the app you were using. The pill stays hidden until you've been back in Codeshi, then shows again the next time you leave while agents work; before, it came back as soon as another run started. The same goes for × on an alert in the panel.
• Keyboard and screen reader fixes (#26). Switching side panels with Enter or Space dropped keyboard focus to the page, because each panel has its own row of tabs. Focus now stays on the tab, and the row is one stop in the Tab order: Left and Right move to the next panel, Home and End to the first and last. The Terminal and Run tabs of the bottom panel are one Tab stop too, with Home and End. Entering or leaving Flow with the keyboard also dropped focus, because the header moves; it now stays on the Flow button. Each message now starts with a heading (You, or the agent's name) for screen reader heading navigation. On the board's canvas, each card tells a screen reader that Option (Alt on Windows) with the arrow keys moves it, and the hint at the corner says so too. In the model picker, Connect… and More … models rows are now read as part of the list.
• Memories no longer need a recheck after every commit (#21). Since 0.30.0, any new commit in a folder marked every memory saved there Needs recheck, even an unrelated commit. Those memories went to agents as possibly out of date and started unticked in Copy to AGENTS.md. Now a commit by itself flags nothing. Conventions and decisions, the rules you set, need a recheck only when a file they name changes. Working fixes and failed approaches, facts found in the code, also need one after a switch to another branch, or when the folder's dependencies change in package.json, composer.json, deno.json, Cargo.toml, pyproject.toml, requirements.txt, Pipfile, Gemfile, go.mod, pubspec.yaml or Package.swift. A project's own version number, its scripts and lock files don't count. Hovering Needs recheck says which of these happened. Before, it said the folder had left the workspace whenever no named file had changed. Editing and saving a memory counts as checking it again on the current branch.

---

Codeshi is free and open source. If it's useful to you, star it on GitHub so more contributors find it, or support it on Patreon.