[Requests and ideas] Feature request: surface canvases in automation output.
- Langage dominant
- Aucune donnée de langage
- Étoiles
- 2.1k
- Forks
- 153
- Métriques de merge des PR
- Aucune PR mergée en 30 j
Description
**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 |
Guide de contribution
Ouvrir le guide de contribution
Piste de recherche
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.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- html
- Domaine
- desktop, frontend
- Type d'issue
- Fonctionnalité
- Difficulté
- 4/5
- Temps estimé
- 3-5 jours
- Activité
- Calme
- Clarté
- Plutôt claire
- Accessibilité débutants
- 48/100