thinkrail
ThinkRail is an incubator project from JetBrains that puts a graphical IDE around the pi coding agent. It is a thin host: pi runs in-process and keeps ownership of models, skills, compaction, cost and session state, while ThinkRail owns the workspace, the editor and the connection to the UI. Its README says the app never assembles prompts behind your back. You can run it as a native desktop app or through the thinkrail CLI, which opens the same app in a browser. The repository was created in July 2026 and the latest stable release when this review was written was v0.3.1 (November 1, 2026), so this is young software that changes quickly.
The central idea is isolation. Each workspace is a git worktree with its own branch and directory, so several agents can work in parallel without touching your checkout. You merge the branch you like and delete the rest. Around that sit Monaco editor tabs, a file tree with git change marks, terminals, and anchored review comments you can send to a chat as structured context. Once a GitHub pull request is open, the top bar shows CI checks and the review decision, and it can hand failing checks to the agent.
The second idea is durable project knowledge. A connected graph of SPEC.md files lives beside the code, and the agent reads, searches and maintains it through dedicated spec_* tools, so intent outlasts a single session. Agent Skills you already keep for other coding agents are read in place. MCP servers come from your pi mcp.json, and ThinkRail asks in the chat before calls the server does not mark read-only. It can also connect any OpenAI-compatible server, including Ollama, LM Studio and LiteLLM. Other tools built on pi, such as oh-my-pi and gentle-shell, stay in the terminal and add capability or workflow to the agent session, while ThinkRail adds an interface and a workspace model on top. It is Apache-2.0 licensed and has no accounts of its own.
Features
Why choose it
Trade-offs
Maintenance check
- Last commit
- 2026-11-08
- Commits, last 90 days
- 100+
- Releases, last 90 days
- 30
- Latest release
- v0.4.0-nightly.7 (2026-11-08)
- Open issues
- 371
- Recent issues with at least one comment
- 2/10
Oldest week on the left; the latest four weeks are orange. Source: GitHub commit activity.
Status rule: archived on GitHub = Archived; last commit within 90 days = Active; 91 to 365 days = Slowing; older = Stale. All figures come from the GitHub API on the date shown.
Most discussed open issues
- #698 Let an agent orchestrate subagents in separate ThinkRail workspaces7 comments · 2026-10-09
Issue titles are quoted from GitHub. Open the link to check whether a problem still applies to the version you use.
Who it fits
- You like pi but want a graphical workbench with an editor, diffs and terminals instead of a terminal-only session.
- You run several agent tasks in parallel and want each one isolated in its own worktree and branch.
- You want project knowledge kept as specs in the repository that the agent has to maintain.
- You use a company LLM gateway or local models through an OpenAI-compatible server.
- You work mainly with Claude Code or Codex and do not plan to move to pi.
- You prefer to stay in the terminal; oh-my-pi or gentle-shell fit better.
- Your policy rules out any usage telemetry, or requires signed Linux binaries.
- You need a stable tool for a team now rather than a v0.3 incubator project.
How it differs
oh-my-pi is a terminal fork of Pi that gives the agent IDE-grade tools, such as LSP edits and real debuggers. ThinkRail keeps pi as the engine and gives you, the person, the IDE: an editor, diffs and pull request controls. Choose oh-my-pi for a stronger agent in the terminal, and ThinkRail for a graphical workbench.
gentle-shell turns a Pi session into a workspace with an opinionated flow: read-only until you ask for a change, plus resumable feature documents. ThinkRail is less about one working method and more about the environment, with worktree isolation and a spec graph. Choose gentle-shell for its workflow rules in the terminal, and ThinkRail for parallel workspaces in a GUI.
Use cases
Alternatives
Comments
No comments yet. Be the first!