Skip to content

KAS: MCP sign-in warning appears in every chat for servers the chat never uses #38457

Open

Description

@kyleseaman

Existing issues

KiroCrew version

0.14.0.dev20261114060535 (running gateway). The notice comes from #36135, merged 2026-11-14, and is unchanged on main b3a9eebe33.

Platform

Linux (Cloud Desktop), dashboard used from a browser on macOS. agent.acp_backend = kas.

What happened

Every new chat on the KAS backend shows this warning row on its first turn, whatever the turn is about:

⚠ notion (an MCP server you added) needs you to sign in before its tools work in this chat. Send a message that names notion, such as "Sign in to notion".

In my case the turn was "ok, can you open the current deck in chrome". Nothing in it related to Notion. I have a Notion MCP server configured but don't use it in these chats, so the row is noise in every session I run. Because it appears in the middle of an unrelated turn, it reads as if the agent tried to reach Notion, which made me worry something was wrong. Nothing was: the row starts no sign-in and calls nothing.

Cause, from src/kiro_crew/dashboard/chat_turn/mcp_session.py (_notice_mcp_sign_in_needed, added in #36135):

  • At session init, KAS starts every configured MCP server and reports unsigned ones as awaiting_auth.
  • The row is posted as soon as that report arrives for any server without a live sign-in card. It doesn't check whether the turn, or the chat, ever wanted that server's tools.
  • It shows once per chat (slot._mcp_sign_in_notice_shown), so every new chat repeats it until the user signs in or removes the server.
  • That flag is in memory only (reset in src/kiro_crew/dashboard/state_parts/slot_session.py), so a chat that already shows the row can show it again after a gateway restart.

Steps to reproduce

  1. Use agent.acp_backend = kas.
  2. Add a remote OAuth MCP server (e.g. Notion) and don't sign in to it.
  3. Open a new chat and send any message unrelated to that server.
  4. The sign-in warning row appears on the first turn. Open another chat: it appears again.

Expected

Stay quiet about an unsigned server until it matters. Options, roughly in order of preference:

  • Show the hint only when it's needed: when the agent tries to use one of that server's tools, or the user's message names the server, and the tool isn't available because sign-in is missing. That's the moment the explanation helps.
  • Otherwise keep it passive: a "needs sign-in" state on the MCP status chip or MCP Servers page, not a warning row in the transcript.
  • If a proactive row stays at all, show it at most once per server per install (persisted across restarts), with a "don't remind me" action. Never repeat it in every chat.
  • Don't post it again after a restart if the transcript already contains one.

The original goal of #36135 still holds: a KAS user who wants a server's tools should learn why they're missing and how to sign in. The fix is about timing, not about removing that path.

Anything else

Related: #34492 (KAS sign-in flow requires naming the exact server), #24871 (clearing ended MCP Authorize cards from the transcript).

Activity

  1. added
    tier:T1Bug: behaviour does not match intent; fix keeps the design
    on Nov 17, 2026
  2. KiroCrewCaptain commented on Nov 17, 2026

    @KiroCrewCaptain
    Collaborator

    Thanks for the report. This issue has been triaged by Crew Captain and will be assigned to a maintainer, who will follow up here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

area: dashboardDashboard UI and its backend handlersbugSomething is not workingtier:T1Bug: behaviour does not match intent; fix keeps the design

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions