Add TCP console socket support, Windows helper scripts and documentation updates - #19

Open

boscv wants to merge 25 commits into

codex/find-remote-control-plugin-for-korefrom

codex/troubleshoot-openkore-remote-connection-issue

Commits on Apr 15, 2026

Add one-command Windows startup script for OpenKore remote stack
boscv
committed
46d7f1f
Support launcher exe and double-click startup for Windows remote stack
boscv
committed
c68d5f2
Clarify auto-detection behavior and existing OpenKore reuse in Windows helper
boscv
committed
bbc2e4a
Make Windows helper configure-only by default and document launcher usage
boscv
committed
d53b4b4
Fix PowerShell automatic variable collisions in TCP checks
boscv
committed
7603471
Fix remaining PowerShell Host automatic variable collision
boscv
committed
de65216
Use platform console loader in Socket interface to avoid Utils::Unix failure on Windows
boscv
committed
f233e50
Launch OpenKore in a new window from generated env helper
boscv
committed
dba46ce
Open TCP env launcher in interactive cmd window for local typing
boscv
committed
5497c8b
Use Console::Simple safely on Windows for Socket interface input loop
boscv
committed
b487f5f
Add one-shot Windows launcher to start OpenKore socket endpoint and gateway
boscv
committed
6d6eb00
Make run-remote.cmd fully standalone and mark as primary simple flow
boscv
committed
090b88f
Rewrite run-remote.cmd with robust batch conditionals to avoid parser errors
boscv
committed
ff3df63
Remove dependency on if.pm for Windows compatibility in Console::Simple
boscv
committed
58e3154
Use platform console backend in Socket interface to restore Windows input handling
boscv
committed
81f6eb7
Launch OpenKore via cmd /k in run-remote to preserve interactive typing
boscv
committed
7ce94ee

Commits on Apr 16, 2026

Launch OpenKore with normal launcher flow in run-remote
boscv
committed
883f775
Simplify PT-BR docs to single run-remote.cmd flow
boscv
committed
9b8dee4
Remove launcher auto-detection from run-remote and require explicit user choice
boscv
committed
07df042
Fix Windows console input by reading from CONIN$
boscv
committed
979394f
Fix run-remote.cmd to open separate Windows consoles
boscv
committed
bcad671
Fix run-remote.cmd Windows quoting for start/cmd invocations
boscv
committed
37e776f
Default Windows Socket interface to TCP endpoint
boscv
committed
983adb5
Avoid UNIX socket path on Perl builds without sockaddr_un
boscv
committed
a5ff5d2
Fallback to TCP when OPENKORE_SOCKET_TCP_PORT is empty/invalid
boscv
committed
442d41e

Navigation Menu

Add TCP console socket support, Windows helper scripts and documentation updates - #19

Add TCP console socket support, Windows helper scripts and documentation updates#19
boscv wants to merge 25 commits into
codex/find-remote-control-plugin-for-korefrom
codex/troubleshoot-openkore-remote-connection-issue

Commits on Apr 15, 2026

Add one-command Windows startup script for OpenKore remote stack

Support launcher exe and double-click startup for Windows remote stack

Clarify auto-detection behavior and existing OpenKore reuse in Windows helper

Make Windows helper configure-only by default and document launcher usage

Fix PowerShell automatic variable collisions in TCP checks

Fix remaining PowerShell Host automatic variable collision

Use platform console loader in Socket interface to avoid Utils::Unix failure on Windows

Launch OpenKore in a new window from generated env helper

Open TCP env launcher in interactive cmd window for local typing

Use Console::Simple safely on Windows for Socket interface input loop

Add one-shot Windows launcher to start OpenKore socket endpoint and gateway

Make run-remote.cmd fully standalone and mark as primary simple flow

Rewrite run-remote.cmd with robust batch conditionals to avoid parser errors

Remove dependency on if.pm for Windows compatibility in Console::Simple

Use platform console backend in Socket interface to restore Windows input handling

Launch OpenKore via cmd /k in run-remote to preserve interactive typing

Commits on Apr 16, 2026

Launch OpenKore with normal launcher flow in run-remote

Simplify PT-BR docs to single run-remote.cmd flow

Remove launcher auto-detection from run-remote and require explicit user choice

Fix Windows console input by reading from CONIN$

Fix run-remote.cmd to open separate Windows consoles

Fix run-remote.cmd Windows quoting for start/cmd invocations

Default Windows Socket interface to TCP endpoint

Avoid UNIX socket path on Perl builds without sockaddr_un

Fallback to TCP when OPENKORE_SOCKET_TCP_PORT is empty/invalid