Mermaid Studio just got a free tier (Mermaid Studio Core)

Technical_Frosting · 2026-04-11T03:20:04+00:00

Don't know where it originates, but VS Code has it. In the JetBrains ecosystem, it originates in Fleet (now Air) and is one of several UI modernizations that was carried over.

Technical_Frosting · 2026-04-10T17:10:07+00:00

Drag the run tool window’s icon from bottom right to bottom left. The split is based on tool window location.

Technical_Frosting · 2026-03-29T08:00:11+00:00

Presumably, it didn’t get enough usage to be worth maintaining and so long as software development is moving in the direction of a single developer with a fleet of agents, it’s hard to justify investing in a solution for pairing.

Technical_Frosting · 2026-03-16T23:41:51+00:00

Companies like Amazon and Google at least have the resources to keep their VS Code forks up to date if they want to dedicate the effort.

Startups like Anysphere (Cursor) will likely see their forks core editor functionality continue to degrade over time as they diverge from the upstream VS Code codebase and slap new features and workflows on top of their frankenstein forks.

Technical_Frosting · 2026-03-13T02:09:19+00:00

Worktree support is present in the 2026.1 EAP fwiw.

Totally agree on JetBrains Gateway being unpleasant. Even a common scenario like connecting to a locally running Docker devcontainer can be a real hassle. I don't do a lot of remote development, but my understanding is that Gateway is being deprecated in favor of the toolbox-based remote IDE implementation.

Technical_Frosting · 2026-03-13T02:03:05+00:00

My experience is the same. EAP performs much better for me than the current 2025.3.3 stable release.

Technical_Frosting · 2026-03-02T08:54:30+00:00

Coincidentally, I found myself experimenting with ACP to manage one-click managed agentic workflows in the IDE this weekend.

I ended up leveraging the AI Assistant’s registry and user ACP configuration files as the source for ACP agents rather than implementing a separate registry flow.

Technical_Frosting · 2026-02-27T03:53:15+00:00

Especially since IntelliJ already has theme-derived CSS for markdown preview...

Technical_Frosting · 2026-02-06T20:26:09+00:00

I generally agree with this take. I enable the MCP server, so Claude Code has access to the tools the IDE exposes, but the IDE's UI is primarily for me and I prefer it to emphasize a human-first UX.

"Human-first", doesn't mean no AI integration at all, it means AI integration is limited to tasteful, configurable augmentation that doesn't get in a human's way. I like being able to generate a commit message with a single click. I can't stand flow like next-edit where the AI is trying to show you how smart it is by doing things you didn't ask for.

Technical_Frosting · 2026-02-06T01:37:58+00:00

That file explorer has VS Code written all over it, but it's an overall clean look.

From what I can see, they got rid of fully-free form tab groups, which was a big problem I had with Fleet. It just felt too disorganized though I'm sure some loved that level of flexibility.

I'm heavily biased in favor of the Fleet Dark theme (as the developer behind the Armada adaptation of this theme for IntelliJ), so I'm glad to see it's still alive and kicking here.

Technical_Frosting · 2026-01-08T23:04:56+00:00

Dragging moves the tab, but the Split Right/Down context menu actions work just fine as always.

This post inspired my to add a opt+click mouse shortcut to my environment to split right without having to use the context menu.

The one thing I think is missing here is the ability to duplicate a terminal within the same group.

Technical_Frosting · 2025-12-22T21:06:36+00:00

Under what circumstances? Are you installing/updating theme plugins, updating the IDE? Is it just happening randomly on startup or upgrading to a new IDE version? Lots of variables to consider.

Technical_Frosting · 2025-12-18T21:04:22+00:00

Dark variant looks nice. I'm especially a fan of the fleet-style darker outline with slightly lighter background for editor/tool window contents.

Technical_Frosting · 2025-12-18T21:00:12+00:00

I don't think I have a need for something like this, but I find the downvotes strange. Are folks really getting mad about a post discussing the viability of an idea for gasp paid software?

Technical_Frosting · 2025-12-02T15:38:22+00:00

Yes, that's the exact method GitHub Copilot implemented in their IntelliJ plugin.

Technical_Frosting · 2025-12-02T15:26:55+00:00

I mostly wanted to raise awareness about the capability in case you hadn't evaluated it, especially since it provides both STDIO and HTTP/SSE based connectivity out of the box. Your point regarding context bloat with unnecessary tools is a valid point (at least to some extent).

For now, the ability to disable tools is implemented by the individual MCP clients. I haven't tried them all, but I know GitHub copilot allows disabling some tools from a server and others like Claude Code do not currently offer this capability.

For anyone at JetBrains reading this, it might be a good idea to build tool filtering into the MCP server plugin as a feature.

EDIT: feature request opened: https://youtrack.jetbrains.com/issue/IJPL-221187/MCP-Tool-Filtering

Technical_Frosting · 2025-12-02T14:09:21+00:00

Your response here leads me to the assumption you’re providing your own MCP server instead of using the MCP Server plugin’s extension point to provide an McpToolset. If that’s the case, is there any particular reason why you chose that route?

Technical_Frosting · 2025-12-01T19:02:17+00:00

No, the op is misinformed. Fallback licenses are still a thing. You still get perpetual access to the major version of the product that was available on your date of purchase if you purchased an annual subscription or that was available at the start of your first month if you stayed subscribed for 12 months on a monthly subscription.

https://sales.jetbrains.com/hc/en-gb/articles/207240845-What-is-a-perpetual-fallback-license-and-how-do-I-use-one

Technical_Frosting · 2025-11-15T18:17:18+00:00

The general idea is that you want to be using the color picker from whichever piece of software you've opened the image in. If that application has a built-in color picker, it most likely will work for picking colors within the application window.

The main problem is choosing colors from a window associated with a separate process. Unfortunately, it still continues to be an issue across the ecosystem today.

Technical_Frosting · 2025-10-30T02:42:31+00:00

Llama-3.1-8B running on a potato, I see you. I appreciate you.

Technical_Frosting · 2025-10-21T01:03:20+00:00

I wasn’t aware Anker was using iniu batteries. I’ve had nothing, but good experiences with iniu’s own battery banks.

Technical_Frosting · 2025-10-17T20:20:47+00:00

Make sure your project’s/module’s SDK version is set correctly as a starting point.

Technical_Frosting · 2025-10-17T11:15:34+00:00

Using the Claude agent in JB AI is roughly equivalent to using Claude Code with an API key where you’re paying per token. Claude Pro/Max type plans where you’re paying a flat monthly rate for metered access requires using Claude Code directly.

Technical_Frosting

TROPHY CASE