{"version":"2.1.319","anchor":"connector-originated-messages-and-mcp-app-view-ids","canonical_anchor":"connector-originated-messages-and-mcp-app-view-ids","heading":"Messages can be marked as coming from a connector, and app views listed by widget id","tier":"internal","area":"Connectors","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/connector-originated-messages-and-mcp-app-view-ids","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Messages can be marked as coming from a connector, and app views listed by widget id\n\nUser messages can now be flagged as coming from a connector, and Claude's reminder about MCP App views now lists them by widget_id\n\n**What**\n\nTwo changes:\n\n- A user message can now carry a mark saying it came from a connector, and that mark is passed on when the turn is handled.\n\n- Claude gets a reminder listing MCP App views (app panels supplied through MCP) that share state. It now lists them by their `widget_id` and says \"none with a widget_id\" when there are none. Before, it listed them by a view id taken from the view.\n\n**Why**\n\nThis changes the text Claude sees about MCP App views, so it now refers to them by widget id.\n\n- Area: Connectors\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}