[BUG] Claude Code Rovo Connector not working

Status Open
Reported on v2.1.251
Maintainer reply None cached
Activity 0 comments · opened Sep 2, 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?

Still stuck on enabledInChat: false on my side, even though the UI clearly shows the toggle on for this chat. That mismatch means the toggle isn't taking effect for this particular session — most likely because this is a long-running scheduled/routine session that was already provisioned before the toggle flipped, and the connector attach only happens at session start.

That's outside what I can fix from in here. The practical next step: end/re-fire this scheduled routine so it launches a brand-new session — a new session should pick up the connector now that it's enabled. If it's still not available after a fresh session starts, that would point to something on the platform side (e.g., the connector needing to be re-saved on the schedule/routine configuration itself, not just the chat toggle), and worth flagging to support.

See photo:

<img width="852" height="636" alt="Image" src="https://github.com/user-attachments/assets/2d3bf2f7-187a-4f9d-b8f0-877446cbee71" />

What Should Happen?

The chat routine should have MCP access to Atlassian Rovo connector.

Error Messages/Logs

Steps to Reproduce

  1. Create a routine
  2. Add Atlassian Rovo Connector
  3. Enable the connector in your routine
  4. Attempt to execute routine
  5. See error enabledInChat: false, Connector in UI is enabled but the chat does not have the ability to use it

Claude Model

Sonnet (default)

Is this a regression?

No, this never worked

Last Working Version

_No response_

Claude Code Version

2.1.251

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Other

Additional Information

_No response_

View original on GitHub ↗