GitHub - JetBrains/thinkrail: ThinkRail is the agentic IDE that gets better every time you use it
ThinkRail is the agentic IDE that gets better every time you use it - JetBrains/thinkrail
ThinkRail is the agentic IDE that gets better every time you use it - JetBrains/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.
*From the left: An isolated workspace, a work session with an AI agent in that workspace, the code change made by the agent, and the spec tree.*
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.
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.
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; in a browser, the agent's mockups are clickable prototypes whose scripts run in a sandbox with no network access. Any HTML file, from a mockup to a generated report, opens in your browser from its tab, its preview or the Files menu. When a question's options come with mockups, open them full screen to flip through them, put two side by side (two HTML mockups scroll together and also compare with a swipe or an overlay), or see them all at once, and pick one right there.
pi package by source (npm, git or a local folder), for you or for a repository, showing what each one adds and letting you switch individual packages, their extensions and skills, and pi's built-ins on or off.pi packages: pi install npm:@thinkrail/pi-ask-user-question for the questions @thinkrail/pi-ask-user-question) and pi install npm:@thinkrail/pi-visualize for the diagrams and previews @thinkrail/pi-visualize), so a vanilla pi in the terminal gets the same tools.Your own model servers. Go to Settings → Providers → Custom servers and connect a company LLM gateway or a model running on your own machine. Any OpenAI-compatible server fits: LiteLLM, sglang, vLLM, Ollama, LM Studio, or llama.cpp.
pi's models.json. The models models appear in the chat model picker, and in the pi CLI alike.
*The project's spec graph as a tree (on the right), with the spec itself rendered alongside in the center.*
Download the thinkrail-desktop-* asset for your platform:
Linux x64 / ARM64: extract the setup tarball and run installer. Desktop builds need glibc 2.38+ with GTK 3, WebKitGTK 4.1, Ayatana AppIndicator 3, librsvg 2, and Ubuntu 24.04 or newer, plus libnotify-bin for desktop notifications:
sudo apt install libgtk-3-0 libwebkit2gtk-4.1-0 libayatana-appindicator3-1 librsvg2-2 libnotify-bin
There are two update channels: stable and nightly. If the ThinkRail desktop app, you can check them in Settings → Updates: Download → Preparing update → Install & Restart.
The installer downloads the right binary, verifies its SHA-256 checksum, and puts thinkrail on your PATH.
macOS / Linux (also Windows under Git Bash):
curl -fsSL https://raw.githubusercontent.com/JetBrains/thinkrail/main/install.sh | bash
Windows: the same command works from cmd and PowerShell:
powershell -c "irm https://raw.githubusercontent.com/JetBrains/thinkrail/main/install.ps1 | iex"
Then run thinkrail, optionally with a git repo to open as a project:
thinkrail ~/code/my-repo
thinkrail needs git on your PATH and a model provider. You can sign in with JetBrains AI from the app or use your own provider credentials. The first launch walks you through connecting a provider and picking a project; Start a new project creates an empty git repository (under ~/thinkrail by default), so you don't need one ready.thinkrail --help lists the flags, and thinkrail --version prints the build.curl -fsSL https://raw.githubusercontent.com/JetBrains/thinkrail/main/install.sh | bash -s -- --channel nightly curl -fsSL https://raw.githubusercontent.com/JetBrains/thinkrail/main/install.sh | bash -s -- --channel stable --version 0.3.1 curl -fsSL https://raw.githubusercontent.com/JetBrains/thinkrail/main/install.sh | bash -s -- --channel nightly --version 0.4.0-nightly.2
On Windows the options are environment variables (THINKRAIL_CHANNEL, THINKRAIL_VERSION, THINKRAIL_PREFIX, THINKRAIL_NO_MODIFY_PATH):
$env:THINKRAIL_CHANNEL='nightly'; irm https://raw.githubusercontent.com/JetBrains/thinkrail/main/install.ps1 | iex # PowerShell set "THINKRAIL_CHANNEL=stable" && set "THINKRAIL_VERSION=0.3.1" && powershell -c "irm https://raw.githubusercontent.com/JetBrains/thinkrail/main/install.ps1 | iex" # cmd
If you keep ThinkRail running, it periodically checks for updates and, when it finds one, shows an "Update available" button in the GUI.
thinkrail uninstall removes the executable, the PATH entry the installer added, and the install metadata; it then asks whether to delete your ~/.thinkrail app state (kept by default; --remove-data deletes it, and -y skips the questions).
If you prefer a manual install, download a binary and the SHA256SUMS from the releases page, and verify the checksum. For self-update to work, rename it to thinkrail (thinkrail.exe on Windows) and place it at <prefix>/bin/thinkrail[.exe]; a binary kept under its release filename or elsewhere must be replaced manually or reinstalled with the script.
| Platform | Desktop | CLI |
|---|---|---|
| macOS Apple Silicon / Intel | DMG | signed binary |
| Windows x64 | signed setup executable and app binaries | signed .exe |
| Linux x64 / ARM64 | setup tarball, unsigned | unsigned |
JetBrains signs the Windows CLI, the desktop setup executable, and every executable and DLL the desktop app installs. The macOS CLI is signed but not yet notarized. Signed and notarized desktop DMGs must come from the coordinated JetBrains service pipeline; older published DMGs and locally built packages may still be unsigned and blocked by Gatekeeper. Linux artifacts are unsigned.
ThinkRail apps collect basic usage events: launches, chat creation, message sends, and provider connections. The data is tied to a random installation ID. Usage analytics never include prompts, code, files, credentials, or account identity. Error reports are always sent as well, tied to the same installation ID, so we can fix crashes: they include the error type and code, and where in ThinkRail's own code it happened. They never include error messages, file paths, names, URLs, or anything from your projects or extensions.
Additional product usage is shared only while Share additional usage data is on; the switch is offered during first-run setup (or right after you skip it) and lives in Settings → Privacy. From the command line, thinkrail --no-analytics (or THINKRAIL_NO_ANALYTICS=1) turns additional sharing off for that launch. With additional sharing on, a packaged build may open the ThinkRail blog in your browser once to link your installation to the website visit that brought you here - only where you accepted marketing cookies on the website or no consent is required, and that link expires after 30 days.
Feedback surveys are separate from usage analytics. ThinkRail may invite you to a short survey, and you can also open it from Settings → Feedback. Your answers, including anything you type, are sent to the ThinkRail team only when you press Send, and tied to the same random installation ID, not to your name or account. Please don't include secrets, code, or personal data. To have your answers deleted, email info@thinkrail.ai.
The ThinkRail apps and the ThinkRail website (thinkrail.ai) use PostHog Inc. services for analytics. The website also uses PostHog Surveys to collect feedback after a desktop download and, only if you choose to provide it, your email address, which is used to ask for further feedback and to send product updates. PostHog's privacy policy is at posthog.com/privacy.
ThinkRail is a thin host that runs pi in-process and bridges it to a web UI. pi owns models, skills, compaction, cost, and session state. ThinkRail owns workspace management, the GUI, and the contracts between the engine and the GUI.
packages/server + packages/shared): a Bun.serve HTTP+WS host with one in-process pi session per chat, launched by apps/cli or apps/desktop.packages/contracts): the typed, versioned protocol between the engine and the GUI.apps/web): React 19 + Zustand + Tailwind v4, shipped independently; it communicates with the engine through the contracts.goal-and-requirements.md and architecture.md are the product and design specs. ThinkRail is developed spec-first: a SPEC.md sits beside every module, and when a change made by an AI agent moves a boundary or a contract, the spec is updated in the same change.
You need Bun 1.4.4 (the pinned package manager and runtime), Node.js ≥ 22.23.4 (the in-process pi
engine needs ≥ 22.19; the website build and typecheck need ≥ 22.23.4 for Astro 7.4), and an AI provider for
agent work.
git clone https://github.com/JetBrains/thinkrail.git cd thinkrail bun install bun run dev # host + web client together; Ctrl+C stops both
bun run --filter @thinkrail/cli dev # browser launcher bun run build:binary # standalone CLI artifact bun run desktop:dev # package and open the Electrobun app bun run desktop:build # package without opening it
CONTRIBUTING.md covers the checks, the end-to-end suites, desktop packaging, and the repository layout.
Contributions are welcome. See CONTRIBUTING.md. This project and community are governed by the Code of Conduct.
Join us on Discord to ask questions, share what you're building, and talk to the team. Bugs and feature requests go to GitHub issues.
Licensed under the Apache License 2.0.
Texto de github.com tal como lo publicó, leído de su página y mostrado aquí con el formato de El Autómata. El original, en github.com · Volver a la noticia de El Autómata