ThinkRail

ThinkRail is an agentic IDE that gets better every time you use it. With Spec-Driven Development support, it learns your project as you work, becoming more capable and helpful over time.

We built a rich interface around the pi coding agent, isolated work into separate workspaces, and gave the agent durable project knowledge through the spec graph and reusable skills. We are now adding full extension support, so ThinkRail can create the tools it needs based on how you work.

Website: thinkrail.ai · Blog: thinkrail.ai/blog · Discord: thinkrail.ai/discord

⭐ If you find ThinkRail useful, give it a star. It helps others discover it.

Installation

ThinkRail ships in two forms: a native desktop installer and the self-contained thinkrail CLI. You can install them from out Landing page.

For latest version, see the Releases page.

What you get

• Isolated workspaces. Open any git repo as a project and create git worktree workspaces from it, each with its own branch and working directory. Agents can then work in parallel without touching your original codebase; when they finish, merge the results you want to keep and delete the rest. Ask a chat to do something "in a side workspace" and the agent starts that workspace and its chat itself, then checks how its chats and pull requests are doing. You can also attach existing git worktrees or explicitly work in the project folder.

  • Finished and dormant workspaces are settled when their pull request merges or closes, or after a quiet week, and return the moment you work in them again.

  • The topbar shows where the active branch stands against origin, and the state of its pull request. From there you can publish, push, or open a new PR described from the plan, the commits, your PR template, or an agent-written draft.

  • Once a GitHub PR is open, ThinkRail shows its CI checks and review decision, and lets you mark it ready, merge it, reopen it, or delete the remote branch.

• An IDE around the agent. ThinkRail comes with Monaco editor tabs, a file tree integrated with git to show code changes as they happen, terminals, and document support. Rendered Markdown previews have a heading outline that follows the section you're reading; hide it or move it to either side. The pane you're typing in stays at full contrast while the rest is dimmed, and VS Code-style keys move you around: F6 steps between panes, ⌘L jumps to the chat input, ⌘0 to Projects, ⌘1–⌘9 to an editor group, and ⌃` to the terminal.

• Powerful chat features. You can open several concurrent work sessions per workspace, each with its own model. Send a prompt, or queue it as a follow-up, delegate to subagents, and work together on a shared plan: the agent updates it, and you review and edit.

• Find anything from one box. ⌘K (or a double tap of Shift) opens a palette that finds chats and the messages inside them, workspaces and projects, files in the current workspace, specs, and plans, with a preview pane. It also runs the app's commands and opens Settings sections, and with nothing typed it lists the chats waiting for you. Type a task and press ⌘↵ to open Create workspace with it as the prompt. Press ⌘⇧F to find text inside the workspace's files as you type: matches are grouped by file, with match-case and whole-word toggles and a code preview, and ↵ opens the file at that line.

• Chats without a project. Ask, plan, or draft without a repository. Each chat gets its own scratch folder under Chats for its files, terminal, and plan, with no branch, review, or pull request. Start one from the Welcome screen, the Create dialog, the palette, or the Chats section; deleting a chat moves its whole folder to the Trash. When a chat turns into work, Continue in workspace has the agent write a handoff summary and starts a new workspace chat with it.

• Always up-to-date specifications. A connected graph of SPEC.md files lives beside the code; the agent reads, searches, and maintains it through dedicated spec_* tools, so project intent persists across sessions. The read-only Specs tool renders the graph as a tree in its own view. Type # and a question in the palette to find the spec sections that answer it, in any word order and word form, ranked the way the agent's own spec_search ranks them. Press ↵ to open the spec at that heading, or ⌥↵ to ask the agent in a new chat when the specs phrase it differently.

• Skills. ThinkRail loads your pi skills and any already in your project. It can also import skills from Claude, Codex, and other coding agents: switch them on in Settings → Extensions, or per project in the Skills dialog, which also shows the size of your skill catalog. A large library is listed within a small prompt budget, and the agent finds the rest with a skill search.

• Agent tools beyond the shell. Thanks to the ThinkRail GUI, your AI agent can ask you structured multiple-choice questions in the chat instead of guessing, draw Mermaid diagrams, and show comparisons and file previews. When the agent proposes a UI change, it shows a before/after mockup you can comment on like a diff.

This is the beginning of the README. Read the rest at the original. Read the full README ↗