New type property of prompt starters (bots.commandLists.commands) not respected by Teams/Copilot

[Benjiiim]

With manifest v1.27 released last month, we are now able to specify the type of prompt starters / commands: "basic" or "prompt.

From my understanding of the updated prompt starters doc, the title should now be used in the compose box when using "basic" and the "prompt" should now be used in the compose box when using "prompt".

For several years (when we were building good old bots with static commands), the title was always used in the composed box.
For several weeks or even months, Teams and Copilot started to use the description instead wich was sometime not the expected behavior and was causing issues.

Now, I'm expected Teams and Copilot to follow the instructions given in the manifest thanks to the type property, command per command (prompt starter per prompt starter), as documented.

However, it seems that Teams and Copilot are still using the description. Is that a know issue?

[m365-agent-toolkit-assistant]

👋 Hi Benjamin Talmard (@Benjiiim),

Thank you for reporting this issue! We want to let you know that:

⏱️ Our team will personally review your issue
🎯 You can expect a response within 1 business day

✨ This is an AI-generated initial response
🤖 AI-Generated Preliminary Analysis:

Classification: Upstream — the manifest behavior you describe is documented, so Teams/Copilot still inserting description instead of title/prompt points to a client/platform-side regression rather than a sample-repo issue.

• Microsoft Learn says for prompt starters: title is shown and populated into the compose box; for type: "prompt", the prompt value should appear instead of title/description.
• Your report matches a mismatch between documented manifest behavior and actual Teams/Copilot UX.
• I didn’t find a separate duplicate in the searched repos yet.

Upgrade check: No repo-side fix/changelog applies here; this appears outside OfficeDev/Microsoft-Teams-Samples.

What to do now:

1. Verify the app is redeployed after the manifest v1.27 change.
2. Capture client/build info (Teams desktop/web/mobile, Copilot surface, tenant ring).
3. Provide a minimal manifest snippet showing one basic and one prompt command.
4. Escalate as a Teams platform regression if reproducible across clients.

Useful links:

• No similar issues found in the searched repos.
• https://learn.microsoft.com/microsoftteams/platform/bots/how-to/conversations/prompt-suggestions

If you share client/build details, I can help draft a tighter repro.

---

Note: This is an automated first response generated by AI. A human team member will review your issue and provide a more detailed response soon. We appreciate your patience!

[Nivedipa-MSFT]

Hello Benjamin Talmard (@Benjiiim) - Did the suggestion above solve your issue?

[Benjiiim]

Hello Nivedipa-MSFT (@Nivedipa-MSFT) > no. I've tried to repro with a new app and the behavior is not consistent.

Example with the following commandLists array:

"commandLists": [
    {
        "scopes": [
            "copilot",
            "personal"
        ],
        "commands": [
            {
                "title": "Help",
                "description": "How can you help me?"
            },
            {
                "type": "basic",
                "title": "Basic command title",
                "description": "Basic command description"
            },
            {
                "type": "prompt",
                "title": "Prompt command title",
                "description": "Prompt command description",
                "prompt": "Prompt command prompt"
            }
        ]
    }
]

Current behaviour in Teams: description is used in the compose box for basic commands (with "type": "basic" or with no type defined as basic is the default).

Current behaviour in Copilot: description is always used in the compose box, regardless of the command type.

Expected behaviour: title should be used in the compose box for basic commands and prompt should be used in the compose box for prompt commands, as documented.

[Nivedipa-MSFT]

Hello Benjamin Talmard (@Benjiiim) - Manifest v1.27 introduced commands.type ("basic" inserts the title, and "prompt" inserts the description). The schema is already live, and atk validate accepts it, but the Teams and Copilot client renderers are still inserting the description for every case, no matter the type. This follows the same schema-first, client-later pattern we saw when prompt starters first replaced static command titles.
Keep type:"basic" set correctly — it's forward-compatible. Don't work around it by putting the title in the description field; that will quietly break once the renderer ships, because type:"prompt" entries will then insert that title-shaped description verbatim.

[Benjiiim]

Thanks Nivedipa-MSFT (@Nivedipa-MSFT)
Do you mean that I just need to wait for Teams & Copilot to implement this new capability?
Do you know how long it will take and if there is a public roadmap item to follow?