github / github/app

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

Abierto
#1,218 0 comentarios 0 reacciones 0 asignados Ver en GitHub
Feedback mood:happy os:macos Requests and ideas
Lenguaje dominante
Sin datos de lenguaje
Estrellas
2.1k
Forks
153
Métricas de merge de PR
Sin PR fusionados en 30 d

Descripción

**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 |

Guía de contribución

Abrir la guía de contribución

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Evaluación

Stack tecnológico
html
Área
desktop, frontend
Tipo de issue
Nueva funcionalidad
Dificultad
4/5
Tiempo estimado
3-5 días
Estado de actividad
Tranquilo
Claridad
Bastante claro
Aptitud para principiantes
48/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.