GT - GhostOS Terminal

GT - GhostOS Terminal is the VS Code client for GhostTerminal.

It keeps VS Code as a client of GT, not as the control plane itself.

The Marketplace identity for this extension is:

If your Visual Studio Marketplace publisher uses a different id, change the publisher field in package.json before publishing.

Licensing:

product license: C:\Users\Bullshit Lab\Desktop\ghostOS\GT\LICENSE.txt
product EULA: C:\Users\Bullshit Lab\Desktop\ghostOS\GT\EULA.md
extension package license: C:\Users\Bullshit Lab\Desktop\ghostOS\GT\vscode\LICENSE.txt

Current Capabilities

launch ghostterm_host commands from the Command Palette and Explorer
appear in the VS Code terminal profile picker as GT - GhostOS Terminal
auto-detect the local ghostOS repository from the current workspace, or use the ghostterminal.repoRoot setting when needed
open GT-managed mobile build, ISO, VMware, selfhost, serial, and ghostOS shell sessions
run a captured mobile build and publish compiler warnings and errors into the Problems panel
explore generated .gbir files under mobile/out
open GBIR summaries inside VS Code through a virtual document view
query live ghostOS runtime state through ghostos status, ghostos ping, ghostos ui, and ghostos send

The extension root is:

C:\Users\Bullshit Lab\Desktop\ghostOS\GT\vscode

Syntax check:

cd C:\Users\Bullshit Lab\Desktop\ghostOS\GT\vscode
node --check .\extension.js

VSIX packaging:

cd C:\Users\Bullshit Lab\Desktop\ghostOS\GT\vscode
powershell -ExecutionPolicy Bypass -File .\build_vsix.ps1

The packaged file will be written under:

C:\Users\Bullshit Lab\Desktop\ghostOS\GT\vscode\dist

GT-native package flow:

cd C:\Users\Bullshit Lab\Desktop\ghostOS
.\GT\bin\ghostterm_host.exe vscode package

GT-native install flow:

cd C:\Users\Bullshit Lab\Desktop\ghostOS
.\GT\bin\ghostterm_host.exe vscode install

The extension expects:

Create or confirm your Visual Studio Marketplace publisher id.
Make sure the publisher field in package.json matches that publisher id exactly.
Package the extension:

cd C:\Users\Bullshit Lab\Desktop\ghostOS\GT\vscode
powershell -ExecutionPolicy Bypass -File .\build_vsix.ps1

vsce login Imagine

vsce publish

Or use the GT-native publish flow:

cd C:\Users\Bullshit Lab\Desktop\ghostOS
$env:VSCE_PAT = "<your_marketplace_token>"
.\GT\bin\ghostterm_host.exe vscode publish

interactive shell and serial flows are launched in an integrated VS Code terminal
captured diagnostics use ghostterm_host mobile build and parse compiler-style messages into Problems
passive runtime inspection can use the live serial marker path even when the GhostTransport shell is not open
release notes: CHANGELOG.md
support notes: SUPPORT.md