Skip to content

v0.1.1

Choose a tag to compare

View all tags
@ethanffu ethanffu released this 06 Aug 15:53
· 27 commits to main since this release
v0.1.1
300fdcc

v0.1.1 — Windows Terminal-hosted interactive PowerShell

Fix (important): the PowerShell window flash-closed when Obsidian was launched from Explorer (GUI process without a console). The formal session is now hosted in Windows Terminal (wt.exe) purely as the console window host, so pwsh receives real console handles. Falls back to a direct pwsh.exe spawn when wt.exe is missing or the vault path contains ; (wt splits on semicolons).

Also in this release:

  • npm run install:test now registers the plugin in the test vault's enabled-plugins list (community-plugins.json) — no manual enable needed.
  • Full CI (npm run verify) on Windows: lint, typecheck, 63 automated tests, build, main.js sync check.

Manually verified in real Obsidian (2026-08-08):

  • Interactive PowerShell window opens from the ribbon; input/output work
  • Get-Location equals the vault root; $PSVersionTable.PSVersion.Major >= 7
  • Session survives closing Obsidian; plugin auto-loads on vault open

Scope & constraints:

  • Windows + PowerShell 7+ only (Windows PowerShell 5.1 is not supported)
  • Ribbon button is the only entry point (no commands, settings, or embedded terminal)
  • No telemetry, no network access, no vault modification; the plugin never invokes cmd.exe / powershell.exe / conhost.exe / shell:true

Assets: main.js, manifest.json, versions.json (no styles.css — the plugin ships no CSS).

Assets 6
Loading