[Gen UI] Inline visualize cards always fail on SSH remote executors (desktop-attached-remote): "Gen UI file is outside the host output directory"
Mantenedores costumam responder em até 1 dia
Ninguém assumiu esta issue ainda.
Avaliação
- Dificuldade
- 4/5
- Tempo estimado
- 3-5 dias
- Facilidade para iniciantes
- 43/100
- Tipo de issue
- Bug
- Clareza
- Claramente especificada
- Status de atividade
- Ativa
- Stack de tecnologia
- javascript, node.js
Direção de pesquisa
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.
Escrita pelo modelo de indexação a partir do texto da issue.
Descrição
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.
- Linguagem predominante
- Python
- Estrelas
- 95
- Forks
- 57
- Métricas de merge de PRs
- Nenhum PR com merge em 30d
Preparar o ambiente
- Sem Dockerfile nem arquivo Docker Compose
- Tem um modelo de pull request
- Ler o guia de contribuição
Primeiros passos
- Leia a issue inteira e depois o guia de contribuição do projeto.
- Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
- Faça um fork do repositório e trabalhe em uma branch.
- Abra um pull request que referencie o número da issue.
Mais 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 triggerTalvez já em andamento @dvd233 assumiu há 19 dias. Aberta
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 85/100
zai-org/zcode-plugins#14 ·
Mantenedores costumam responder em até 1 dia
-
Dificuldade 4/5 3-5 dias Facilidade para iniciantes 44/100
zai-org/zcode-plugins#84 ·
Mantenedores costumam responder em até 1 dia
-
Dificuldade 3/5 1-2 dias Facilidade para iniciantes 45/100
zai-org/zcode-plugins#80 ·
Mantenedores costumam responder em até 1 dia
-
Dificuldade 5/5 Mais de uma semana Facilidade para iniciantes 25/100
zai-org/zcode-plugins#68 ·
Mantenedores costumam responder em até 1 dia
-
Dificuldade 4/5 3-5 dias Facilidade para iniciantes 49/100
zai-org/zcode-plugins#67 ·
Mantenedores costumam responder em até 1 dia
Todas as issues de zai-org/zcode-plugins
Issues semelhantes
-
enhancement from-review
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 78/100
khuisman/mcp-gee-sweet#1010 ·
Mantenedores costumam responder em até 1 dia
-
bug confirmed issue
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 72/100
open-webui/open-webui#32333 · 2 comentários ·
Mantenedores costumam responder em até 1 dia
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 68/100
ll7/robot_sf_ll7#10368 ·
Mantenedores costumam responder em até 1 dia
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 62/100
-
mcp: a write that loses its answer is reported as "cannot reach", although it may have landedAberta
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 68/100
flop-labs/technocore-chat#982 ·
Mantenedores costumam responder em até 1 dia