[Gen UI] Inline visualize cards always fail on SSH remote executors (desktop-attached-remote): "Gen UI file is outside the host output directory"
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 43/100
- Tipo de issue
- Error
- Claridad
- Bien especificado
- Estado de actividad
- Activo
- Stack tecnológico
- javascript, node.js
Línea de trabajo
Start with packages/services/src/gen-ui/adapters/files.ts and the readGenUiDocument path described in the report, then read docs/architecture/r2-server-cli-and-daemon.md to confirm executor ownership. Trace how desktop-attached remote reads reach the executor and compare that with the local validation path. Done when the remote executor validates the file against its output root and returns its HTML for the client card to render.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Note: filed here because github.com/zai-org/ZCode has issues disabled; this repo already hosts main-repo bug reports (see #64, #60). Happy to repost if the team prefers another channel.
Environment
- ZCode Desktop client 3.15.1 (Windows 11), latest
- Remote executor over SSH: Ubuntu 24.04 (root), zcode-server 3.15.1 (matched), service authority mode
desktop-attached-remote - Executor env:
ZCODE_GEN_UI_OUTPUT_ROOT=/root/.zcode/v2/visualizations
Steps to reproduce
- Connect Desktop to an SSH remote executor (WSL2 Ubuntu) as a remote workspace
- Ask the agent to emit any
::visualizefragment; the executor writes it into the host-injected session dir, e.g./root/.zcode/v2/visualizations/<sha256(workspace-identity,session-id)>/view.html - Client renders the Gen UI card
Actual behavior
Card fails to load: Gen UI file is outside the host output directory(客户端提示“无法加载交互视图”)。100% reproducible across multiple files; “重试” never helps.
Executor-side checks (all pass)
- File is inside
ZCODE_GEN_UI_OUTPUT_ROOT; directory name = sha256 of[workspace-identity, session-id], exactly as injected by the host - Permissions 644, no symlinks on the whole path (verified with
namei), valid HTML fragment, well under 5 MB - The error string exists in
zcode-server.cjs(readGenUiDocument), but at read time the failing validation cannot be the executor's own — the file is under the executor root, so therelative()check would pass there
Root-cause analysis (from the client bundle + repo source)
- The Desktop client bundle (app.asar 3.15.1) embeds the same reader —
readGenUiDocument(minifiedbL) ofpackages/services/src/gen-ui/adapters/files.ts:let r = resolve(t), // t = outputRoot, resolved on the LOCAL client machine o = normalize(n.path), // n.path = remote executor's absolute POSIX path, e.g. /root/.zcode/v2/... s = relative(r, o); if (!s || s === ".." || s.startsWith(`..${sep}`) || isAbsolute(s)) throw new Error("Gen UI file is outside the host output directory");relative()between a Windows local output root and the remote absolute path can never pass, so the client throws before any remote access happens. packages/services/src/gen-ui/adapters/files.ts(current main) states the intended design in a comment: “读取范围只由执行端 Host 的固定输出根目录决定” — the read scope is owned by the executor-side Host.docs/architecture/r2-server-cli-and-daemon.mdplaces the same ownership on the executor.- Conclusion: in
desktop-attached-remotemode the Gen UI document read/validation is not dispatched to the remote host; the client performs a local-filesystem read with a local output root instead.
Expected behavior
In desktop-attached-remote mode, route the Gen UI document read/validation through the remote transport: the executor validates against its own ZCODE_GEN_UI_OUTPUT_ROOT and returns the HTML content to the client for rendering.
Impact / current workaround
Only inline interactive Gen UI cards are affected; all other remote functionality works fine. Current workaround: executor delivers Playwright PNG screenshots plus standalone HTML files instead of ::visualize cards.
Notes
- No user-facing configuration found that redirects the client-side validation root (
ZCODE_GEN_UI_OUTPUT_ROOTonly configures the executor side). - Happy to provide full connection logs or a minimal repro if useful.
- Lenguaje dominante
- Python
- Estrellas
- 95
- Forks
- 57
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de zai-org/zcode-plugins
-
video-agent-kit (0.4.3): hooks invoke python3, which doesn't exist on Windows — SessionStart/UserPromptSubmit/Stop hooks fail on every triggerPosiblemente ocupada @dvd233 la tomó hace 20 días. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 85/100
zai-org/zcode-plugins#14 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 4/5 3-5 días Aptitud para principiantes 35/100
zai-org/zcode-plugins#88 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 5/5 Más de una semana Aptitud para principiantes 25/100
zai-org/zcode-plugins#86 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 4/5 3-5 días Aptitud para principiantes 44/100
zai-org/zcode-plugins#84 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 3/5 1-2 días Aptitud para principiantes 45/100
zai-org/zcode-plugins#80 ·
Los mantenedores suelen responder en 1 día
Todos los issues de zai-org/zcode-plugins
Issues similares
-
Atomic append fails to create a missing filePosiblemente ocupada @harbinresearcher la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
fabiocaccamo/python-fsutil#201 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
Los mantenedores suelen responder en 1 día
-
task
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
danparshall/claude_researcher#87 ·
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
GhostManager/Ghostwriter#998 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 85/100
datajoint/datajoint-python#1586 ·
Los mantenedores suelen responder en 1 día