惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

Stack Overflow Blog
Stack Overflow Blog
云风的 BLOG
云风的 BLOG
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
Recent Announcements
Recent Announcements
Microsoft Security Blog
Microsoft Security Blog
Microsoft Azure Blog
Microsoft Azure Blog
J
Java Code Geeks
D
DataBreaches.Net
U
Unit 42
P
Proofpoint News Feed
I
InfoQ
Apple Machine Learning Research
Apple Machine Learning Research
Google DeepMind News
Google DeepMind News
博客园 - Franky
博客园_首页
IT之家
IT之家
博客园 - 叶小钗
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
酷 壳 – CoolShell
酷 壳 – CoolShell
博客园 - 【当耐特】
Hugging Face - Blog
Hugging Face - Blog
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
阮一峰的网络日志
阮一峰的网络日志

Nx Blog

Sharing Tailwind CSS Styles Across Apps in a Monorepo | Nx Blog How SiriusXM Stays Competitive by Iterating and Getting to Market Fast | Nx Blog Agentic Experience Is the New Developer Experience | Nx Blog Nx Joins the Linux Foundation and the Agentic AI Foundation | Nx Blog A Monorepo Is NOT a Monolith | Nx Blog Why we deleted (most of) our MCP tools | Nx Blog Teach Your AI Agent How to Work in a Monorepo | Nx Blog How Broadcom stays efficient and nimble with monorepos | Nx Blog Why Monorepos are King in the Age of AI | Nx Blog Nx 2026 Roadmap: Expanding Agent Autonomy, Improving Performance, Better Polyglot and More | Nx Blog End to End Autonomous AI Agent Workflows with Nx | Nx Blog Autonomous Agents at Scale | Nx Blog Scaling 700+ Projects: How Nx Became a 'No-Brainer' for Caseware | Nx Blog Configure Tailwind v4 with Angular in an Nx Monorepo | Nx Blog The Missing Multiplier for AI Agent Productivity | Nx Blog A Year of Nx Webinars | Nx Blog Wrapping Up 2025 | Nx Blog Nx 22.3 Release: Angular 21 Support, tsgo Compiler, and Prettier v3 | Nx Blog Nx Cloud Release: Agent Resource Usage | Nx Blog Nx Platform Outperforms DIY Cache by 5x | Nx Blog An Nx Carol: Past, Present, and Future of Your Monorepo | Nx Blog Nx 22.1 Release: Terminal UI on Windows, Storybook 10, Vitest 4, and more! | Nx Blog The Compounding Effect: How Nx Features Multiply Performance Gains | Nx Blog 10 Monorepo Myths Debunked: Separating Fact from Fiction | Nx Blog Nx Cloud Release: Enterprise Task Analytics | Nx Blog Watch and Rebuild Storybook Dependencies with Nx | Nx Blog Book - React for Enterprise: Timeless Architecture for Enterprise Apps | Nx Blog Beyond Remote Cache: Unlock 70% More CI Performance | Nx Blog Nx 22 Release: Expanding the build platform | Nx Blog What's the Point of Generating All This Code If You Can't Merge It? | Nx Blog
Your AI Assistant Can Now Read Your Terminal: Real-Time D...
Juri Strumpflohner · 2025-05-29 · via Nx Blog

One of the most frustrating aspects of working with AI coding assistants has been their inability to see what's happening in your terminal. When your development server crashes with an error, you'd have to manually copy the error message, paste it into your chat, and explain the context.

Not anymore. We've just shipped an integration that allows your AI assistant to access your Nx terminal, the tasks that are currently running as well as their output. This opens up a whole new interaction workflow where you don't have to provide context: the LLM "would just know" about it. Let's dive in.

Let's backtrack for a second - what's this actually about?

Besides helping you write new code, LLMs are also great at helping you debug issues. Stacktraces are ideal for that because they provide a lot of information. To involve your AI assistant, you'd usually copy & paste the stacktrace to your chat window, or use the "Add to Chat" functionalities of editors.

While this works perfectly, we figured we can do better. We want to open up the workflow so that the LLM can independently - even as part of a separate interaction - just grab the necessary context from the terminal to satisfy a user request with more precision.

To demo that, I can just ask What's currently running in my terminal or even more concretely Help me fix my broken dev server:

As a side note, for convenience, we also added a shortcut directly to our Nx terminal UI that allows you to send the output to a new LLM chat conversation.

Technical architecture: How does this actually work?

This integration leverages several components working together:

  • Nx Console as the MCP Host: Nx Console acts as the Model Context Protocol (MCP) host, providing the communication bridge between your AI assistant and the Nx ecosystem.

  • JSON RPC Communication: When you launch the new Nx terminal UI, Nx Console establishes a JSON RPC server that creates a communication channel between the terminal running your tasks, the Nx Console instance in your editor, and your AI assistant through the MCP.

  • Nx Terminal UI: The new Nx Terminal UI connects to this RPC server to send updates on the current tasks that are run, their state and output.

When the LLM assistant requires knowledge about the tasks or terminal output, it communicates via the Nx MCP hosted by Nx Console, which in turn returns the relevant data.

Some things to point out here:

  • This also works if you run the Nx TUI in another terminal, like Warp. It doesn't have to run within VSCode or Cursor. As long as Nx Console runs in one of the editors (for this workspace), the Nx TUI would be able to connect to it.
  • All of this is also made in a way that it is "workspace-aware", ensuring that the terminal communication is tied to the correct workspace instance, so you don't get confused data if you have multiple Nx workspaces running simultaneously.

Why this integration is powerful

This terminal integration gives your AI assistant complete visibility into the three critical areas of your development workflow:

  • Source Code: Your LLM already has access to your codebase, which gets significantly enhanced by the Nx MCP's higher-level structural understanding of workspace architecture, project relationships, and monorepo organization.

  • Browser Environment: For web applications, you can combine this with browser monitoring tools like Playwright MCP or BrowserTools MCP to give your AI assistant access to console logs, network requests, and browser dev tools data.

  • Terminal Output: And now, with this new feature, your AI assistant has direct access to terminal processes, build outputs, error logs, and running tasks.

But this isn't just about convenience (though never having to copy-paste stack traces again is pretty amazing). The real power lies in autonomous context retrieval: your LLM can now independently call into terminal processes and output logs whenever it determines this information might be useful to satisfy your request, without you explicitly saying "fix my terminal" or "look at the terminal."

Getting started

To use this feature, you'll need:

  1. Nx Console installed in your editor
  2. The Nx MCP server configured for your AI assistant
  3. The new Nx terminal UI (available in the latest version of Nx)

Once set up, simply run your development tasks through Nx and start asking your AI assistant for help when issues arise.

Looking forward

This terminal integration represents another crucial step in our core mission at Nx: improving developer experience and making LLMs truly usable for large-scale workspaces. The key to achieving this lies in providing LLMs with comprehensive context, enabling them to make better-informed decisions rather than operating in isolation.

Large monorepos present unique challenges that generic AI assistants simply can't handle effectively without deep contextual understanding. By systematically exposing different layers of your development environment to LLMs, we're building a complete picture that enables truly intelligent assistance:

  • Workspace Structure Context: Through our MCP integration, LLMs gain architectural awareness of your monorepo - understanding project relationships, dependencies, and organizational patterns that are crucial for making informed development decisions.

  • CI Pipeline Context: Our CI integration provides LLMs with real-time visibility into build failures, test results, and deployment status, enabling proactive problem-solving before issues compound.

  • Terminal Context: And now, with this terminal integration, LLMs have access to local development processes, build outputs, and runtime errors - completing the picture of your development environment.

This isn't just about convenience (though never having to copy-paste stack traces is pretty amazing). It's about fundamentally changing how AI assistants understand and interact with complex development workflows. When an LLM has visibility into your workspace architecture, your CI pipeline status, and your local terminal output, it can provide contextually relevant assistance that actually scales with your codebase complexity.

We're already working on even more "agentic" features that will further enhance this integrated experience, making your AI assistant a reliable peer programmer that actually provides value.


Learn more: