Use Discussions to file bugs, ideas, questions, and to share what you've built. Pick the matching category.
| What you have | Where to post it |
|---|---|
| A question about how to do something | Discussions → Q&A |
| A bug or unexpected behavior | Discussions → Bugs (use the Bug template) |
| A feature idea or improvement | Discussions → Ideas |
| A plugin, agent, skill, MCP tool, or use case you built | Discussions → Show and tell (and a PR if you want to land it) |
| A security vulnerability | MSRC — see SECURITY.md. Do not post in public Discussions. |
A great bug post makes the difference between "we need more info" and "shipping a fix." The Bug template prompts you for each of these:
-
Microsoft Discovery version. Either
Help → Aboutin the Microsoft Discovery app, or the file name of the installer you ran (DiscoveryExpressSetup-0.13.41.exe→ version0.13.41). -
OS version (
winver). -
What you were trying to do in one sentence.
-
Exact steps to reproduce. Numbered. Including any commands you typed in the
dxCLI or in Copilot Chat. -
What you expected vs what actually happened.
-
Logs.
- Open the Output panel in VS Code (
Ctrl+Shift+U) and select the Microsoft Discovery channel; copy the relevant tail. - Attach
.discovery/logs/files from your workspace if any are present.
- Open the Output panel in VS Code (
-
dx doctoroutput. From your workspace folder:dx doctor --workspace . -
Screenshots or a short screen recording, if the bug is visual.
Open a Discussion in the Ideas category. Use the structure the template suggests:
- Problem — what user pain are you solving? Be specific.
- Proposal — what you'd like to see. A sketch is fine; a full design is not required.
- Who benefits — what kinds of users get value from this.
- Alternatives considered — including "do nothing."
Ideas with clear problem statements get traction fastest.
Open a Discussion in Show and tell describing what you built and what it's for — workflows, prompts, notebooks, or anything you've put together on top of Microsoft Discovery.
If you'd like to land your work in the catalog, see CONTRIBUTING.md for the PR workflow and the per-content authoring guides.