coilyco-flight-deck/agentic-os

Watch

Spike live Alacritty director feedback from Agent Proxy metadata #738

New issue

Closed

opened 2026-07-25 03:33:41 +00:00 by coilyco-ops · 0 comments

coilyco-ops commented

2026-07-25 03:33:41 +00:00

Owner

Outcome

Determine which Alacritty capabilities can turn Agent Proxy current-run metadata into useful, playful feedback for director windows on both Windows and macOS. Produce an evidence-backed recommendation before AOS commits to a live bridge.

This spike follows the static agent-terminal branding from #730. It does not replace native artifact work in #734 or host convergence in coilyco-flight-deck/infrastructure#639 and coilyco-flight-deck/infrastructure#641.

Ownership contract

Agent Proxy owns normalized, correlated runtime facts and their read API.
Agent Compose owns renderer-neutral role and personality identity.
Ward and AOS own launch context and lifecycle.
agent-terminal owns translation into Alacritty behavior.
Infrastructure owns installation and host-local configuration.

Questions to answer

Which properties can change without restarting a window: title, cursor, selection, background, bell or urgency state, icon, class, and shell-visible annotations?
Which mechanisms work on each native platform: OSC sequences through the PTY, live config reload, alacritty msg, child-controlled titles, or a small sidecar?
Alacritty documents its IPC socket as Unix-only. What is the honest Windows fallback?
Can an adapter target exactly one director window without changing unrelated terminals?
Can every live change restore the static baseline on normal exit, crash, disconnect, and stale-run timeout?
Should updates be event-driven or poll a bounded Agent Proxy current-run endpoint? What cadence avoids flicker and needless load?
Which safe scalars are genuinely useful at a glance: harness, effective role, repo and issue, workflow, expression or state, blocked or HITL state, and model or provider class?
What useful Warp affordances remain missing in Alacritty after the current startup-directory, palette, font, opacity, live-reload, and OSC 52 work?

Capability audit

Test the installed or currently supported Alacritty release on native Windows and macOS. Record a compact matrix for each candidate behavior with:

mechanism
Windows support
macOS support
per-window targeting
reset behavior
latency and overhead
security or terminal-injection risk
whether AOS, Agent Proxy, Agent Compose, or Infrastructure owns any follow-up

The audit should include dynamic titles, colors, cursor and selection accents, bell or urgency indicators, hyperlinks, working-directory inheritance, opening a new window in the current directory, keybindings, shell integration, and any other useful Warp-to-Alacritty compatibility gap discovered during the spike.

Proof of concept

Build only enough disposable or clearly marked probe code to demonstrate the capability boundary. A fixture payload may stand in for the Agent Proxy API, so coilysiren/inbox#263 is related but not a blocker.

Demonstrate, where supported:

one per-window title update
one visual state update driven by a safe metadata fixture
restoration to the static agent-terminal baseline
rejection or normalization of control characters and hostile metadata
graceful behavior when Agent Proxy is unavailable

Do not ship a resident bridge from this issue unless the evidence makes it both trivial and clearly within the spike boundary.

Acceptance criteria

The issue records native Windows and macOS evidence, including version and exact mechanism tested.
The capability matrix distinguishes supported, unsupported, platform-specific, and unknown behavior.
The proof verifies per-window isolation and baseline restoration wherever live mutation is possible.
The issue records measured polling or event overhead if Agent Proxy participates in the probe.
The final recommendation chooses one bounded product shape: static only, title only, title plus visual state, or no-go.
Any implementation work becomes small follow-up issues in the owning repositories.

Safety

Never expose secrets, prompt or response bodies, raw endpoints, opaque identifiers, or unrestricted filesystem paths.
Treat every metadata value as untrusted terminal input.
Keep static launch branding as the failure mode.
No full TUI, tabs or panes, Agent Proxy configuration ownership, permission changes, action buttons, prompt display, host rollout, or replacement for #734, infrastructure#639, or infrastructure#641.

References

#730
#734
coilysiren/inbox#263
coilyco-flight-deck/infrastructure#639
coilyco-flight-deck/infrastructure#641
Alacritty runtime message interface
Alacritty configuration reference
Alacritty releases

## Outcome Determine which Alacritty capabilities can turn Agent Proxy current-run metadata into useful, playful feedback for director windows on both Windows and macOS. Produce an evidence-backed recommendation before AOS commits to a live bridge. This spike follows the static `agent-terminal` branding from #730. It does not replace native artifact work in #734 or host convergence in `coilyco-flight-deck/infrastructure#639` and `coilyco-flight-deck/infrastructure#641`. ## Ownership contract * Agent Proxy owns normalized, correlated runtime facts and their read API. * Agent Compose owns renderer-neutral role and personality identity. * Ward and AOS own launch context and lifecycle. * `agent-terminal` owns translation into Alacritty behavior. * Infrastructure owns installation and host-local configuration. ## Questions to answer * Which properties can change without restarting a window: title, cursor, selection, background, bell or urgency state, icon, class, and shell-visible annotations? * Which mechanisms work on each native platform: OSC sequences through the PTY, live config reload, `alacritty msg`, child-controlled titles, or a small sidecar? * Alacritty documents its IPC socket as Unix-only. What is the honest Windows fallback? * Can an adapter target exactly one director window without changing unrelated terminals? * Can every live change restore the static baseline on normal exit, crash, disconnect, and stale-run timeout? * Should updates be event-driven or poll a bounded Agent Proxy current-run endpoint? What cadence avoids flicker and needless load? * Which safe scalars are genuinely useful at a glance: harness, effective role, repo and issue, workflow, expression or state, blocked or HITL state, and model or provider class? * What useful Warp affordances remain missing in Alacritty after the current startup-directory, palette, font, opacity, live-reload, and OSC 52 work? ## Capability audit Test the installed or currently supported Alacritty release on native Windows and macOS. Record a compact matrix for each candidate behavior with: * mechanism * Windows support * macOS support * per-window targeting * reset behavior * latency and overhead * security or terminal-injection risk * whether AOS, Agent Proxy, Agent Compose, or Infrastructure owns any follow-up The audit should include dynamic titles, colors, cursor and selection accents, bell or urgency indicators, hyperlinks, working-directory inheritance, opening a new window in the current directory, keybindings, shell integration, and any other useful Warp-to-Alacritty compatibility gap discovered during the spike. ## Proof of concept Build only enough disposable or clearly marked probe code to demonstrate the capability boundary. A fixture payload may stand in for the Agent Proxy API, so `coilysiren/inbox#263` is related but not a blocker. Demonstrate, where supported: * one per-window title update * one visual state update driven by a safe metadata fixture * restoration to the static `agent-terminal` baseline * rejection or normalization of control characters and hostile metadata * graceful behavior when Agent Proxy is unavailable Do not ship a resident bridge from this issue unless the evidence makes it both trivial and clearly within the spike boundary. ## Acceptance criteria * The issue records native Windows and macOS evidence, including version and exact mechanism tested. * The capability matrix distinguishes supported, unsupported, platform-specific, and unknown behavior. * The proof verifies per-window isolation and baseline restoration wherever live mutation is possible. * The issue records measured polling or event overhead if Agent Proxy participates in the probe. * The final recommendation chooses one bounded product shape: static only, title only, title plus visual state, or no-go. * Any implementation work becomes small follow-up issues in the owning repositories. ## Safety * Never expose secrets, prompt or response bodies, raw endpoints, opaque identifiers, or unrestricted filesystem paths. * Treat every metadata value as untrusted terminal input. * Keep static launch branding as the failure mode. * No full TUI, tabs or panes, Agent Proxy configuration ownership, permission changes, action buttons, prompt display, host rollout, or replacement for #734, infrastructure#639, or infrastructure#641. ## References * #730 * #734 * `coilysiren/inbox#263` * `coilyco-flight-deck/infrastructure#639` * `coilyco-flight-deck/infrastructure#641` * [Alacritty runtime message interface](https://alacritty.org/cmd-alacritty-msg.html) * [Alacritty configuration reference](https://alacritty.org/config-alacritty.html) * [Alacritty releases](https://github.com/alacritty/alacritty/releases)

coilyco-ops

2026-07-29 03:44:57 +00:00

closed this issue
added the
autonomy
async-consult

priority
P4
labels

coilyco-ops referenced this issue

2026-08-28 06:48:35 +00:00

Remove stale Ward QA fixture repository pointers #1294

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#738

No description provided.

Rows
Columns