KuaDashboard

English

Español

English

Español

Appearance

KUA for VS Code ​

Next release

The KUA extension for VS Code comes with the next KUA release after 2.0.0, which attaches its .vsix to the release. Until then, build it from the repository with npm ci && npm run package in vscode/.

The KUA extension brings your local KUA into VS Code:

  • Status bar: whether KUA runs on this computer, its version and plan, and whether AI agents are allowed. Click it for the commands.
  • MCP server for the chat: with KUA open, the editor's chat (Copilot in agent mode and any client that uses the VS Code MCP API) gets KUA's tools without editing any file. The extension starts the MCP server of the KUA you have installed, so both always have the same version. With KUA closed the server still starts and tells the agent to open KUA.
  • Applications view: the KUA icon of the activity bar lists your KUA Applications with what needs attention (the same text as KUApps: thresholds broken, resources that no longer exist, failed collections), their resources with the signal state, and the product Advisor. The application of this workspace comes first and expanded: the one set in kua.application (Link this workspace to a KUA Application in the view), or the only one whose GitHub repository, set in KUA or declared by its workloads, matches the workspace's origin. Each item has Open in KUA (that application and tab in KUA) and Send to chat, which gives the editor's chat KUA's brief of an issue, an Advisor finding or the whole Advisor, without credentials or raw logs; in an editor without a chat the brief is copied. The view is refreshed when the window gets focus, when KUA starts or stops and with its refresh button, and only reads KUA's local API.
  • KUA: Open dashboard opens the desktop app (kua://open), or the browser for a KUA run from the repository. Setting kua.openIn chooses app or browser.
  • KUA: Verify MCP connection starts the server like the chat does and reports the tools and profiles it reached, or the error.
  • KUA: Add MCP server to this workspace writes the kua entry to .vscode/mcp.json, keeping other servers and comments, for editors that read that file but not the extension API. An invalid file is not overwritten.
  • KUA: Add KUA steering to this workspace for Kiro writes .kiro/steering/kua.md (see Kiro).

Kiro ​

Kiro is built on VS Code, so the same extension installs in Kiro from the .vsix (or Open VSX). Kiro gets KUA's tools from its own MCP file: use Install in KUA's Connect an AI agent → Kiro, which covers the Kiro IDE and kiro-cli.

KUA: Add KUA steering to this workspace for Kiro adds a steering file that Kiro's agent always reads: how to work with KUA, the same rules as the kua skill of the Claude Code plugin. Start from the Advisor and log intelligence, check the current state before changing infrastructure, show the cost and ask before billed or destructive operations, change KUA Applications only through a preview the user approves, and never copy credentials or raw logs into the repository. A kua.md you edited is only replaced if you confirm it. Commit it so the whole team's Kiro gets it.

What Kiro reads through KUA stays on this computer: KUA's inventory, Advisor findings, log intelligence over cached logs and KUA Applications, through the local MCP server. Cloud credentials stay in KUA.

Prompts to try in Kiro:

  • "Use KUA's Advisor for the AWS profile of this project and fix the findings that the Terraform in infra/ can fix. Show me the diff."
  • "Which recurring error grew the most in the logs of orders-api this week? Find where it comes from in this repository."
  • "What needs attention in the KUA Application of this repository, and which of it can I fix from the code?"

KUA is not packaged as a Kiro Power yet: a Power carries a fixed MCP command, while KUA's depends on where KUA is installed on each computer, which KUA's own install already writes.

Install ​

Until the extension is in the Marketplace and Open VSX, install the .vsix from the release: Extensions → … → Install from VSIX…. It needs VS Code 1.101 or later for the chat integration.

KUA is found by itself, whatever its port (the same way as the MCP server). Set kua.url (for example http://localhost:7192) to use a specific one.

The extension runs on the computer where KUA runs, also when the editor is connected to Remote SSH, WSL or a Dev Container.

Privacy ​

The extension only talks to the KUA on this computer (127.0.0.1) and does not read or store cloud credentials. Agents read through KUA, every change to KUA Applications is previewed and approved in KUA, and turning agents off in KUA's tray panel refuses them all.