github / github/copilot-cli

Extension canvas.open emits malformed opened event and does not reliably focus

Abierto
#4,112 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

area:plugins
Lenguaje dominante
Shell
Estrellas
11.2k
Forks
1.9k
Merge medio
14 h 16 min
PR fusionados (30 d)
6

Descripción

Problem

A user-scoped Copilot CLI extension can register and manually render a canvas, but calling the documented low-level session.rpc.canvas.open route on resume does not reliably make the canvas visible and emits a malformed event warning in the extension process.

Copilot CLI version: 1.0.71-0 on macOS arm64.

Reproduction

  1. Register a canvas through joinSession({ canvases: [...], requestCanvasRenderer: true }).
  2. After detecting a resumed session, resolve the canvas through session.rpc.canvas.list().
  3. Call session.rpc.canvas.open with the exact returned provider ID:
await session.rpc.canvas.open({
  extensionId: declared.extensionId,
  canvasId: declared.canvasId,
  instanceId: "stable-instance",
  input: { key: "example" },
});

A complete implementation and focused tests are available in the Session Briefing adapter and its test.

Actual behavior

  • The canvas.open promise resolves; the extension's bounded failure diagnostic does not run.
  • The extension process logs failed to deserialize session.canvas.opened payload.
  • The resumed CLI does not reliably show/focus the canvas.
  • The SDK rejects the event because the payload does not satisfy OpenCanvasInstance (provider identity, instance/canvas IDs, reopen, and availability).

Expected behavior

The returned/opened snapshot and session.canvas.opened event satisfy the bundled SDK schema, and reopening a stable instance visibly focuses the canvas.

Additional evidence

  • The same canvas renders successfully when opened through the host's open_canvas tool with the explicit provider ID.
  • Omitting extensionId and passing the exact ID returned by canvas.list() both produce the malformed-event warning.
  • The canvas ID is unique in the session.

A small diagnostic option to log or expose the rejected event shape would also make this class of failure much easier to debug without instrumenting the SDK.

Guía de contribución

Abrir la guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Línea de trabajo

Empieza por el adaptador Session Briefing y su adapter.test.mjs; después, sigue la ruta session.rpc.canvas.open y el manejo del evento session.canvas.opened. Compara el snapshot y el evento devueltos con el esquema OpenCanvasInstance incluido. Se considera terminado cuando el evento se deserializa correctamente y volver a abrir una instancia estable enfoca visiblemente el canvas.

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

Evaluación

Stack tecnológico
javascript
Área
api, cli
Tipo de issue
Error
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.