Publish agent-terminal in native AOS artifacts #734

Closed
opened 2026-07-24 22:01:34 +00:00 by coilyco-ops · 2 comments
Owner

Outcome

Publish the AOS-owned agent-terminal launcher from agentic-os#730 as a versioned native artifact that infrastructure can install without a source checkout.

Scope

  • Include agent-terminal in the existing native AOS release and packaging surfaces for Windows and macOS.
  • Keep the launcher version aligned with the agentic-os release that defines its renderer contract.
  • Install the binary on PATH beside the other AOS-owned native tools.
  • Preserve the renderer boundary. Agent-compose supplies agent-compose.overlay.v1, while agent-terminal translates it into Alacritty arguments.
  • Add artifact-level smoke coverage using --dry-run with a fixture or installed agent-compose binary.
  • Document installation, upgrade, rollback, and version reporting.

Acceptance

  • Versioned Windows and macOS artifacts contain a runnable agent-terminal binary.
  • A clean native installation can run agent-terminal --help and a representative --dry-run without an agentic-os checkout.
  • Packaging contains no host-specific paths or fleet configuration.
  • Release validation and repository pre-commit pass.

Boundary

Infrastructure owns installation and host convergence after this artifact exists. Removing retired Warp launch machinery remains agentic-os#727.

## Outcome Publish the AOS-owned `agent-terminal` launcher from agentic-os#730 as a versioned native artifact that infrastructure can install without a source checkout. ## Scope * Include `agent-terminal` in the existing native AOS release and packaging surfaces for Windows and macOS. * Keep the launcher version aligned with the agentic-os release that defines its renderer contract. * Install the binary on `PATH` beside the other AOS-owned native tools. * Preserve the renderer boundary. Agent-compose supplies `agent-compose.overlay.v1`, while `agent-terminal` translates it into Alacritty arguments. * Add artifact-level smoke coverage using `--dry-run` with a fixture or installed agent-compose binary. * Document installation, upgrade, rollback, and version reporting. ## Acceptance * Versioned Windows and macOS artifacts contain a runnable `agent-terminal` binary. * A clean native installation can run `agent-terminal --help` and a representative `--dry-run` without an agentic-os checkout. * Packaging contains no host-specific paths or fleet configuration. * Release validation and repository pre-commit pass. ## Boundary Infrastructure owns installation and host convergence after this artifact exists. Removing retired Warp launch machinery remains agentic-os#727.
Author
Owner

WARD-WORKFLOW: done

details

Review: intentionally skipped. Implementation and QA are role-separated. QA is a separate, opt-in exact-commit verification role bound to candidate c20f67d3ccd8a77530078098f14c74e28307ce1c.

workflow: merge-remote-main; review summary: intentionally skipped for separate exact-commit QA

Felt: clean extension of the existing native release path.
Confidence: high. Cross-build, packaging, artifact smoke, 608 tests, and full pre-commit passed.
Surprises: documentation caps called for one focused native guide.
Follow-ups: infrastructure owns installation and convergence. Exact-commit QA remains opt-in.

Codex

WARD-WORKFLOW: done ✅ <details><summary>details</summary> Review: intentionally skipped. Implementation and QA are role-separated. QA is a separate, opt-in exact-commit verification role bound to candidate `c20f67d3ccd8a77530078098f14c74e28307ce1c`. workflow: merge-remote-main; review summary: intentionally skipped for separate exact-commit QA Felt: clean extension of the existing native release path. Confidence: high. Cross-build, packaging, artifact smoke, 608 tests, and full pre-commit passed. Surprises: documentation caps called for one focused native guide. Follow-ups: infrastructure owns installation and convergence. Exact-commit QA remains opt-in. Codex </details>
Author
Owner

WARD-WORKFLOW: reservation-released

release details

Run finished with WARD-WORKFLOW: done ✅.

ward container reap released container engineer-codex-agentic-os-734 (--harness codex): the terminal outcome supersedes the reservation, so a later redispatch no longer needs --override-reservation.

— Codex, via ward agent

<!-- ward-agent-reservation-released --> WARD-WORKFLOW: reservation-released <details><summary>release details</summary> Run finished with `WARD-WORKFLOW: done ✅`. `ward container reap` released container `engineer-codex-agentic-os-734` (`--harness codex`): the terminal outcome supersedes the reservation, so a later redispatch no longer needs `--override-reservation`. </details> <!-- ward-agent-signature --> — Codex, via `ward agent`
Sign in to join this conversation.
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#734
No description provided.