🐛 Bug - Processing shows Success when MCP server is signed out (no GitHub create issue credentials)

[KostaMadorsky]

Cc: @calumjs @ricksu978 @adamcogan
Hi Kosta

🟥 Watch the video (2 min 34 sec)

Pain

When the user has been signed out / disconnected from the MCP server (e.g., GitHub Create Issue credentials unavailable), YakShaver processing can report Success even though the core action (creating the GitHub issue) did not occur. This is confusing because the user believes their YakShaver was processed and an issue was created, but no issue number exists and the run ends with a limitation message.

Reproduce Steps

1. Ensure the GitHub MCP tool is not available (e.g., sign out / disconnect MCP server so GitHub create issue credentials are unavailable)
2. In YakShaver, record a YakShaver that should create a GitHub issue
3. Process the YakShaver
4. Observe that the UI reports Success but no issue number is produced
5. Reprocess with prompts like “don’t just draft it, actually create an issue”
6. Observe it still reports Success while the run ends with a limitation message like “no GitHub create issue tool credentials available in this session”
7. Observe it adds a link to a new issue creation page as a link for the Shave in the list of Shaves, e.g. https://github.com/SSWConsulting/SSW.Tiger/issues/new

Expected Behavior

If YakShaver cannot create the issue because the required MCP tool is disconnected / unauthenticated, the processing result should be reported as Failure (or otherwise clearly “Not completed”) with an explicit reason, and the UI should clearly indicate the MCP connectivity/auth status that caused the failure.

Acceptance Criteria

• When a run requires a GitHub MCP tool but credentials are unavailable, the final run result is not reported as Success
• The run summary clearly states the failure reason (e.g., “GitHub MCP not connected” / “No GitHub create issue tool credentials available in this session”)
• The UI provides a clear, always-visible indicator of MCP connectivity/auth status (at least for configured MCPs)
• When issue creation does not occur, no “Issue created” success state is shown and no empty/missing issue number is presented as success

Tasks

• Investigate
• Fix

More Information

This seems to occur after some time (possibly after an update) where previously-connected MCP tooling becomes disconnected. Long-term, consider a spike for architecture that allows the agent to dynamically detect required MCPs and prompt/connect as needed.

Environment

• Device: Windows PC
• Browser: N/A (Desktop app)
• OS: Windows

Screenshots

Figure: when MCP is not connected link to a new issue creation page is added on re-process attempt instead of a link to the created issue

Thanks!