Skip to content

feat: 1.0.0 - zypi starts zycode-agent, --setup, standalone bundles, Linux aarch64 TUI - #130

Merged
zy1233 merged 7 commits into
mainfrom
feat/omarchy-and-1.0.0
Nov 16, 2026
Merged

zy1233 merged 7 commits into
mainfrom
feat/omarchy-and-1.0.0

Conversation

@zy1233

@zy1233 zy1233 commented Nov 16, 2026 •

Copy link
Copy Markdown
Owner

Summary

zypi starts zycode-agent and has --setup. Each tag gets standalone bundles (zypi and zycode-agent in one archive) for Linux x86_64, Linux aarch64 and macOS arm64. All seven Python packages and the TUI go to 1.0.0. The #131 changes (usage_update, the max thinking level, auto_compact, the stop reason max_turn_requests) ship in the same release.

zypi finds the agent
  PI_AGENT_COMMAND
  [agent].command          (agent.toml, then config.toml)
  PI_PYTHON                only when set and not empty: python -m pi_agent_cli
  zycode-agent             next to zypi (a symlink is followed), then PATH   <- no python fallback any more

Release (tag v1.0.0)                         Agent binaries (runs after Release)
  build                  wheels, sdists        5 agent archives
  build-tui              zypi-linux-x86_64        |
  build-tui-linux-arm    zypi-linux-aarch64 NEW   +-> zycode-<target>-1.0.0.tar.gz NEW
  build-tui-macos-arm    zypi-macos-arm64             (linux-x86_64, linux-aarch64, darwin-aarch64;
  publish-pypi, github-release                         the step fails when one of the three is missing)

Changes after review

A review of this PR found two high and several medium and low problems. All are fixed on this branch:

 web/ README / TUI guide (install)
-  pip install pi-agent-cli-lc ; download a standalone zypi ; run zypi      (zypi finds no zycode-agent)
+  download releases/download/v1.0.0/zycode-linux-x86_64-1.0.0.tar.gz        (tag-pinned: still works after 1.0.1)
+  "zypi alone": export PI_PYTHON=python3 (or PI_AGENT_COMMAND), with a note in the text

 CHANGELOG.md
-  "## [0.9.1]" heading gone, the 0.9.1 text sits under 1.0.0
+  0.9.1 restored, 1.0.0 has its own Known issues; the "no Python fallback" item is a Behaviour change under Changed
+  the text about classifiers is correct now (three packages have Production/Stable, the four extensions have none)

 .github/workflows/agent-binaries.yml
-  2>/dev/null || true ; if [ -f ... ]      (a missing bundle is skipped, the job stays green)
+  every missing input is an ::error:: and exit 1 ; the three bundle names are checked in the release after the upload
+  a tag whose build.py has no --bundle-from-archive still gets its agent archives (repair of old tags)

 packaging/agent/build.py
-  dead "if src is not None" (extractfile() returning None failed first, with a TypeError)
+  only a regular file named zycode-agent or zycode-agent.exe is taken from the archive

 test_packaging_bundle.py
-  input archive built by hand
+  input archive from the real pack(); 8 tests

 web/ hero badge ("In beta") and docs: stale default text for the agent lookup (DESIGN, WINDOWS, NOTICE, TUI user guide)
+  1.0.0 stable; the lookup order above

The omarchy patch in docs/specs/2026-11-15-omarchy-agent-pr.md is a draft. Its status line names two defects that are not fixed here (see Known issues in the CHANGELOG). It is not part of this release.

Evidence

  • Windows: pytest 6238 passed, 107 skipped. Linux (WSL, clean venv from git archive): 6303 passed, 42 skipped.
  • Ruff: check and format --check pass with 0.16.0 (the pin of release.yml) and 0.17.5.
  • Web: npm run check and npm run build pass. The built pages name the tag-pinned URL and no longer say "beta".
  • Publish step of agent-binaries.yml, run in WSL with a stand-in gh, 5 cases: all three bundles; a missing zypi-* asset; a missing agent archive; an old tag whose build.py has no --bundle-from-archive; build.py that makes no file. The first and the fourth pass, the other three stop with ::error::.
  • Release dry run (workflow_dispatch on this branch, run 43841723521): all jobs passed: Pre-release tests, Build Python packages, and the three TUI builds (Linux x86_64, Linux aarch64 - the first run of the new job - and macOS arm64). Publish to PyPI and GitHub Release were skipped, as a dry run does.
  • Wheels of the dry run: the seven 1.0.0 wheels install in a clean venv, uv pip check is clean, all seven import. pi-agent-cli-lc has the console scripts pi-agent-cli and pi-agent-cli-lc (no zycode-agent, as the docs say).

Not verified: zypi for Linux aarch64 and macOS arm64 was built by CI but nobody ran it by hand; max was not sent to a real provider; the max item of the VS Code menu was not tried in a real window.

Merge Danger

Door: one-way

Merge to main deploys zycode.dev at once (web/ changes). The README and the site name the v1.0.0 bundles, and these files exist only after the Release workflow and then Agent binaries have run on the tag. Tag v1.0.0 right after the merge. The tag publishes the seven packages to PyPI, and PyPI never takes a version back.

Blast Radius: release

…the known issues to 1.0.0

The merge of the 1.0.0 branch had dropped the heading of 0.9.1, so the release notes of v1.0.0 (cut by awk from one heading to the next) would have held the text of 0.9.1.

Also: the 1.0.0 section now lists usage_update, the max thinking level, auto_compact and max_turn_requests (all from #131), moves the removal of the Python fallback of zypi to Changed as a behaviour change with the one-line fix, says what the Omarchy item really is (a draft with two known defects), and has its own Known issues. Date 2026-11-16.
…, show 1.0.0 as stable

zypi no longer starts python -m pi_agent_cli when nothing is set, and the pip package has no zycode-agent command. The install steps on the web site (en and zh), in the README and in the TUI guide still told a user to pip install the agent and download a bare zypi, which fails at the first start. They now use the bundle (zypi and zycode-agent in one archive), and say how to use the pip package (PI_PYTHON).

The bundle URLs name the tag (releases/download/v1.0.0/...) and not latest: the file name holds the version, so latest would give a 404 after the next release. The version for the web text is one constant in web/src/data/site.ts.

The hero badge and the terminal tag said beta while the page says 1.0.0 is stable and the README table says Stable. The docs that still described the old default (DESIGN, WINDOWS, the pager user guide, tui/NOTICE) say zycode-agent now. The Omarchy design record is marked as a draft with its two known defects.
…ndling with real archives

The publish step of Agent binaries ignored a failed download (|| true) and skipped a target whose input was missing, so a release could go out with a green run and no bundle, while the README and the web page link to the bundles. It now fails for a missing zypi file, a missing agent archive or a bundle that is not made, attaches the agent archives first (the VS Code extension needs them), and checks that the release holds the three bundles at the end. A tag from before the bundles (its build.py has no --bundle-from-archive) still gets its agent archives and no bundle, so the repair path of old tags works. Checked in WSL with a stand-in gh for five cases (all there, no zypi file, no agent archive, old build.py, an upload that loses a bundle).

build.py: the check for src is None could not run, because with None raises first (TypeError). Only a regular file counts as the program now, and a directory of that name gives the clear FileNotFoundError.

The tests now go through the real pack(), cover the zip archive, the two error cases and the command line that the workflow runs.
…fier

The 1.0.0 entry said that all seven Python packages get Development Status :: 5 - Production/Stable. Only three have that classifier (pi-agent-core-lc, pi-agent-harness-lc, pi-agent-cli-lc). The four extension packages never had a Development Status classifier. Found when the seven wheels of the Release dry run were installed in a clean venv.
@zy1233 zy1233 changed the title feat: promote to 1.0.0 Stable, add zypi --setup and Omarchy Linux integration feat: 1.0.0 - zypi starts zycode-agent, --setup, standalone bundles, Linux aarch64 TUI Nov 16, 2026
@zy1233
zy1233 merged commit 037b162 into main Nov 16, 2026
18 checks passed
@zy1233
zy1233 deleted the feat/omarchy-and-1.0.0 branch November 16, 2026 10:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant