fix(aterm): warn when the bundles call an older aterm than the one writing them #1281

Merged

coilyco-ops merged 1 commit from aos/claude/rc44-bundle-version into main

2026-08-26 09:04:47 +00:00

coilyco-ops commented

2026-08-26 09:03:09 +00:00

Owner

Kai reported the .app names and PATH fixed but the window still small and unmaximized, and read it as kitty ignoring its options.

It was not kitty. Generation writes the wrapper, so names and PATH landed the moment she regenerated, while every window option comes from the installed binary the wrapper invokes. That binary is still aos-v0.231.0, which has no --start-as or --font-size at all. Both fixes shipped in the same commit, so the split between them looked like a kitty problem rather than a version one.

The fix

Nothing said so. Generation now reads the version of the aterm it bakes in and warns when it differs from its own, naming both:

warning    /opt/homebrew/bin/aterm (aos-v0.231.0), not this dev build

That is the line that would have answered this in one run instead of a bisect through kitty's config.

Verified on the real host

The warning reproduces the exact case against the actually-installed binary.
kitty does honor both options once a new enough aterm passes them. Worth recording for the next person who measures this: a window sampled at startup reports its pre-resize size, so the check needs a settle delay. With one, --start-as=maximized -o font_size=14.5 gives 49x168 against 23x71 for the default window; without one, both read 23x71 and maximized looks broken.
101 tests green, pre-commit run --all-files green.

Not a code problem

The release pipeline is healthy: the fixes are in aos-v0.242.0 and the tap formula upstream is already at 0.242.0. The Mac's local tap checkout is behind, which brew update resolves.

Kai reported the `.app` names and PATH fixed but the window still small and unmaximized, and read it as kitty ignoring its options. It was not kitty. Generation writes the wrapper, so names and `PATH` landed the moment she regenerated, while every window option comes from the installed binary the wrapper invokes. That binary is still `aos-v0.231.0`, which has no `--start-as` or `--font-size` at all. Both fixes shipped in the same commit, so the split between them looked like a kitty problem rather than a version one. ## The fix Nothing said so. Generation now reads the version of the `aterm` it bakes in and warns when it differs from its own, naming both: ``` warning /opt/homebrew/bin/aterm (aos-v0.231.0), not this dev build ``` That is the line that would have answered this in one run instead of a bisect through kitty's config. ## Verified on the real host - The warning reproduces the exact case against the actually-installed binary. - kitty does honor both options once a new enough `aterm` passes them. Worth recording for the next person who measures this: a window sampled at startup reports its pre-resize size, so the check needs a settle delay. With one, `--start-as=maximized -o font_size=14.5` gives 49x168 against 23x71 for the default window; without one, both read 23x71 and maximized looks broken. - 101 tests green, `pre-commit run --all-files` green. ## Not a code problem The release pipeline is healthy: the fixes are in `aos-v0.242.0` and the tap formula upstream is already at 0.242.0. The Mac's local tap checkout is behind, which `brew update` resolves.

coilyco-ops added 1 commit

2026-08-26 09:03:09 +00:00

fix(aterm): warn when the bundles call an older aterm than the one writing them

ci / aos-eval-tests (pull_request) Successful in 7s

Details

ci / ward-doctor (pull_request) Successful in 7s

Details

ci / aos-cli-tests (pull_request) Successful in 28s

Details

ci / gate (pull_request) Successful in 49s

Details

12f8d4b0de

Kai reported the .app names and PATH fixed but the window still small
and unmaximized. Both halves shipped together, so the split looked like
kitty ignoring its options. It was not kitty: generation writes the
wrapper, so names and PATH landed at once, while every window option
comes from the installed binary the wrapper invokes, which was still
aos-v0.231.0 and has no --start-as or --font-size at all.

Nothing said so. Generation now reads the version of the aterm it bakes
in and warns when it differs from its own, naming both, which is the
line that would have answered this in one run instead of a bisect
through kitty's config.

Verified against the real host: the warning reproduces the exact case,
and kitty does honor both options once a new enough aterm passes them.
A window measured at startup reports the pre-resize size, so the check
needs a settle delay: 49x168 maximized against 23x71 default.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Co-authored-by: Kai Siren <coilysiren@gmail.com>
Co-authored-by: Claude <noreply@anthropic.com>
Agent-Role: platform

coilyco-ops merged commit 52fa695f92 into main

2026-08-26 09:04:47 +00:00

coilyco-ops referenced this pull request from a commit

2026-08-26 09:04:49 +00:00

fix(aterm): warn when the bundles call an older aterm than the one writing them (#1281)

No reviewers

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

coilyco-flight-deck/agentic-os!1281

No description provided.

Rows
Columns