perf(warp): avoid Bash subprocess during PowerShell startup #726

Closed
opened 2026-07-24 21:05:15 +00:00 by coilyco-ops · 1 comment
Owner

Problem

The rendered PowerShell profile launches Git Bash, sources shell/common.sh, prints the full environment, and reparses it on every PowerShell startup. Local measurements show that bridge adds roughly one second at the median and occasionally several seconds.

Outcome

  • The Warp renderer emits the required Windows environment and PATH setup without launching Bash during PowerShell startup.
  • Shared values retain one canonical owner and do not drift between shell implementations.
  • Warp rendering tests cover the native PowerShell output.
  • ward exec warp-test and repository pre-commit validation pass.
## Problem The rendered PowerShell profile launches Git Bash, sources `shell/common.sh`, prints the full environment, and reparses it on every PowerShell startup. Local measurements show that bridge adds roughly one second at the median and occasionally several seconds. ## Outcome * The Warp renderer emits the required Windows environment and PATH setup without launching Bash during PowerShell startup. * Shared values retain one canonical owner and do not drift between shell implementations. * Warp rendering tests cover the native PowerShell output. * `ward exec warp-test` and repository pre-commit validation pass.
Author
Owner

workflow: pull-request-and-merge

Implementation checkpoint: b24d769 on issue-726-warp-pwsh-startup.

Create the Forgejo PR from the pushed branch: https://forgejo.coilysiren.me/coilyco-flight-deck/agentic-os/compare/main...issue-726-warp-pwsh-startup

Measured fresh-process startup:

  • Bare PowerShell: 468 ms median
  • Previous rendered profile: 1.73 s median
  • Native rendered profile: 497 ms median

Validation:

  • ward exec warp-test passed
  • Focused shellcheck for shell/common.sh passed
  • Rendered PowerShell syntax and environment probes passed
  • Applicable all-files hooks passed
  • Full Python suite: 525 passed, 16 existing native-Windows fixture failures
workflow: pull-request-and-merge Implementation checkpoint: `b24d769` on `issue-726-warp-pwsh-startup`. Create the Forgejo PR from the pushed branch: https://forgejo.coilysiren.me/coilyco-flight-deck/agentic-os/compare/main...issue-726-warp-pwsh-startup Measured fresh-process startup: * Bare PowerShell: 468 ms median * Previous rendered profile: 1.73 s median * Native rendered profile: 497 ms median Validation: * `ward exec warp-test` passed * Focused shellcheck for `shell/common.sh` passed * Rendered PowerShell syntax and environment probes passed * Applicable all-files hooks passed * Full Python suite: 525 passed, 16 existing native-Windows fixture failures
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#726
No description provided.