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 |

Beginne in der /chat-Erfahrung unter Windows und reproduziere das gemeldete Verhalten mit von Copilot erstellten Markdown-Dateien: Öffne sie im Markdown-Editor, erstelle anklickbare Links und zeige ihre Pfade an. Es werden keine Quelldateien oder Tests genannt; als erledigt gilt die Aufgabe, wenn diese Dateien zuverlässig geöffnet werden können oder nutzbare Links bereitgestellt werden, ohne eine manuelle Navigation im Worktree zu erfordern.

Vom Indexierungsmodell aus dem Issue-Text verfasst.