github / github/app

[Requests and ideas] Feature request: surface canvases in automation output.

Offen
#1,218 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
Feedback mood:happy os:macos Requests and ideas
Vorherrschende Sprache
Keine Sprachdaten
Sterne
2.1k
Forks
153
PR-Merge-Kennzahlen
Keine gemergten PRs in 30 T.

Beschreibung

**Mood:** 😊
**Category:** Requests and ideas

Feature request: surface canvases in automation output. I have automations that generate interactive HTML dashboards and call open\_canvas to display them. The automation runs, the HTML gets built, the open\_canvas call fires but when the automation finishes, I only see text. The canvas artifact exists if I go looking for it, but it's not part of the results view. It would be great if, when an automation has a canvas open at completion, that canvas showed up when I view the automation's output, similar to how canvases work in regular sessions. The artifacts are already being generated. Would love to see them without the extra step.

---
| Field | Value |
| --- | --- |
| App version | 1.0.1 |
| OS | macOS 26.5.1 |
| Theme | Noctis Azureus |
| Path | /chat |
| Tenure | Week 4 |

Beitragsleitfaden

Beitragsleitfaden öffnen

Rechercherichtung

Start by tracing the automation output and results view, then compare how an open_canvas artifact is surfaced in regular sessions. Done means a canvas that is open when an automation completes appears with the automation's output without requiring users to find the artifact separately.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
html
Bereich
desktop, frontend
Issue-Typ
Feature
Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Aktivitätsstatus
Ruhig
Klarheit
Größtenteils klar
Anfängerfreundlichkeit
48/100

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.