Repository navigation
Codeshi 0.46.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 | shOr download the zip for your Mac:
| Mac | File |
|---|---|
| Apple Silicon (M1 and later) | Codeshi-0.46.0-mac-apple-silicon.zip |
| Intel | Codeshi-0.46.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 | iexOr download Codeshi-0.46.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.46.0
What's new
Added
- A plan's steps are tested before later steps build on them (#89). When a step of a running plan finishes, Codeshi runs the test command marked in the Run panel on a temporary copy of its result. For a step that worked in its own copy, that is the folder with the step's changes merged on top. The folder and the copy are left untouched, and the step's merge review shows the same result. If the tests fail, the steps that depend on it wait. Fix the step in its task, or open the Plan and choose Check again or Continue anyway. Continuing is recorded as your decision. Each card in the Plan shows the result: Tests passed, Tests failed, No changes or Not tested, with the reason. A step is marked not tested when no test command is marked, its folder isn't a Git repository, or Codeshi closed while its tests were running. Failed tests show the end of their output in the step's details.
- Open a pull request from the Git panel (#18). After you commit, Open pull request shows where the branch will go before anything is sent: the repository, the branch and the branch it merges into, the commits GitHub doesn't have yet, and any files you haven't committed. The title and description are drafted from what Codeshi recorded, with no model: the branch's commits, the request that started the work, a link to any GitHub issue you brought into the conversation, and Codeshi's last test result. Secrets and local paths are removed as in exports, and you edit both before opening. You can open it as a draft. Clicking pushes the branch with your own Git login and opens the pull request with
gh. Codeshi never force-pushes and never pushes the branch a pull request merges into. If you're on that branch (main, say), you name a new branch, your commits move to it, and main goes back to where GitHub has it. If the branch already has an open pull request, the same button pushes your new commits to it. This is the only place Codeshi pushes, and agents never push.
Changed
- A plan step's instructions are written when it starts (#89). Until now, every step's instructions were written when the plan started, so a step only saw the titles of the steps before it. Now each step gets what those steps actually did: whether their changes were merged or kept as a branch, the files they changed, their test result, and their final report, labelled as the contract, schema or findings the plan asked for. The step is told to check the files rather than rely on the reports. If an earlier step finishes again after a later one has started, the later step's card says it was built on an older version.
- The recap includes tasks and plans (#88). While you were away used to cover only each workspace's main conversation. It now also lists tasks that worked, finished or stopped while you were gone: who did each, which files it changed, and whether it waits for you to merge it or approve something. A plan's steps fold into one line, such as The plan “Checkout rewrite” has 2 of 4 steps done, followed by the steps still working, the steps whose tests failed and are holding the steps after them, and the steps ready to merge. A step whose tests failed stays in the recap until you deal with it. Merging, keeping and discarding are your own actions, so they're left out.
- Times use a 12-hour clock. Every time Codeshi shows is now written like 9:41 PM: on messages, limit resets, checkpoints, the board, the phone view and Ask a Friend's sharing page.
- Flow's What happened card is shorter. It shows the latest three runs, and its Timeline button is gone, since Files changed beside it already has one.
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.