[BUG] Cowork — Atlassian connector throws spurious error toasts on successful Jira writes

Resolved 💬 1 comment Opened May 8, 2026 by jleertou Closed Jun 5, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

In Cowork mode, every successful Jira write via the Atlassian connector produces these error toasts in the chat UI:

  • "Unable to reach Atlassian Rovo"
  • "MCP error -32601: Method not found"

The underlying Jira API call succeeds (the issue is updated correctly), but the toasts pop up on every tool call. Looks like the Atlassian MCP integration is making a companion call to Rovo that either doesn't exist or isn't implemented on the server side. The toast obscures the chat and makes successful operations look like failures.

Repro: in Cowork, use the built-in Atlassian connector to call any Jira write tool (e.g. editJiraIssue) — the toast appears every time despite the call succeeding.

Cowork build: [whichever version you're on — there's usually a version number in Settings or About]

Screenshots attached.

What Should Happen?

seemed like it worked but spams the chat with errors

<img width="379" height="151" alt="Image" src="https://github.com/user-attachments/assets/2f1239d4-15e4-495f-8da6-aeb0d118bf20" />
<img width="785" height="568" alt="Image" src="https://github.com/user-attachments/assets/6e2cc613-494d-4b7b-8504-5326827c9d20" />

Error Messages/Logs

Steps to Reproduce

existing story in jira with subtasks, subtasks are beeing updated and seems to work but screen gets spammed with errors, that should not happen

Claude Model

Opus

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

Claude 1.6608.0 (f65729) 2026-05-07T14:16:09.000Z

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗