Add agent-compose branded Alacritty director launcher #730

Closed
opened 2026-07-24 21:26:13 +00:00 by coilyco-ops · 2 comments
Owner

Outcome

Add the first cross-platform branded director terminal surface in agentic-os using Alacritty and the existing renderer-neutral agent-compose overlay contract.

The first slice launches one warded director per OS window. Agent-compose supplies identity data, agentic-os translates it into static Alacritty branding, and Ward remains terminal-agnostic.

Contract

  • Agent-compose remains renderer-neutral. The launcher consumes agent-compose overlay --json and introduces no Alacritty concepts into agent-compose.
  • Agentic-os owns the Alacritty configuration and the thin agent-terminal launcher.
  • Ward remains the child command and owns execution authority.
  • The launcher accepts role, seat, expression, working directory, and a human-readable task title, then executes a caller-supplied command.
  • Branding uses the canonical derived favorite color for cursor, selection, and a subtle opaque background tint.
  • The launcher sets a stable window title from canonical identity plus the task title.
  • The launcher does not remap the ANSI palette, inject control sequences into captured command output, or add an interactive TUI loop.
  • Noninteractive inspection exposes the resolved identity and Alacritty arguments without opening a window.

Acceptance criteria

  • Windows and macOS launch shapes are covered without host-absolute paths.
  • The launcher validates the agent-compose overlay schema and fails with actionable errors for missing binaries, malformed JSON, unknown identity, or an empty child command.
  • Color derivation is deterministic and preserves readable contrast.
  • Tests cover overlay parsing, title construction, color derivation, argument construction, and failure paths.
  • Documentation explains ownership boundaries and the static first-slice limitation.
  • docs/FEATURES.md records the new branded terminal capability.
  • The repository declares Ward verbs for focused and full validation.
  • ward exec test passes.
  • ward exec pre-commit-all passes.

Non-goals

  • Live expression updates after launch.
  • Tabs, panes, session management, or a terminal multiplexer.
  • Avatars, background images, or a full interactive TUI.
  • Fleet installation or default-terminal rollout. Infrastructure owns that follow-up.
  • Removing the retired Warp launcher machinery tracked by #727.
## Outcome Add the first cross-platform branded director terminal surface in agentic-os using Alacritty and the existing renderer-neutral agent-compose overlay contract. The first slice launches one warded director per OS window. Agent-compose supplies identity data, agentic-os translates it into static Alacritty branding, and Ward remains terminal-agnostic. ## Contract * Agent-compose remains renderer-neutral. The launcher consumes `agent-compose overlay --json` and introduces no Alacritty concepts into agent-compose. * Agentic-os owns the Alacritty configuration and the thin `agent-terminal` launcher. * Ward remains the child command and owns execution authority. * The launcher accepts role, seat, expression, working directory, and a human-readable task title, then executes a caller-supplied command. * Branding uses the canonical derived favorite color for cursor, selection, and a subtle opaque background tint. * The launcher sets a stable window title from canonical identity plus the task title. * The launcher does not remap the ANSI palette, inject control sequences into captured command output, or add an interactive TUI loop. * Noninteractive inspection exposes the resolved identity and Alacritty arguments without opening a window. ## Acceptance criteria * Windows and macOS launch shapes are covered without host-absolute paths. * The launcher validates the agent-compose overlay schema and fails with actionable errors for missing binaries, malformed JSON, unknown identity, or an empty child command. * Color derivation is deterministic and preserves readable contrast. * Tests cover overlay parsing, title construction, color derivation, argument construction, and failure paths. * Documentation explains ownership boundaries and the static first-slice limitation. * `docs/FEATURES.md` records the new branded terminal capability. * The repository declares Ward verbs for focused and full validation. * `ward exec test` passes. * `ward exec pre-commit-all` passes. ## Non-goals * Live expression updates after launch. * Tabs, panes, session management, or a terminal multiplexer. * Avatars, background images, or a full interactive TUI. * Fleet installation or default-terminal rollout. Infrastructure owns that follow-up. * Removing the retired Warp launcher machinery tracked by #727.
Author
Owner

Landed on canonical main in commit 1529af7.

Validation:

  • ward exec agent-terminal-test, agent-terminal-build, and agent-terminal-lint pass.
  • A real agent-compose overlay --json dry run resolves the director identity and deterministic Alacritty launch arguments.
  • All repository hooks pass except two native-Windows host limitations: forgejo-runner-validate cannot bootstrap its Go environment because pre-commit cleanup returns WinError 145, and ShellCheck sees carriage returns in the unchanged tooling-image-zoom script.
  • The full Python suite reports 525 passed and 16 existing native-Windows shell, symlink, and file-URL failures outside agent-terminal.
  • Alacritty is not installed on this engineer host, so a live window launch remains part of fleet rollout.
Landed on canonical `main` in commit `1529af7`. Validation: * `ward exec agent-terminal-test`, `agent-terminal-build`, and `agent-terminal-lint` pass. * A real `agent-compose overlay --json` dry run resolves the director identity and deterministic Alacritty launch arguments. * All repository hooks pass except two native-Windows host limitations: `forgejo-runner-validate` cannot bootstrap its Go environment because pre-commit cleanup returns `WinError 145`, and ShellCheck sees carriage returns in the unchanged `tooling-image-zoom` script. * The full Python suite reports 525 passed and 16 existing native-Windows shell, symlink, and file-URL failures outside `agent-terminal`. * Alacritty is not installed on this engineer host, so a live window launch remains part of fleet rollout.
Author
Owner

Follow-up landed on canonical main in commit ec3b0d6: AOS now tracks alacritty/alacritty.toml as the portable Sombra baseline. It carries appearance, font size, live reload, and OSC 52 policy, while deliberately omitting scrollback, shell selection, startup directory, tabs, and host paths. A Ward verb validates the file against the installed Alacritty schema. The host-local root config retains only Windows shell and startup-directory preferences until infrastructure convergence.

Follow-up landed on canonical `main` in commit `ec3b0d6`: AOS now tracks `alacritty/alacritty.toml` as the portable Sombra baseline. It carries appearance, font size, live reload, and OSC 52 policy, while deliberately omitting scrollback, shell selection, startup directory, tabs, and host paths. A Ward verb validates the file against the installed Alacritty schema. The host-local root config retains only Windows shell and startup-directory preferences until infrastructure convergence.
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#730
No description provided.