The JetBrains terminal parses with libghostty
JetBrains says IDE terminals from the 2026.3 line parse with libghostty instead of JediTerm. The IDE still draws the terminal. The engine is on by default in the early builds.
The short version
JetBrains says libghostty now parses and holds terminal state, starting with the 2026.3 builds. The IDE still does the drawing. JediTerm remains a registry fallback.
The blog
JetBrains published a platform post saying the built-in terminal in its IDEs runs on libghostty starting with the 2026.3 line. Libghostty is the terminal-emulation library from the Ghostty project. JetBrains says it replaces JediTerm for parsing and for terminal state. The IDE still handles rendering and the higher-level features. The post says the engine is already on by default in the 2026.3 early-access builds and will stay on through beta, release candidate, and the stable release. YouTrack issue IJPL-218849 is the ticket the post points at for comments.
What changed for a person at the prompt
The blog's user-facing claim is protocol support. It says the Kitty keyboard protocol lets a terminal program tell Enter apart from Shift-Enter and Control-Enter, and that an older Vim protocol is supported as well. It also says the terminal answers a dark-or-light query from the current IDE theme. Those are JetBrains's descriptions of behavior. This page does not retest a build. The ffmpeg pin on this desk was a version choice inside a house project. This post is a vendor saying which library parses the IDE terminal.The ffmpeg pin.
The fallback
JetBrains says a user who hits trouble can switch back to JediTerm. The blog names the registry flag terminal.use.ghostty.emulator and asks for a report on the YouTrack issue. Naming that flag is the rollback the vendor documented. It is not a tuning guide, and this page will not expand it into a tour of the registry. The Node October release was a patch level on a language runtime. This is a library swap inside an IDE, with the old parser left as a switch. Asked directly, Does the October blog cancel that September note? The October blog says the engine is on by default in 2026.3. It does not say the September Windows note was withdrawn.The Node October patch.
Ghostty's side
Ghostty describes libghostty as the embeddable library, with libghostty-vt as the piece that parses sequences and holds terminal state. A discussion opened on September 18, 2026, by a JetBrains engineer says Windows resize behavior was not compatible with ConPTY, and that the IDE terminal could not ship on Windows without a fix. The October JetBrains post does not say Windows is excluded, and it does not say that September note is closed. Both documents stand. A reader on Windows should treat the September note as an open engineering comment, not as a retraction of the October announcement.systemd's Rust leaves.
What this page will not claim
The blog lists sequences the library can parse that the IDE does not yet act on, including clipboard, notifications, progress, and graphics. Parsing support is not a feature a user can already see. This page will not mark those as shipped. Reddit's token rule was a forum policy. It is linked because both pieces are about a project choosing a boundary: JetBrains chose a parser, and the forum chose a credential rule. Asked directly, What did a JetBrains engineer say about Windows in September? In a Ghostty discussion on September 18, the engineer said Windows resize behavior was not yet compatible with ConPTY.Reddit's token rule.
A library is not the application
Libghostty inside an IDE is not the Ghostty application, and it is not a claim that every JetBrains terminal feature has moved. JetBrains was explicit that rendering stays in the IDE. The Linux 7.4 short-slice brief was a scheduler change in a kernel. The KVM pull filed today is another kernel merge. The IDE terminal is a desktop component. The three should stay distinct. Asked directly, What does JetBrains say libghostty replaced? JediTerm, for parsing and terminal state. The IDE still handles rendering and the integrations around it.The short slice.
The record
The record is the JetBrains blog for the 2026.3 default, YouTrack IJPL-218849 for the tracking ticket, and the September Ghostty discussion for the Windows resize comment. The parser named in the October post is libghostty. The parser it replaces, for state, is JediTerm. The drawing code, JetBrains says, is still the IDE's. The short answer this page will stand on is this: JetBrains says libghostty now parses and holds terminal state, starting with the 2026.3 builds. The IDE still does the drawing. JediTerm remains a registry fallback.
Filed on software
This is a software filing because the dependency is which library an IDE uses to parse a terminal. Ghostty itself is an open-source project, and the September discussion lives on its tracker. The announcement that changes the IDE is JetBrains's. One filing is enough. A second brief on the Ghostty application would need a Ghostty release note this page does not have. Asked directly, Which JetBrains line uses libghostty? The 2026.3 line. JetBrains says the engine is on by default in the EAP builds and stays on through beta, release candidate, and stable.
What a reader can check
A reader with a 2026.3 early-access build can see whether the new engine is the one the blog describes, and can use the registry flag the blog names if it is not. This page did not run that build. The alloc pin was a house crate choice, not a leaderboard. The same restraint applies here: a vendor post is a vendor post, not a measurement this desk repeated. Asked directly, How does JetBrains say a user switches back? The blog names a registry flag, terminal.use.ghostty.emulator, and points reports at YouTrack issue IJPL-218849.The alloc pin.
Sources
The reports this brief is filing. Futureweb did not republish them.
Questions
Which JetBrains line uses libghostty?
The 2026.3 line. JetBrains says the engine is on by default in the EAP builds and stays on through beta, release candidate, and stable.
What does JetBrains say libghostty replaced?
JediTerm, for parsing and terminal state. The IDE still handles rendering and the integrations around it.
How does JetBrains say a user switches back?
The blog names a registry flag, terminal.use.ghostty.emulator, and points reports at YouTrack issue IJPL-218849.
What did a JetBrains engineer say about Windows in September?
In a Ghostty discussion on September 18, the engineer said Windows resize behavior was not yet compatible with ConPTY.
Does the October blog cancel that September note?
The October blog says the engine is on by default in 2026.3. It does not say the September Windows note was withdrawn.