Connector stays checked in the dropdown but is never attached to the composer — tool never dispatches (fresh sessions, any machine)

Bug Reports
1

Summary

When I select a connector (MCP / NAS / custom), it stays checked (✓) in the Connectors dropdown, but it never appears as a chip in the composer — the input bar where I type. On send, the model behaves as if no connector is attached and the tool is never dispatched. A Comet browser session that was opened before the regression still dispatches the same connectors correctly, so this looks like a client-side desync between the dropdown selection state and the actual composer attachment, not a server outage.

Reproduction steps

  1. Open a fresh session (any machine).
  2. Open the Connectors dropdown.
  3. Select one or more connectors (e.g. an MCP / NAS connector).
  4. The connector stays checked (✓) in the dropdown, but no chip appears in the composer.
  5. Type a prompt that requires the connector.
  6. Send.
  7. The model responds as if no connector is attached — the tool is never called.

Environment

  • Occurs in fresh sessions across multiple machines.
  • Affects standard chats (with and without a Space).
  • A Comet browser session opened before the regression still dispatches the same connectors correctly.

What I ruled out

  • Not a network issue: proxy / DNS / TLS all verified.
  • Not a dangling / broken connector: reproduced with freshly re-added connectors.
  • Not specific to one connector: reproduced with multiple different connectors.
  • Not a service outage: status page is green, and pre-regression cached sessions still work.

Related reports

  • Mac app 26.24.0 (28) – all MCP tools broken and irrecoverable in Spaces (thread 5397) — team already confirmed.
  • Custom MCP connector fails with ‘did not return a client_secret’ (thread 5172).
  • Additional note: in my case this also affects chats without a Space, which the existing threads do not cover.

Request

Please investigate the desync between the dropdown selection state and the composer attachment so connectors are actually dispatched on send. Happy to provide a HAR capture or a screen recording (fresh session fails vs. pre-regression cached session works) on request.

2

I have been suffering this issue with attempts to use Linear and Github. Very frustrating that perplexity itself is unaware of the bug and unable to describe the workaround.

3

Hey @Viktor_Hadzhiyski, @ckeryakes! Could you please let us know if you are still facing issues with the connectors you mentioned, as the team has been working on it and this should be fixed. They should work properly when you @ tag them in your prompts.

4

still have the problem. need full restarter to be sure. will check an let you know. Do you need more explanation and screnshots, or you are fully aware what look like the problem?

5

I get this message when I try:
I don’t have the ability to create or modify issues/PRs directly in your Linear or GitHub from this chat, even with the connectors enabled; my access to those systems is read/assist, not write.perplexity+3

What I can do is:

  • Draft precise Linear tickets (titles, descriptions, acceptance criteria, labels, assignees) that you can paste into Linear.perplexity+1

  • Draft GitHub issues or PR descriptions tied to those tickets, so creation is a single copy‑paste step in your repo.perplexity+1

If you share which tickets you want (for example, “Watermarked animal photos V1” and how you want them split across BD/BL/Codex), I’ll write out:

  • Linear-ready issue text (including status, priority, and labels).

  • Matching GitHub issue/PR boilerplate for breederdesk or catgenes.

You can then create them in Linear/GitHub with minimal manual work.