microsoft / microsoft/amplifier

Draft message 'Send' button renders content in edit mode instead of sending

Open
#293 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Python
Stars
3.1k
Forks
261
Avg merge
3h 28m
Merged PRs (30d)
13

Description

Description

When Lume drafts a message (e.g. an iMessage) and presents it to the user with a Send button, clicking Send renders the draft content in an edit/code-block mode rather than actually sending the message or confirming it was sent.

Steps to Reproduce

  1. Ask Lume to draft a message to a contact (e.g. "draft a message to Natalee about X")
  2. Lume presents the draft with a Send button
  3. Click the Send button

Expected Behavior

The message is sent and a confirmation is shown (e.g. "Sent to Natalee via iMessage")

Actual Behavior

The draft content is displayed in what appears to be an edit/code-block rendering mode — the message is not sent, and no confirmation is given

Context

  • Surface: Amplifier CLI / Lume bundle
  • Message type: iMessage draft
  • Reported: 2026-05-13
  • The user had to send the message manually as a workaround

Impact

User confusion — unclear whether the message was sent or not. Forces manual workaround.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the Send-button flow in the Amplifier CLI and Lume bundle for drafted iMessages. Reproduce the issue using the listed steps and inspect where the draft is rendered after clicking Send. Done means the message is sent and a confirmation such as "Sent to Natalee via iMessage" is shown instead of edit/code-block content.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
cli
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.