JetBrains Releases GoLand 2026.3, Enabling AI Agents to Directly Operate Profiler for Go Performance Diagnosis
GoLand 2026.3 introduces features allowing AI coding agents like Claude Code to automatically analyze CPU and memory performance data via MCP tools to locate code bottlenecks.
Software developer JetBrains has released version 2026.3 of its Go integrated development environment, GoLand. A key update opens the built-in profiler to direct operation by AI agents. Developers can describe issues such as slow API responses, high CPU usage, or increasing memory consumption, and supported AI coding agents (including Claude Code, Codex, and Junie) can start the program, collect performance data, and identify resource-intensive functions and code locations.
This functionality is implemented through the built-in goland-profiler skill and Model Context Protocol (MCP) tools. If a developer has already started the program via the profiler, the AI agent can take over that execution; otherwise, the agent starts the program based on the project's run configuration, requiring no additional analysis code in the source. The AI agent selects appropriate analysis methods based on the problem type: recording CPU performance data during high load, capturing blocking and mutex analysis for synchronization waits or lock contention, or comparing memory usage at different times to check for resource leaks when memory consumption increases.
Each performance analysis dataset includes a summary listing up to five top resource-consuming functions along with their resource usage, call paths, and code lines. When the summary is insufficient to determine the cause, the AI agent can use MCP tools to further query function rankings, call paths, and source code locations, then propose improvements. Built-in skills also instruct the agent to distinguish between actual measured results and its own inferred causes. Developers can open Flame Graphs to verify AI judgments, or manually capture performance data for AI analysis.
Current limitations apply: GoLand's profiler must modify the executable at compile time to provide the necessary interface for analysis, so it cannot directly attach to programs not started in profiling mode. Since performance analysis requires collecting samples during program execution, this feature is best suited for long-running applications like servers and background workers, and less effective for command-line tools that exit immediately after execution.