Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

agx: empty output on HTML-generation charges (already fixed in wrapper)

未关闭
  • 哪里不对？
#152 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
1/5
预计耗时
1 小时以内
新手友好度
15/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
停滞
技术栈
shell
领域
cli, tooling

调研方向

从 ~/AI/Tools/agx 的入口点开始，并将其与实际用于 dispatch agy 的路径进行比较。检查第 96-104 行的空输出保护，以及第 108-116 行的 AGX_OUT 工件保护，然后重新运行 Sea of Demand charge。完成的标准是 active path 以 1 退出并给出诊断信息，而不是在输出为空时报告成功。

由索引模型根据 Issue 内容生成。

描述

Summary

agx (Antigravity wrapper) returns 0 bytes with exit 0 on charges that ask it to produce HTML/files. The caller only discovers the failure by checking output size.

Environment

  • LazyCodex: 4.15.1 (this harness)
  • agx wrapper: ~/AI/Tools/agx (current)
  • Reproduction: 2026-08-04 FleetOpus Sea of Demand visualization charge (5.4KB prompt → self-contained HTML dashboard)
  • Prior occurrences: sprite-factory (2026-07-25), portfolio roadmap (2026-07-28)

Repository Decision

  • Target: code-yeongyu/lazycodex
  • Why: The agx wrapper lives in the operator's ~/AI/Tools/ fleet dispatch layer, which is a LazyCodex-orchestrated harness integration. The defect (silent empty output) was in the wrapper, not upstream Codex or Antigravity core.

Reproduction

  1. Dispatch via agx (or a stale path to agx) with a prompt that says "output HTML" or "write a file"
  2. agy runs in headless mode (no --sandbox or denied writes)
  3. Model attempts write → denied silently → returns nothing
  4. Wrapper previously exited 0 with empty stdout

Expected Behavior

Wrapper detects empty output or no written artifact and exits 1 with a clear diagnostic.

Actual Behavior (historical)

Wrapper exited 0, 0 bytes stdout, 0 bytes stderr. Caller treated it as success.

Evidence

  • agx source at ~/AI/Tools/agx (137 lines) already contains the guard:
    • Lines 96-104: if [ "$STATUS" -eq 0 ] && [ -z "$RESULT" ] → echo "agx: agy exited 0 but produced NO output — refusing to report success" >&2; exit 1
    • Lines 108-116: AGX_OUT snapshot-diff guard → exit 1 if no new artifacts written
  • Comments in the wrapper cite the exact prior failures (2026-07-25, 2026-07-29) and the design rationale for the artifact guard.
  • The guard was added after the 2026-07-25/07-28 incidents; the 2026-08-04 reproduction suggests the caller used a stale agx path or invoked agy directly.

Root Cause

The wrapper lacked an empty-output + AGX_OUT guard. When agy (headless) silently denied a write, the wrapper reported success on nothing. The guard now exists.

Proposed Fix

Already implemented. The current agx wrapper (Option 1 + Option 3 from the report) does exactly what the recommendation asked for:

  • Detects empty stdout + exit 0 → exit 1 with message
  • In AGX_OUT mode, diffs the output directory and refuses on empty diff
  • Documents the "print to stdout, not write a file" discipline in the artifact-mode contract (lines 81-87)

Action for caller: ensure ~/AI/Tools/agx (or the current agx in PATH) is the one being dispatched. If a different code path calls agy directly, route it through agx or replicate the guard.

Verification Plan

  • Re-run the Sea of Demand charge using the current agx wrapper with AGX_OUT set → should now exit 1 with the diagnostic instead of 0 + empty file.
  • Confirm that any future charge that forgets the "print to stdout" discipline is caught by the wrapper guard.

This issue or PR was generated by LazyCodex.
Tag: lazycodex-generated

主要语言
TypeScript
星标
3.8k
派生
246
30 天内没有已合并 PR

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

code-yeongyu/lazycodex 的其他 Issue

查看 code-yeongyu/lazycodex 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。