Need a way to manage the sessions and redirect their pipes.

[sharpninja]

It would be good to be able to create a monitoring app that can manage the sessions and redirect the input/output for logging and analysis purposes.

[yotsuda]

@sharpninja — thanks for the idea. 1.14.1 covers the logging part with PowerShell's own tools rather than a new interface.

Start-Transcript is now a complete record. It used to capture each command's output but not the command itself; now both land in the transcript, in order. Add this to your $PROFILE and every console that loads it keeps its own log:

$dir = Join-Path $HOME 'transcripts'
New-Item -ItemType Directory -Path $dir -Force | Out-Null
Start-Transcript -OutputDirectory $dir | Out-Null

A monitoring app can tail or index those files without touching the module. For an audit trail that's harder to tamper with, use PowerShell 7's Script Block Logging — see Auditing an AI Session.

I'd rather not expose the pipes themselves: the pipe between the proxy and a console is a control channel (whatever goes down it runs) with an internal protocol, so redirecting it would mean handing another process your shell.

If you need a session-management operation or live data that transcripts don't give you, let me know what it is.

[sharpninja]

Session Management (List of sessions, kill session, get log by session) would all be extremely usefull. Get Outlook for Android<https://aka.ms/AAb9ysg>

…

________________________________ From: Yoshifumi ***@***.***> Sent: Sunday, 13 September 2026 03:24:12 To: yotsuda/PowerShell.MCP ***@***.***> Cc: Payton Byrd ***@***.***>; Mention ***@***.***> Subject: Re: [yotsuda/PowerShell.MCP] Need a way to manage the sessions and redirect their pipes. (Discussion #57) @sharpninja<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_sharpninja&d=DwMFaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=As2uQNd8xtAcBVJiKEgSSZTvTvbVAzhKL-ZnasVVLn8&m=oCp_IXJdyCxAE5GpZV4nwbzSPABtbwnAQ5A_-Af_AE4jl1yA8bkTomdxWF0Yyjnz&s=PvLmP5IP6ptFaSqZD7W8L35PaqTwzOmYTNtB4CqBKm0&e=> — thanks for the idea. 1.14.1<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_yotsuda_PowerShell.MCP_releases_tag_v1.14.1&d=DwMFaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=As2uQNd8xtAcBVJiKEgSSZTvTvbVAzhKL-ZnasVVLn8&m=oCp_IXJdyCxAE5GpZV4nwbzSPABtbwnAQ5A_-Af_AE4jl1yA8bkTomdxWF0Yyjnz&s=3CdJ83zejd2tBpd4qgeDLgXyk8mZWEAEowVGD3GUkxo&e=> covers the logging part with PowerShell's own tools rather than a new interface. Start-Transcript is now a complete record. It used to capture each command's output but not the command itself; now both land in the transcript, in order. Add this to your $PROFILE and every console that loads it keeps its own log: $dir = Join-Path $HOME 'transcripts' New-Item -ItemType Directory -Path $dir -Force | Out-Null Start-Transcript -OutputDirectory $dir | Out-Null A monitoring app can tail or index those files without touching the module. For an audit trail that's harder to tamper with, use PowerShell 7's Script Block Logging — see Auditing an AI Session<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_yotsuda_PowerShell.MCP_blob_main_SECURITY.md-23auditing-2Dan-2Dai-2Dsession&d=DwMFaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=As2uQNd8xtAcBVJiKEgSSZTvTvbVAzhKL-ZnasVVLn8&m=oCp_IXJdyCxAE5GpZV4nwbzSPABtbwnAQ5A_-Af_AE4jl1yA8bkTomdxWF0Yyjnz&s=q8Q50PMMXdkRAH-EOzIFjRx-xF73Iuid-e2zb5lc06c&e=>. I'd rather not expose the pipes themselves: the pipe between the proxy and a console is a control channel (whatever goes down it runs) with an internal protocol, so redirecting it would mean handing another process your shell. If you need a session-management operation or live data that transcripts don't give you, let me know what it is. — Reply to this email directly, view it on GitHub<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_yotsuda_PowerShell.MCP_discussions_57-3Femail-5Fsource-3Dnotifications-26email-5Ftoken-3DAD3GCLCQTZFBUYLFV4KQFML5OZKSZA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBUGE4TMMJSUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y-23discussioncomment-2D18419612&d=DwMFaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=As2uQNd8xtAcBVJiKEgSSZTvTvbVAzhKL-ZnasVVLn8&m=oCp_IXJdyCxAE5GpZV4nwbzSPABtbwnAQ5A_-Af_AE4jl1yA8bkTomdxWF0Yyjnz&s=z45gSoACGwdT2hGU3yuDZTdXTDst2Wi3y9De6jnYocY&e=>, or unsubscribe<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AD3GCLE6ER25H7LJTE2KVFT5OZKSZAVCNFSNUABJKJSXA33TNF2G64TZHMYTAMBRHE3TCNRUHA5UI2LTMN2XG43JN5XDWMJQG44DEOJTG2QXMAQ&d=DwMFaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=As2uQNd8xtAcBVJiKEgSSZTvTvbVAzhKL-ZnasVVLn8&m=oCp_IXJdyCxAE5GpZV4nwbzSPABtbwnAQ5A_-Af_AE4jl1yA8bkTomdxWF0Yyjnz&s=LnGiG3v3FWGGN8B_puM3UHzSt3UKx2JHxWD-qQoH4CI&e=>. You are receiving this because you were mentioned.Message ID: ***@***.***>