[OneDev #18] chore(station): install and verify PowerShell 7 #27

Closed
opened 2026-05-24 04:46:39 +00:00 by joseph · 1 comment
Owner

Imported from OneDev issue #18 (id 35319)
Original project: internal-joseph
Original state: Closed
Original submitterId: 5
Original submitDate: 2026-04-13T17:24:40.245+00:00
Original lastActivity: {'date': '2026-04-18T12:52:36.446+00:00', 'description': "changed state to 'Closed'", 'userId': 5}

Original fields:

  • Type: New Feature
  • Priority: Normal
  • Assignees: None

Idea

Ensure PowerShell 7 (pwsh) is installed on Station, pinned to a known version, and verified working — confirming it's the default shell invoked by scripts and tooling rather than Windows PowerShell 5.1.

Why

Several tools in the PCT stack (and Claude CLI wrappers) behave differently or break entirely on PS 5.1. Having PS7 confirmed and on $PATH prevents subtle cross-version bugs and keeps the environment consistent with other machines.

Open questions

  • Install via winget, scoop, or MSI? Pick one and document it in dotfiles.
  • Should pwsh be set as the default terminal profile in Windows Terminal?
Imported from OneDev issue #18 (id 35319) Original project: internal-joseph Original state: Closed Original submitterId: 5 Original submitDate: 2026-04-13T17:24:40.245+00:00 Original lastActivity: {'date': '2026-04-18T12:52:36.446+00:00', 'description': "changed state to 'Closed'", 'userId': 5} Original fields: - Type: New Feature - Priority: Normal - Assignees: None ## Idea Ensure PowerShell 7 (pwsh) is installed on Station, pinned to a known version, and verified working — confirming it's the default shell invoked by scripts and tooling rather than Windows PowerShell 5.1. ## Why Several tools in the PCT stack (and Claude CLI wrappers) behave differently or break entirely on PS 5.1. Having PS7 confirmed and on `$PATH` prevents subtle cross-version bugs and keeps the environment consistent with other machines. ## Open questions - Install via winget, scoop, or MSI? Pick one and document it in dotfiles. - Should `pwsh` be set as the default terminal profile in Windows Terminal?
Author
Owner

Imported from OneDev comment id 374 on issue #18
Original userId: 5
Original date: 2026-04-18T12:52:35.446+00:00

Superseded by #13. tui-use is a concrete implementation of this vision — the ecosystem converged on node-pty + xterm-headless. However, #13 is now expanded to cover a broader evaluation: ghst (our self-built PTY tool) vs tui-use, with potential outcomes including extend ghst, borrow tui-use ideas, or abandon ghst entirely if tui-use is significantly better. Tracking there.

Imported from OneDev comment id 374 on issue #18 Original userId: 5 Original date: 2026-04-18T12:52:35.446+00:00 Superseded by #13. tui-use is a concrete implementation of this vision — the ecosystem converged on node-pty + xterm-headless. However, #13 is now expanded to cover a broader evaluation: ghst (our self-built PTY tool) vs tui-use, with potential outcomes including extend ghst, borrow tui-use ideas, or abandon ghst entirely if tui-use is significantly better. Tracking there.
Sign in to join this conversation.
No labels
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
joseph/internal-joseph#27
No description provided.