--- title: The "LSP Moment" for AI Agents: WebStorm ACP | daily.dev description: WebStorm now supports the Agent Client Protocol (ACP), an open standard that decouples the IDE from AI agents — analogous to what LSP did for language tooling.... canonical: https://daily.dev/posts/the-lsp-moment-for-ai-agents-webstorm-acp-wgebx0n8r twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: The "LSP Moment" for AI Agents: WebStorm ACP | daily.dev og:description: WebStorm now supports the Agent Client Protocol (ACP), an open standard that decouples the IDE from AI agents — analogous to what LSP did for language tooling.... og:url: https://daily.dev/posts/the-lsp-moment-for-ai-agents-webstorm-acp-wgebx0n8r og:image: https://api.daily.dev/og/posts/WgeBx0N8R.png og:image:alt: The "LSP Moment" for AI Agents: WebStorm ACP og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # The "LSP Moment" for AI Agents: WebStorm ACP **[JetBrains](https://daily.dev/sources/jetbrains)** · 7 min read · 0 upvotes · 0 comments ## Summary WebStorm now supports the Agent Client Protocol (ACP), an open standard that decouples the IDE from AI agents — analogous to what LSP did for language tooling. ACP lets developers connect any ACP-compliant agent (GitHub Copilot, Claude Code, custom agents) directly to WebStorm without requiring a JetBrains AI subscription. Teams can orchestrate multiple specialized agents — switching between them for tasks like Figma-to-code conversion, refactoring, code review, or documentation — while keeping WebStorm's local indexing and code intelligence intact. A new Chrome Connect integration (built with Google's Chrome DevTools team) lets agents read console logs and network requests to verify fixes in the browser. For teams, ACP supports BYOK, data compliance boundaries, and custom agent deployment with internal project knowledge. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What is the Agent Client Protocol (ACP) and how does it work with WebStorm? ACP is an open standard that decouples the IDE from the AI agent, the same idea as the Language Server Protocol but for AI agents. It standardizes how an IDE sends context like files, diffs, and terminal output to an agent, and how the agent sends back actions such as file edits, tool calls, and shell commands. WebStorm supports ACP, letting developers use any ACP-compliant agent, including GitHub Copilot's ACP server or Claude Code's official ACP adapter, without a required JetBrains AI subscription. _daily.dev helps developers track how emerging standards like ACP reshape which AI agents work with their IDE._ ### Do I need a JetBrains AI subscription to use third-party AI agents in WebStorm? No, with ACP support in WebStorm, teams with an existing subscription to Anthropic, OpenAI, or Google can use it directly without an additional JetBrains AI subscription. JetBrains AI still exists as a convenient way to manage multiple models in one place, but it is no longer the only option. Teams can also bring their own key (BYOK) and point agents to backends like Azure, AWS, Anthropic, or local LLMs. _Compare AI coding tool subscription costs and lock-in tradeoffs on daily.dev before committing your team's budget._ ### Why would a developer use multiple AI coding agents instead of just one? Because no single agent excels at every task: independent benchmarking of Figma-to-code work found agents scoring well on component architecture (3.3 to 3.6 out of 5) dropped sharply on design token extraction (1.7 to 2.9). Agents are trained on different data and specialize differently, so one might excel at Figma-to-component conversion, another at reasoning through messy refactors, and another at debugging via stack traces. _daily.dev surfaces agent benchmark data so developers can pick the right AI tool for each coding task._ ## Similar posts on daily.dev - [How to Use AI Agents in IntelliJ IDEA With ACP](https://daily.dev/posts/how-to-use-ai-agents-in-intellij-idea-with-acp-kuctw5rln) · JetBrains · 0 upvotes · 0 comments - [JetBrains throws support behind Agent Client Protocol](https://daily.dev/posts/jetbrains-throws-support-behind-agent-client-protocol-okvfpnxqm) · The Register · 0 upvotes · 0 comments - [Specialized IDEs deserve AI too: Kiro adopts ACP](https://daily.dev/posts/specialized-ides-deserve-ai-too-kiro-adopts-acp-lin59ouze) · Kiro · 0 upvotes · 0 comments - [Our 2026 Direction: AI and Classic Workflows in JetBrains IDEs](https://daily.dev/posts/our-2026-direction-ai-and-classic-workflows-in-jetbrains-ides-rtcomvlpw) · JetBrains · 0 upvotes · 0 comments --- Tags: [#devtools](https://daily.dev/tags/devtools), [#ai-coding](https://daily.dev/tags/ai-coding), [#jetbrains](https://daily.dev/tags/jetbrains) [View this post on daily.dev](https://daily.dev/posts/the-lsp-moment-for-ai-agents-webstorm-acp-wgebx0n8r) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"The \"LSP Moment\" for AI Agents: WebStorm ACP","url":"https://daily.dev/posts/the-lsp-moment-for-ai-agents-webstorm-acp-wgebx0n8r","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/the-lsp-moment-for-ai-agents-webstorm-acp-wgebx0n8r"},"datePublished":"2026-08-11T15:16:08.721Z","dateModified":"2026-09-14T07:16:53.939Z","description":"WebStorm now supports the Agent Client Protocol (ACP), an open standard that decouples the IDE from AI agents — analogous to what LSP did for language tooling....","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/b2b02791fb8fa9de4fa083de7384a953?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/b2b02791fb8fa9de4fa083de7384a953?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"JetBrains","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"JetBrains","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/53ecf0c676f34b3896ee109609d91efa","url":"https://daily.dev/sources/jetbrains"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/the-lsp-moment-for-ai-agents-webstorm-acp-wgebx0n8r","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"devtools,ai-coding,jetbrains","timeRequired":"PT7M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"JetBrains","item":"https://daily.dev/sources/jetbrains"},{"@type":"ListItem","position":3,"name":"The \"LSP Moment\" for AI Agents: WebStorm ACP"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/the-lsp-moment-for-ai-agents-webstorm-acp-wgebx0n8r#faq","mainEntity":[{"@type":"Question","name":"What is the Agent Client Protocol (ACP) and how does it work with WebStorm?","acceptedAnswer":{"@type":"Answer","text":"ACP is an open standard that decouples the IDE from the AI agent, the same idea as the Language Server Protocol but for AI agents. It standardizes how an IDE sends context like files, diffs, and terminal output to an agent, and how the agent sends back actions such as file edits, tool calls, and shell commands. WebStorm supports ACP, letting developers use any ACP-compliant agent, including GitHub Copilot's ACP server or Claude Code's official ACP adapter, without a required JetBrains AI subscription. daily.dev helps developers track how emerging standards like ACP reshape which AI agents work with their IDE."}},{"@type":"Question","name":"Do I need a JetBrains AI subscription to use third-party AI agents in WebStorm?","acceptedAnswer":{"@type":"Answer","text":"No, with ACP support in WebStorm, teams with an existing subscription to Anthropic, OpenAI, or Google can use it directly without an additional JetBrains AI subscription. JetBrains AI still exists as a convenient way to manage multiple models in one place, but it is no longer the only option. Teams can also bring their own key (BYOK) and point agents to backends like Azure, AWS, Anthropic, or local LLMs. Compare AI coding tool subscription costs and lock-in tradeoffs on daily.dev before committing your team's budget."}},{"@type":"Question","name":"Why would a developer use multiple AI coding agents instead of just one?","acceptedAnswer":{"@type":"Answer","text":"Because no single agent excels at every task: independent benchmarking of Figma-to-code work found agents scoring well on component architecture (3.3 to 3.6 out of 5) dropped sharply on design token extraction (1.7 to 2.9). Agents are trained on different data and specialize differently, so one might excel at Figma-to-component conversion, another at reasoning through messy refactors, and another at debugging via stack traces. daily.dev surfaces agent benchmark data so developers can pick the right AI tool for each coding task."}}]} ```