Claude Duet's Messages Show Up as If You Typed Them, a Developer Says

On 8 November, a developer filed a GitHub feature request, anthropics/claude-code issue 108257, saying messages Claude Duet sends to a local Claude Code session are stored as ordinary user prompts, indistinguishable from messages typed by the user. The reporter observed it on Windows 11 in the Claude desktop app, running Claude Code 2.1.317.

The reporter quotes Duet's approval card: "Allowing sends this as your own message to that session." Per the issue, the message was sent after the user tapped "Allow once"; that approval is separate from how the receiving session labels the message. Per the report, the session got an ordinary user turn, and its transcript shows origin kind "human" with a textNotTyped flag, which the model never sees. The reporter says messages from other Claude Code sessions carry a sender and a wrapper, and that Duet's sends skip that path.

The issue asks for Duet's messages to carry their own origin, so the receiving session and the user can see where a message came from.

Key facts

• The issue is anthropics/claude-code issue 108257, filed November 8, 2026. The reporter observed it on Windows 11 in the Claude desktop app, running Claude Code 2.1.317.
• The reporter quotes Duet's approval card: "Allowing sends this as your own message to that session." Per the issue, the message was sent after the user tapped "Allow once"; that approval is separate from how the receiving session labels the message.
• Per the report, the session got an ordinary user turn, and its transcript shows origin kind "human" with a textNotTyped flag, which the model never sees.
• The reporter says messages from other Claude Code sessions carry a sender and a wrapper, and that Duet's sends skip that path.
• The issue asks for Duet sends to carry their own origin, so the receiving session and the user can see where the message came from.