One of the more frustrating things lately has been the inconsistent way in wh...

One of the more frustrating things lately has been the inconsistent way in which sessions are able (or not able) to leverage some of the harness' own tools. Specifically, having copilot create a markdown file for me to review, and then often, but not always, being unable to open that file using its own excellent markdown editor. It also seems incapable (sometimes) of creating a clickable link to some of those same sorts of assets for me to manually open, and will more often than not show me a relative path to the file, which would then require me to go searching down half-hidden worktree folder structures to get to the file. Pretty terrible experience for this particular slice of functionality when it seems to have all the pieces necessary for this to be an excellent experience. You have one of the very best WYSIWYG markdown editors I've seen!

---
| Field | Value |
| --- | --- |
| App version | 1.1.12 |
| OS | Windows 10.0.26100 |
| Theme | GitHub |
| Path | /chat |
| Tenure | Week 7 |

Start in the /chat experience on Windows and reproduce the reported behavior with Copilot-created markdown files: opening them in the markdown editor, creating clickable links, and displaying their paths. No source files or tests are named; done means reliably opening these assets or providing usable links without requiring manual worktree navigation.

Written by the indexing model from the issue text.