Remove retired Warp tab launcher machinery #727

New issue

Open

opened 2026-07-24 21:11:42 +00:00 by coilyco-ops · 1 comment

coilyco-ops commented

2026-07-24 21:11:42 +00:00

Owner

Outcome

Remove the retired Warp tab and launch-configuration machinery from agentic-os.

Kai has not used the launcher flow in a month. Ward already retired the old --watch and --new-tab surfaces in ward#356. Agentic-os still carries the former consumer-side implementation and documentation.

Remove

The ward agent ... --new-tab queue shim and its Warp launch configuration.
The checked-in warp/tab_configs/ and warp/launch_configurations/ surfaces, including the dynamic wtab helper and startup tab config.
Warp URI dispatch through warp:// and warppreview://.
The launch-config symlink reconciliation and related host-path fields in the Warp module.
The default_tab_config_path setting and any tab-config rendering.
Shell functions whose purpose is opening Warp tabs or launch configurations.
Documentation, skill guidance, layout exceptions, and tests that describe or preserve the retired launcher.

Preserve

Basic Warp settings and theme management while Warp remains installed during terminal migration.
The mouse-reporting recovery binding unless separate evidence shows the replacement terminal makes it safe to remove.
Generic shell startup-directory behavior that remains useful outside Warp. Rename any Warp-specific variable or wording only when the current owner is clear.

Acceptance criteria

No tracked tab config, launch config, queue shim, or Warp URI launcher remains.
The Warp apply and doctor paths manage only the retained basic configuration.
Existing owned links or rendered files receive an ownership-scoped cleanup path. Fleet rollout stays in infrastructure if host convergence is required.
Repository documentation describes Warp as a transitional basic terminal configuration, not an agent-launch surface.
A repository-wide search finds no live references to the retired Ward --new-tab workflow.
ward exec test passes.
ward exec pre-commit-all passes.

Non-goals

Selecting or installing Warp's replacement.
Building an agent-compose terminal renderer.
Changing Ward's current director or headless worker workflow.

## Outcome Remove the retired Warp tab and launch-configuration machinery from agentic-os. Kai has not used the launcher flow in a month. Ward already retired the old `--watch` and `--new-tab` surfaces in [ward#356](https://forgejo.coilysiren.me/coilyco-flight-deck/ward/issues/356). Agentic-os still carries the former consumer-side implementation and documentation. ## Remove * The `ward agent ... --new-tab` queue shim and its Warp launch configuration. * The checked-in `warp/tab_configs/` and `warp/launch_configurations/` surfaces, including the dynamic `wtab` helper and startup tab config. * Warp URI dispatch through `warp://` and `warppreview://`. * The launch-config symlink reconciliation and related host-path fields in the Warp module. * The `default_tab_config_path` setting and any tab-config rendering. * Shell functions whose purpose is opening Warp tabs or launch configurations. * Documentation, skill guidance, layout exceptions, and tests that describe or preserve the retired launcher. ## Preserve * Basic Warp settings and theme management while Warp remains installed during terminal migration. * The mouse-reporting recovery binding unless separate evidence shows the replacement terminal makes it safe to remove. * Generic shell startup-directory behavior that remains useful outside Warp. Rename any Warp-specific variable or wording only when the current owner is clear. ## Acceptance criteria * No tracked tab config, launch config, queue shim, or Warp URI launcher remains. * The Warp apply and doctor paths manage only the retained basic configuration. * Existing owned links or rendered files receive an ownership-scoped cleanup path. Fleet rollout stays in infrastructure if host convergence is required. * Repository documentation describes Warp as a transitional basic terminal configuration, not an agent-launch surface. * A repository-wide search finds no live references to the retired Ward `--new-tab` workflow. * `ward exec test` passes. * `ward exec pre-commit-all` passes. ## Non-goals * Selecting or installing Warp's replacement. * Building an agent-compose terminal renderer. * Changing Ward's current director or headless worker workflow.

coilyco-ops referenced this issue

2026-07-24 21:26:13 +00:00

Add agent-compose branded Alacritty director launcher #730

coilyco-ops referenced this issue from coilyco-flight-deck/infrastructure

2026-07-24 22:01:57 +00:00

Converge Alacritty branded director terminals on native hosts #639

coilysiren referenced this issue from a commit

2026-07-24 22:24:47 +00:00

docs: retire Warp paste workaround (refs #727)

coilyco-ops commented

2026-07-24 22:25:06 +00:00

Author

Owner

Landed the command-delivery sub-scope on canonical main in commit 0668795. The public AOS base no longer carries the Warp-specific /tmp launcher, fixed 25-character threshold, or terminal paste workaround. The execution-boundary and reusable-script rules remain. A repository-wide search finds no live heredoc or equivalent Warp-paste wording. Stale matches in agentic-os-kai are generated May repo digests and should disappear through their scheduled source refresh.

Landed the command-delivery sub-scope on canonical `main` in commit `0668795`. The public AOS base no longer carries the Warp-specific `/tmp` launcher, fixed 25-character threshold, or terminal paste workaround. The execution-boundary and reusable-script rules remain. A repository-wide search finds no live heredoc or equivalent Warp-paste wording. Stale matches in agentic-os-kai are generated May repo digests and should disappear through their scheduled source refresh.

coilyco-ops added the

autonomy

live-collab

priority

labels

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

coilyco-ops added

priority

and removed

priority

labels

2026-08-05 10:25:53 +00:00