Best Tools · Coding
ThinkRail 0.2.0
SummaryJetBrains' open-source agentic IDE puts every agent task in its own git worktree and ends each turn with a receipt of the files that actually changed.
Filed October 26, 2026. Price, as published by the maker: Free, open source (Apache-2.0). No ThinkRail account; you bring your own model provider for the pi coding agent..
Open the maker’s site (opens in a new tab)
ThinkRail is an agentic IDE from JetBrains' incubator (JetBrains InnovationHub), built around the open-source pi coding agent. Each workspace is a git worktree with its own branch, files, terminals and chats, so agents work away from your main checkout. Version 0.2.0 (October 18, 2026) added a "turn receipt": when a run changes something, the chat shows how many files changed, with a Review turn button. ThinkRail says the count comes from snapshots of the worktree, not from the agent's own report.
How we tested. October 26, 2026, on an 8-core Linux box. We downloaded the 0.2.0 Linux binary, checked its SHA-256 against the release's checksum file, and ran it in a clean home folder against a tiny test repo. No API key: we plugged in a local scripted model that told the agent to run one shell command editing two files, then had it claim it changed only one. We ran it twice. The full test is in the story.
Pro: The receipt was right when the agent wasn't. Under a reply saying only tax.py changed, ThinkRail showed "2 files changed · +3 −1" and Review turn opened both diffs, including a new NOTES.md that plain git diff --stat missed. Our main checkout stayed clean; the edits stayed in the workspace's worktree, unstaged.
Con: Basic usage analytics (launches, chats created, messages sent, provider connections, tied to a random install ID) are always on, per the README. --no-analytics only turns off the extra sharing, and the extra-sharing switch was already on at first launch in our run even with that flag. You also need your own model provider, and the Linux builds are unsigned.