fix(devices): let Windows SSH device startup close its session#24370

🏁 Script executed:

bash

1	set -o pipefail
2	printf '%s\n' '--- changed paths ---'
3	git diff --name-only aaf4a901c490da4f0943afe1d941f3a8d58dc1c8 e76d400a4c6bf12bc6943536e7b35cca192026a2
4	printf '%s\n' '--- target file relevant lines ---'
5	nl -ba apps/server/src/device/sshDeviceScript.ts | sed -n '1,340p'
6	printf '%s\n' '--- references and tests ---'
7	rg -n -F --glob '*.{ts,tsx}' -e 'sshDeviceScript' -e 'powershell.exe' -e 'EncodedCommand' -e 'options.input' apps packages || test "$?" -eq 1

Repository: pingdotgg/t3code

Length of output: 23750

---

🏁 Script executed:

bash

1	printf '%s\n' '--- device test ---'
2	nl -ba apps/server/src/device/sshDeviceScript.test.ts | sed -n '1,180p'
3	printf '%s\n' '--- existing encoded-command implementation ---'
4	nl -ba apps/server/src/process/externalLauncher.ts | sed -n '50,105p'
5	printf '%s\n' '--- relevant diff ---'
6	git diff --unified=25 aaf4a901c490da4f0943afe1d941f3a8d58dc1c8 e76d400a4c6bf12bc6943536e7b35cca192026a2 -- apps/server/src/device/sshDeviceScript.ts apps/server/src/device/sshDeviceScript.test.ts

Repository: pingdotgg/t3code

Length of output: 33249

---

🌐 Web query:

Microsoft Windows PowerShell 5.1 powershell.exe -Command - stdin encoding and -EncodedCommand UTF-16LE documentation

💡 Result:

1	<source_evidence>
2	<source kind="search">
3	<title>about_PowerShell_exe - PowerShell | Microsoft Learn</title>
4	<location>https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_powershell_exe?view=powershell-5.1&amp;viewFallbackFrom=powershell-Microsoft.PowerShell.Core</location>
5	<excerpt>citeturn0search0 [wordlim: 200] Crawled: 5 days ago; PowerShell -PSConsoleFile sqlsnapin.psc1 ... # To use the -EncodedCommand parameter: ... powershell.exe -EncodedCommand $encodedCommand
6	### -ConfigurationName &lt;string&gt;
7
8	Specifies a configuration endpoint in which PowerShell is run. This can be any endpoint registered on the local machine including the default PowerShell remoting endpoints or a custom endpoint having specific user role capabilities.
9
10	### -EncodedArguments &lt;Base64EncodedArguments&gt;
11
12	Accepts a Base64-encoded string version command arguments. Use this parameter to submit arguments that require complex, nested quoting. The Base64 representation must be a UTF-16LE encoded string.
13
14	### -EncodedCommand &lt;Base64EncodedCommand&gt;
15
16	Accepts a base-64-encoded string version of a command. Use this parameter to submit commands to PowerShell that require complex quotation marks or curly braces. The string must be formatted using UTF-16LE character encoding.
17
18	### -ExecutionPolicy &lt;ExecutionPolicy&gt;
19
20	Sets the default execution policy for the current session and saves it in the `$Env:PSExecutionPolicyPreference` environment variable. This parameter does not change the PowerShell execution policy that&#39;s set in the registry. ## Remarks
21
22	Troubleshooting note: In PowerShell 2.0, starting some programs from the PowerShell console fails with a LastExitCode of 0xc0000142.
23
24	## Examples
25
26	PowerShell
27
28	Copy
29
30	`# Create a new PowerShell session and load a saved console file
31	PowerShell -PSConsoleFile sqlsnapin.psc1
32
33	# Create a new PowerShell V2 session with text input, XML output, and no logo
34	PowerShell -Version 2.0 -NoLogo -InputFormat text -OutputFormat XML
35
36	# Execute a PowerShell Command in a session
37	PowerShell -Command &quot;Get-EventLog -LogName Security&quot;
38
39	# Run a script block in a session
40	PowerShell -Command {Get-EventLog -LogName Security}
41
42	# An alternate way to run a command in a new session
43	PowerShell -Command &quot;&amp; {Get-EventLog -LogName Security}&quot;
44
45	# To use the -EncodedCommand parameter:
46	$command = &quot;dir &#39;C:\Program Files&#39; &quot;
47	$bytes = [System.Text.Encoding]::Unicode.GetBytes($command)
48	$encodedCommand = [Convert]::ToBase64String($bytes)
49	powershell.exe -EncodedCommand $encodedCommand
50	`
51
52	Collaborate with us on GitHub
53
54	The source for this content can be found on GitHub, where you can also create and review issues and pull requests. For more information, see our contributor guide.
55
56	* Last updated on 07/23/2024</excerpt>
57	</source>
58	<source kind="search">
59	<title>about_PowerShell_exe - PowerShell | Microsoft Learn</title>
60	<location>https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_powershell_exe?view=powershell-5.1</location>
61	<excerpt>citeturn0search2 [wordlim: 200] Published: 2.3 years ago; Crawled: 2 days ago; 5. ... Displays the command-line parameters and describes the syntax. ... For example, the following command uses the All parameter of the `Get-Script.ps1` script file: `-File . ... If Windows PowerShell 3.0 is installed on the computer, &quot;3.0&quot; is the default version. ... powershell.exe -EncodedCommand $encodedCommand
62
63	# about_PowerShell_exe
64
65	Feedback
66
67	Summarize this article for me
68
69	## In this article
70
71	1. SHORT DESCRIPTION
72	2. LONG DESCRIPTION
73	3. Syntax
74	4. Parameters
75	5. Remarks
76	6. Examples
77	Show 2 more
78
79	## SHORT DESCRIPTION
80
81	Explains how to use the `powershell.exe` command-line interface. Displays the command-line parameters and describes the syntax.
82
83	## LONG DESCRIPTION
84
85	For information about the command-line options for PowerShell 7, see about_Pwsh.
86
87	## Syntax
88
89	Copy
90
91	`PowerShell[.exe]
92	[-PSConsoleFile &lt;file&gt; | -Version &lt;version&gt;]
93	[-NoLogo]
94	[-NoExit]
95	[-Sta]
96	[-Mta]
97	[-NoProfile]
98	[-NonInteractive]
99	[-InputFormat {Text | XML}]
100	[-OutputFormat {Text | XML}]
101	[-WindowStyle &lt;style&gt;]
102	[-EncodedArguments &lt;Base64EncodedArguments&gt;]
103	[-EncodedCommand &lt;Base64EncodedCommand&gt;]
104	[-ConfigurationName &lt;string&gt;]
105	[-File - | &lt;filePath&gt; &lt;args&gt;]
106	[-ExecutionPolicy &lt;ExecutionPolicy&gt;]
107	### -Command
108
109	The value of Command can be `-`, a script block, or a string. If the value of Command is `-`, the command text is read from standard input.
110
111	The Command parameter only accepts a script block for execution when it can recognize the value passed to Command as a ScriptBlock type. This is only possible when running `powershell.exe` from another PowerShell host. The ScriptBlock type may be contained in an existing variable, returned from an expression, or parsed by the PowerShell host as a literal script block enclosed in curly braces (`{}`), before being passed to `powershell.exe`.
112
113	PowerShell
114
115	Copy
116
117	`powershell -Command {Get-WinEvent -LogName Security}
118	`
119
120	In `cmd.exe`, there is no such thing as a script block (or ScriptBlock type), so the value passed to Command is always a string. You can write a script block inside the string, but instead of being executed it behaves exactly as though you typed it at a typical PowerShell prompt, printing the contents of the script block back out to you.
121
122	A string passed to Command is still executed as PowerShell code, so the script block curly braces are often not required in the first place when running from `cmd.exe`. To execute an inline script block defined inside a string, the call operator `&amp;` can be used:
123
124	Windows Command Prompt
125
126	Copy
127
128	`powershell.exe -Command &quot;&amp; {Get-WinEvent -LogName Security}&quot;
129	`
130
131	If the value of Command is a string, Command must be the last parameter for pwsh, because all arguments following it are interpreted as part of the command to execute.
132
133	When called from within an existing PowerShell session, the results are returned to the parent shell as deserialized XML objects, not live objects. For other shells, the results are returned as strings.
134
135	If the value of Command is `-`, the commands are read from standard input. You must redirect standard input when using the Command parameter with standard input. For example:
136
137	PowerShell
138
139	Copy
140
141	`@&#39;
142	&quot;in&quot;
143
144	&quot;hi&quot; |
145	% { &quot;$_ there&quot; }
146
147	&quot;out&quot;
148	### -Sta
149
150	Starts PowerShell using a single-threaded apartment. In Windows PowerShell 2.0, multi-threaded apartment (MTA) is the default. In Windows PowerShell 3.0, single-threaded apartment (STA) is the default.
151
152	### -Version &lt;PowerShell Version&gt;
153
154	Starts the specified version of PowerShell. Valid values are 2.0 and 3.0. The version that you specify must be installed on the system. If Windows PowerShell 3.0 is instal…[truncated]</excerpt>
155	</source>
156	<source kind="search">
157	<title>about_Character_Encoding - PowerShell | Microsoft Learn</title>
158	<location>https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_Character_Encoding</location>
159	<excerpt>citeturn0search1 [wordlim: 200] Crawled: 6 days ago; Creating PowerShell scripts on a Unix-like platform or using a cross-platform editor on Windows, such as Visual Studio Code, results in a file encoded using `UTF8NoBOM`. ... In general, Windows PowerShell uses the Unicode UTF-16LE encoding by default.
160	## Character encoding in Windows PowerShell
161
162	In PowerShell 5.1, the Encoding parameter supports the following values:
163
164	* `Ascii` Uses Ascii (7-bit) character set.
165	* `BigEndianUnicode` Uses UTF-16 with the big-endian byte order.
166	* `BigEndianUTF32` Uses UTF-32 with the big-endian byte order.
167	* `Byte` Encodes a set of characters into a sequence of bytes.
168	* `Default` Uses the encoding that corresponds to the system&#39;s active code page (usually ANSI).
169	* `Oem` Uses the encoding that corresponds to the system&#39;s current OEM code page.
170	* `String` Same as `Unicode`.
171	* `Unicode` Uses UTF-16 with the little-endian byte order.
172	* `Unknown` Same as `Unicode`.
173	* `UTF32` Uses UTF-32 with the little-endian byte order.
174	* `UTF7` Uses UTF-7.
175	* `UTF8` Uses UTF-8 (with BOM).
176
177	In general, Windows PowerShell uses the Unicode UTF-16LE encoding by default. However, the default encoding used by cmdlets in Windows PowerShell is not consistent.
178
179	Note
180
181	Using any Unicode encoding, except `UTF7`, always creates a BOM.
182	</excerpt>
183	</source>
184	<source kind="search">
185	<title>powershell-safety/skills/powershell-safety/references/encoding-guide.md at master · AmethystLuna/powershell-safety · GitHub</title>
186	<location>https://github.com/amethystluna/powershell-safety/blob/master/skills/powershell-safety/references/encoding-guide.md</location>
187	<excerpt>citeturn0search3 [wordlim: 200] Crawled: 4 days ago; Deep reference for file encoding in Windows PowerShell 5.1 and PowerShell 7+. ... # Step 1: Set stdin encoding (data TO native exe)
188
189	# PowerShell File Encoding Guide
190
191	Deep reference for file encoding in Windows PowerShell 5.1 and PowerShell 7+. Load this when writing files that will be read by compilers, git, JSON/XML parsers, or cross-platform tools.
192
193	## Encoding Matrix by Cmdlet
194
195	### Windows PowerShell 5.1
196
197	Cmdlet | Default Encoding | BOM | Notes
198	--- | --- | --- | ---
199	`Out-File` | UTF-16 LE | Yes | `-Encoding utf8` adds UTF-8 BOM
200	`Out-File -Encoding utf8` | UTF-8 | Yes | The `utf8` alias means &quot;UTF-8 with BOM&quot; in PS 5.1
201	`Set-Content` | ANSI (system code page) | No | Chinese Windows: GBK/CP936
202	`Set-Content -Encoding utf8` | UTF-8 | Yes | Same BOM issue
203	`Add-Content` | ANSI (system code page) | No | Inherits from existing file if BOM present
204	`Get-Content` | BOM-detect → ANSI fallback | — | Can misdetect UTF-8 without BOM as ANSI
205	`&gt;` redirect | UTF-16 LE | Yes | Identical to `Out-File` with no `-Encoding`
206	`&gt;&gt;` redirect | UTF-16 LE | Yes | Appends in UTF-16 LE regardless of existing encoding
207	`Start-Process -RedirectStandardOutput` | UTF-16 LE | Yes | Same as `Out-File` — file output, not console
208	`Start-Process -RedirectStandardError` | UTF-16 LE | Yes | Same behavior
209	`ConvertTo-Json` output | Depends on consumer | — | Escapes non-ASCII as `\uXXXX` in PS 5.1; raw UTF-8 in PS 7+
210
211	### PowerShell 7+ (Core)
212
213	Cmdlet | Default Encoding | BOM
214	--- | --- | ---
215	`Out-File` | UTF-8 | No
216	`Set-Content` | UTF-8 | No
217	`Add-Content` | UTF-8 | No
218	`&gt;` / `&gt;&gt;` | UTF-8 | No
219	`Start-Process -RedirectStandardOutput` | UTF-8 | No
220
221	### The `utf8` vs `utf8NoBOM` Trap
222
223	In PS 5.1:
224
225	* `-Encoding utf8` → UTF-8 with BOM (bytes `EF BB BF`)
226	* `-Encoding utf8NoBOM` → does NOT exist in PS 5.1
227	* The only way to get UTF-8 without BOM is the .NET API
228
229	In PS 7+:
230
231	* `-Encoding utf8` → UTF-8 without BOM
232	* `-Encoding utf8BOM` → UTF-8 with BOM (new in PS 7+)
233
234	</excerpt>
235	</source>
236	<source kind="search">
237	<title>about_Character_Encoding - PowerShell | Microsoft Learn</title>
238	<location>https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_character_encoding?view=powershell-7.4</location>
239	<excerpt>citeturn0search4 [wordlim: 200] Crawled: 2 weeks ago; * `bigendianunicode`: Encodes in UTF-16 format using the big-endian byte order. ... Putting this command in your PowerShell profile makes the preference a session-global setting that affects all commands and scripts that do not explicitly specify an encoding.
240	## Character encoding in PowerShell
241
242	In PowerShell (v7.1 and higher), the Encoding parameter supports the following values:
243
244	* `ascii`: Uses the encoding for the ASCII (7-bit) character set.
245	* `ansi`: Uses the encoding for the for the current culture&#39;s ANSI code page. This option was added in PowerShell 7.4.
246	* `bigendianunicode`: Encodes in UTF-16 format using the big-endian byte order.
247	* `bigendianutf32`: Encodes in UTF-32 format using the big-endian byte order.
248	* `oem`: Uses the default encoding for MS-DOS and console programs.
249	* `unicode`: Encodes in UTF-16 format using the little-endian byte order.
250	* `utf7`: Encodes in UTF-7 format.
251	* `utf8`: Encodes in UTF-8 format (no BOM).
252	* `utf8BOM`: Encodes in UTF-8 format with Byte Order Mark (BOM)
253	* `utf8NoBOM`: Encodes in UTF-8 format without Byte Order Mark (BOM)
254	* `utf32`: Encodes in UTF-32 format using the little-endian byte order.
255
256	PowerShell defaults to `utf8NoBOM` for all output.
257
258	Beginning with PowerShell 6.2, the Encoding parameter also allows numeric IDs of registered code pages (like `-Encoding 1251`) or string names of registered code pages (like `-Encoding &quot;windows-1251&quot;`). For more information, see the .NET documentation for Encoding.CodePage.
259
260	Starting with PowerShell 7.4, you can use the `ANSI` value for the Encoding parameter to pass the numeric ID for the current culture&#39;s ANSI code page without having to specify it manually.
261
262	## Changing the default encoding
263
264	PowerShell has two default variables that can be used to change the default encoding behavior.
265
266	* `$PSDefaultParameterValues`
267	* `$OutputEncoding`
268
269	For more information, see about_Preference_Variables.
270
271	Beginning in PowerShell 5.1, the redirection operators (`&gt;` and `&gt;&gt;`) call the `Out-File` cmdlet. Therefore, you can set the default encoding of them using the `$PSDefaultParameterValues` preference variable as shown in this example:
272
273	PowerShell
274
275	Copy
276
277	`$PSDefaultParameterValues[&#39;Out-File:Encoding&#39;] = &#39;utf8&#39;
278	`
279
280	Use the following statement to change the default encoding for all cmdlets that have the Encoding parameter.
281
282	PowerShell
283
284	Copy
285
286	`$PSDefaultParameterValues[&#39;*:Encoding&#39;] = &#39;utf8&#39;
287	`
288
289	Important
290
291	Putting this command in your PowerShell profile makes the preference a session-global setting that affects all commands and scripts that do not explicitly specify an encoding.
292
293	Similarly, you should include such commands in your scripts or modules that you want to behave the same way. Using these commands ensure that cmdlets behave the same way even when run by another user, on a different computer, or in a different version of PowerShell.
294
295	The automatic variable `$OutputEncoding` affects the encoding PowerShell uses to communicate with external programs. It has no effect on the encoding that the output redirection operators and PowerShell cmdlets use to save to files.
296
297	</excerpt>
298	</source>
299	<omitted_sources count="27">Additional source records were omitted from this bounded result.</omitted_sources>
300	</source_evidence>
301
302	Citations:
303
304	- 1: https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_powershell_exe?view=powershell-5.1&utm_source=openai
305	- 2: https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_powershell_exe?view=powershell-5.1&viewFallbackFrom=powershell-Microsoft.PowerShell.Core&utm_source=openai

---

🌐 Web query:

Windows PowerShell 5.1 powershell.exe -Command - piped stdin encoding code page UTF-8

💡 Result:

1	<source_evidence>
2	<source kind="search">
3	<title>about_PowerShell_exe - PowerShell | Microsoft Learn</title>
4	<location>https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_powershell_exe?view=powershell-5.1</location>
5	<excerpt>citeturn0search1 [wordlim: 200] Published: 2.3 years ago; Crawled: 2 days ago; For example, the following command uses the All parameter of the `Get-Script.ps1` script file: `-File . ... For example, if you are in `cmd.exe` and want to pass an environment variable value, you would use the `cmd.exe` syntax: `powershell.exe -File .\test.ps1 -TestParam %windir%` ... A string passed to Command is still executed as PowerShell code, so the script block curly braces are often not required in the first place when running from `cmd.exe`.
6	### -Command
7
8	The value of Command can be `-`, a script block, or a string. If the value of Command is `-`, the command text is read from standard input.
9
10	The Command parameter only accepts a script block for execution when it can recognize the value passed to Command as a ScriptBlock type. This is only possible when running `powershell.exe` from another PowerShell host. The ScriptBlock type may be contained in an existing variable, returned from an expression, or parsed by the PowerShell host as a literal script block enclosed in curly braces (`{}`), before being passed to `powershell.exe`.
11
12	PowerShell
13
14	Copy
15
16	`powershell -Command {Get-WinEvent -LogName Security}
17	`
18
19	In `cmd.exe`, there is no such thing as a script block (or ScriptBlock type), so the value passed to Command is always a string. You can write a script block inside the string, but instead of being executed it behaves exactly as though you typed it at a typical PowerShell prompt, printing the contents of the script block back out to you.
20
21	A string passed to Command is still executed as PowerShell code, so the script block curly braces are often not required in the first place when running from `cmd.exe`. To execute an inline script block defined inside a string, the call operator `&amp;` can be used:
22
23	Windows Command Prompt
24
25	Copy
26
27	`powershell.exe -Command &quot;&amp; {Get-WinEvent -LogName Security}&quot;
28	`
29
30	If the value of Command is a string, Command must be the last parameter for pwsh, because all arguments following it are interpreted as part of the command to execute.
31
32	When called from within an existing PowerShell session, the results are returned to the parent shell as deserialized XML objects, not live objects. For other shells, the results are returned as strings.
33
34	If the value of Command is `-`, the commands are read from standard input. You must redirect standard input when using the Command parameter with standard input. For example:
35
36	PowerShell
37
38	Copy
39
40	`@&#39;
41	&quot;in&quot;
42
43	&quot;hi&quot; |
44	% { &quot;$_ there&quot; }
45
46	&quot;out&quot;
47	</excerpt>
48	</source>
49	<source kind="search">
50	<title>about_Character_Encoding - PowerShell | Microsoft Learn</title>
51	<location>https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_Character_Encoding</location>
52	<excerpt>citeturn0search0 [wordlim: 200] Crawled: 6 days ago; Creating PowerShell scripts on a Unix-like platform or using a cross-platform editor on Windows, such as Visual Studio Code, results in a file encoded using `UTF8NoBOM`. ... Without the BOM, Windows PowerShell misinterprets your script as being encoded in the legacy &quot;ANSI&quot; codepage. ... In PowerShell 5.1, the Encoding parameter supports the following values:
53	## Character encoding in Windows PowerShell
54
55	In PowerShell 5.1, the Encoding parameter supports the following values:
56
57	* `Ascii` Uses Ascii (7-bit) character set.
58	* `BigEndianUnicode` Uses UTF-16 with the big-endian byte order.
59	* `BigEndianUTF32` Uses UTF-32 with the big-endian byte order.
60	* `Byte` Encodes a set of characters into a sequence of bytes.
61	* `Default` Uses the encoding that corresponds to the system&#39;s active code page (usually ANSI).
62	* `Oem` Uses the encoding that corresponds to the system&#39;s current OEM code page.
63	* `String` Same as `Unicode`.
64	* `Unicode` Uses UTF-16 with the little-endian byte order.
65	* `Unknown` Same as `Unicode`.
66	* `UTF32` Uses UTF-32 with the little-endian byte order.
67	* `UTF7` Uses UTF-7.
68	* `UTF8` Uses UTF-8 (with BOM).
69
70	In general, Windows PowerShell uses the Unicode UTF-16LE encoding by default. However, the default encoding used by cmdlets in Windows PowerShell is not consistent.
71
72	Note
73
74	Using any Unicode encoding, except `UTF7`, always creates a BOM.
75	</excerpt>
76	</source>
77	<source kind="search">
78	<title>about_Character_Encoding - PowerShell | Microsoft Learn</title>
79	<location>https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_character_encoding?view=powershell-7.4</location>
80	<excerpt>citeturn0search2 [wordlim: 200] Crawled: 2 weeks ago; Beginning with PowerShell 6.2, the Encoding parameter also allows numeric IDs of registered code pages (like `-Encoding 1251`) or string names of registered code pages (like `-Encoding &quot;windows-1251&quot;`). ... Starting with PowerShell 7.4, you can use the `ANSI` value for the Encoding parameter to pass the numeric ID for the current culture&#39;s ANSI code page without having to specify it manually. ... `$PSDefaultParameterValues[&#39;Out-File:Encoding&#39;] = &#39;utf8&#39; ... Putting this command in your PowerShell profile makes the preference a session-global setting that affects all commands and scripts that do not explicitly specify an encoding.
81	## Character encoding in PowerShell
82
83	In PowerShell (v7.1 and higher), the Encoding parameter supports the following values:
84
85	* `ascii`: Uses the encoding for the ASCII (7-bit) character set.
86	* `ansi`: Uses the encoding for the for the current culture&#39;s ANSI code page. This option was added in PowerShell 7.4.
87	* `bigendianunicode`: Encodes in UTF-16 format using the big-endian byte order.
88	* `bigendianutf32`: Encodes in UTF-32 format using the big-endian byte order.
89	* `oem`: Uses the default encoding for MS-DOS and console programs.
90	* `unicode`: Encodes in UTF-16 format using the little-endian byte order.
91	* `utf7`: Encodes in UTF-7 format.
92	* `utf8`: Encodes in UTF-8 format (no BOM).
93	* `utf8BOM`: Encodes in UTF-8 format with Byte Order Mark (BOM)
94	* `utf8NoBOM`: Encodes in UTF-8 format without Byte Order Mark (BOM)
95	* `utf32`: Encodes in UTF-32 format using the little-endian byte order.
96
97	PowerShell defaults to `utf8NoBOM` for all output.
98
99	Beginning with PowerShell 6.2, the Encoding parameter also allows numeric IDs of registered code pages (like `-Encoding 1251`) or string names of registered code pages (like `-Encoding &quot;windows-1251&quot;`). For more information, see the .NET documentation for Encoding.CodePage.
100
101	Starting with PowerShell 7.4, you can use the `ANSI` value for the Encoding parameter to pass the numeric ID for the current culture&#39;s ANSI code page without having to specify it manually.
102
103	## Changing the default encoding
104
105	PowerShell has two default variables that can be used to change the default encoding behavior.
106
107	* `$PSDefaultParameterValues`
108	* `$OutputEncoding`
109
110	For more information, see about_Preference_Variables.
111
112	Beginning in PowerShell 5.1, the redirection operators (`&gt;` and `&gt;&gt;`) call the `Out-File` cmdlet. Therefore, you can set the default encoding of them using the `$PSDefaultParameterValues` preference variable as shown in this example:
113
114	PowerShell
115
116	Copy
117
118	`$PSDefaultParameterValues[&#39;Out-File:Encoding&#39;] = &#39;utf8&#39;
119	`
120
121	Use the following statement to change the default encoding for all cmdlets that have the Encoding parameter.
122
123	PowerShell
124
125	Copy
126
127	`$PSDefaultParameterValues[&#39;*:Encoding&#39;] = &#39;utf8&#39;
128	`
129
130	Important
131
132	Putting this command in your PowerShell profile makes the preference a session-global setting that affects all commands and scripts that do not explicitly specify an encoding.
133
134	Similarly, you should include such commands in your scripts or modules that you want to behave the same way. Using these commands ensure that cmdlets behave the same way even when run by another user, on a different computer, or in a different version of PowerShell.
135
136	The automatic variable `$OutputEncoding` affects the encoding PowerShell uses to communicate with external programs. It has no effect on the encoding that the output redirection operators and PowerShell cmdlets use to save to files.
137
138	</excerpt>
139	</source>
140	<source kind="search">
141	<title>powershell-safety/skills/powershell-safety/references/encoding-guide.md at master · AmethystLuna/powershell-safety · GitHub</title>
142	<location>https://github.com/amethystluna/powershell-safety/blob/master/skills/powershell-safety/references/encoding-guide.md</location>
143	<excerpt>citeturn0search3 [wordlim: 200] Crawled: 4 days ago; Deep reference for file encoding in Windows PowerShell 5.1 and PowerShell 7+. ... [Console]::OutputEncoding # PS 5.1 default: system code page (CP936 on Chinese Windows) ... # Step 1: Set stdin encoding (data TO native exe) ... [System.IO.File]::WriteAllText(&quot;data.json&quot;, $c, [System.Text.UTF8Encoding]::new($false))
144
145	# PowerShell File Encoding Guide
146
147	Deep reference for file encoding in Windows PowerShell 5.1 and PowerShell 7+. Load this when writing files that will be read by compilers, git, JSON/XML parsers, or cross-platform tools.
148
149	## Encoding Matrix by Cmdlet
150
151	### Windows PowerShell 5.1
152
153	Cmdlet | Default Encoding | BOM | Notes
154	--- | --- | --- | ---
155	`Out-File` | UTF-16 LE | Yes | `-Encoding utf8` adds UTF-8 BOM
156	`Out-File -Encoding utf8` | UTF-8 | Yes | The `utf8` alias means &quot;UTF-8 with BOM&quot; in PS 5.1
157	`Set-Content` | ANSI (system code page) | No | Chinese Windows: GBK/CP936
158	`Set-Content -Encoding utf8` | UTF-8 | Yes | Same BOM issue
159	`Add-Content` | ANSI (system code page) | No | Inherits from existing file if BOM present
160	`Get-Content` | BOM-detect → ANSI fallback | — | Can misdetect UTF-8 without BOM as ANSI
161	`&gt;` redirect | UTF-16 LE | Yes | Identical to `Out-File` with no `-Encoding`
162	`&gt;&gt;` redirect | UTF-16 LE | Yes | Appends in UTF-16 LE regardless of existing encoding
163	`Start-Process -RedirectStandardOutput` | UTF-16 LE | Yes | Same as `Out-File` — file output, not console
164	`Start-Process -RedirectStandardError` | UTF-16 LE | Yes | Same behavior
165	`ConvertTo-Json` output | Depends on consumer | — | Escapes non-ASCII as `\uXXXX` in PS 5.1; raw UTF-8 in PS 7+
166
167	### PowerShell 7+ (Core)
168
169	Cmdlet | Default Encoding | BOM
170	--- | --- | ---
171	`Out-File` | UTF-8 | No
172	`Set-Content` | UTF-8 | No
173	`Add-Content` | UTF-8 | No
174	`&gt;` / `&gt;&gt;` | UTF-8 | No
175	`Start-Process -RedirectStandardOutput` | UTF-8 | No
176
177	### The `utf8` vs `utf8NoBOM` Trap
178
179	In PS 5.1:
180
181	* `-Encoding utf8` → UTF-8 with BOM (bytes `EF BB BF`)
182	* `-Encoding utf8NoBOM` → does NOT exist in PS 5.1
183	* The only way to get UTF-8 without BOM is the .NET API
184
185	In PS 7+:
186
187	* `-Encoding utf8` → UTF-8 without BOM
188	* `-Encoding utf8BOM` → UTF-8 with BOM (new in PS 7+)
189
190	</excerpt>
191	</source>
192	<source kind="search">
193	<title>about_Redirection - PowerShell | Microsoft Learn</title>
194	<location>https://learn.microsoft.com/en-gb/powershell/module/microsoft.powershell.core/about/about_redirection?view=powershell-5.1</location>
195	<excerpt>citeturn0search4 [wordlim: 200] Crawled: 6 days ago; Redirecting the output of a PowerShell command (cmdlet, function, script) using the redirection operator (`&gt;`) is functionally equivalent to piping to `Out-File` with no extra parameters. ... However, stdin isn&#39;t connected to the PowerShell pipeline for input. ... It uses `2&gt;&amp;1` to redirect the Error stream to the Success stream, and `&gt;` to send the resultant Success stream to a file called `dir.log` ... When you are writing to files, the redirection operators use `UTF8NoBOM` encoding.
196	</excerpt>
197	</source>
198	<omitted_sources count="65">Additional source records were omitted from this bounded result.</omitted_sources>
199	</source_evidence>
200
201	Citations:
202
203	- 1: https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_powershell_exe?view=powershell-5.1&utm_source=openai
204	- 2: https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_powershell_exe?view=powershell-5.1&utm_source=openai

---

🌐 Web query:

PowerShell source ConsoleShell stdin encoding -Command - Windows PowerShell 5.1

💡 Result:

1	<source_evidence>
2	<source kind="search">
3	<title>ConsoleShell Class (Microsoft.PowerShell) | Microsoft Learn</title>
4	<location>https://learn.microsoft.com/en-us/dotnet/api/microsoft.powershell.consoleshell?view=powershellsdk-7.6.0</location>
5	<excerpt>citeturn1search1 [wordlim: 200] Crawled: 2 months ago; Microsoft.PowerShell.ConsoleHost.dll ... Start(RunspaceConfiguration, String, String, String[]) | Entry point in to ConsoleShell.
6	</excerpt>
7	</source>
8	<source kind="search">
9	<title>PowerShell-Docs/reference/5.1/Microsoft.PowerShell.Core/About/about_PowerShell_exe.md at main · MicrosoftDocs/PowerShell-Docs · GitHub</title>
10	<location>https://github.com/MicrosoftDocs/PowerShell-Docs/blob/main/reference/5.1/Microsoft.PowerShell.Core/About/about_PowerShell_exe.md</location>
11	<excerpt>citeturn1search3 [wordlim: 200] Published: 2.3 years ago; Crawled: 3 weeks ago; -Command -ConfigurationName -EncodedCommand -ExecutionPolicy -File -Help -InputFormat -Mta -NoExit -NoLogo -NonInteractive -NoProfile -OutputFormat -PSConsoleFile -Sta -Version -WindowStyle ... view=powershell-5.1&amp;WT.mc_id=ps-gethelp ... In contrast, running `powershell.exe -File .\test.ps1 -TestParam $Env:windir` in `cmd.exe` results in the script receiving the literal string `$Env:windir` because it has no special meaning to the current `cmd.exe` shell.The `$Env:windir` style of environment variable reference can be used inside a Command parameter, since there it&#39;s interpreted as PowerShell code. ... # Create a new PowerShell V2 session with text input, XML output, and no logo
12	</excerpt>
13	</source>
14	<source kind="search">
15	<title>ConsoleShell Class (Microsoft.PowerShell) | Microsoft Learn</title>
16	<location>https://learn.microsoft.com/en-us/dotnet/api/microsoft.powershell.consoleshell?view=powershellsdk-7.6.0</location>
17	<excerpt>citeturn2search0 [wordlim: 200] Crawled: 2 months ago; Microsoft.PowerShell.ConsoleHost.dll ... Start(InitialSessionState, String, String, String[]) | Entry point in to ConsoleShell.
18
19	Note
20
21	Access to this page requires authorization. You can try signing in or changing directories.
22
23	Access to this page requires authorization. You can try changing directories.
24
25	# ConsoleShell Class
26
27
28	## Definition
29
30	Namespace:
31	Microsoft.PowerShell
32
33	Assembly:
34	Microsoft.PowerShell.ConsoleHost.dll
35
36	Package:
37	Microsoft.PowerShell.5.1.ReferenceAssemblies v1.0.0
38
39	Package:
40	Microsoft.PowerShell.ConsoleHost v7.4.15
41
42
43	Important
44
45	Some information relates to prerelease product that may be substantially modified before it’s released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
46
47	This class provides an entry point which is called to transfer control to console host implementation.
48
49	`public ref class ConsoleShell abstract sealed`
50
51	`public ref class ConsoleShell abstract sealed`
52
53	`class ConsoleShell abstract sealed`
54
55	`public static class ConsoleShell`
56
57
58	`Public Class ConsoleShell`
59
60	Inheritance
61
62
63	Object
64
65	ConsoleShell
66
67
68	## Methods
69
70	Expand table
71
72	Name | Description
73	--- | ---
74	Start(InitialSessionState, String, String, String[]) | Entry point in to ConsoleShell. Used to create a custom Powershell console application.
75	Start(RunspaceConfiguration, String, String, String[]) | Entry point in to ConsoleShell. This method is called by main of minishell.
76	Start(String, String, String[]) | Entry point in to ConsoleShell. This method is called by main of minishell.
77
78	## Applies to
79
80	## In this article
81
82	1. Definition
83	2. Methods
84	3. Applies to</excerpt>
85	</source>
86	<source kind="search">
87	<title>GitHub - PowerShell/PowerShell: PowerShell for every system! · GitHub</title>
88	<location>https://github.com/PowerShell/PowerShell</location>
89	<excerpt>citeturn2search6 [wordlim: 200] Crawled: last month; Windows PowerShell specific issues should be reported with the Feedback Hub app, by choosing &quot;Apps &gt; PowerShell&quot; in the category. ... GitHub Discussions is a feature to enable free and open discussions within the community for topics that are not related to code, unlike issues. ... ## Downloading the Source Code ... License: By requesting and using the Container OS Image for Windows containers, you acknowledge, understand, and consent to the Supplemental License Terms available on Microsoft Artifact Registry.
90
91	# PowerShell
92
93	Welcome to the PowerShell GitHub Community! PowerShell is a cross-platform (Windows, Linux, and macOS) automation and configuration tool/framework that works well with your existing tools and is optimized for dealing with structured data (e.g. JSON, CSV, XML, etc.), REST APIs, and object models. It includes a command-line shell, an associated scripting language, and a framework for processing cmdlets.
94
95	## Windows PowerShell vs. PowerShell 7+
96
97	Although this repository started as a fork of the Windows PowerShell codebase, changes made in this repository are not ported back to Windows PowerShell 5.1. This also means that issues tracked here are only for PowerShell 7.x and higher. Windows PowerShell specific issues should be reported with the Feedback Hub app, by choosing &quot;Apps &gt; PowerShell&quot; in the category.
98
99	## New to PowerShell?
100
101	If you are new to PowerShell and want to learn more, we recommend reviewing the getting started documentation.
102	</excerpt>
103	</source>
104	<source kind="search">
105	<title>about_Character_Encoding - PowerShell | Microsoft Learn</title>
106	<location>https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_character_encoding?view=powershell-7</location>
107	<excerpt>citeturn0search0 [wordlim: 200] Crawled: 4 days ago; In PowerShell 5.1, the Encoding parameter supports the following values: ... In general, Windows PowerShell uses the Unicode UTF-16LE encoding by default. ... ANSI is also what the PowerShell engine uses when it reads source code from files.
108	## Character encoding in Windows PowerShell
109
110	In PowerShell 5.1, the Encoding parameter supports the following values:
111
112	* `Ascii` Uses Ascii (7-bit) character set.
113	* `BigEndianUnicode` Uses UTF-16 with the big-endian byte order.
114	* `BigEndianUTF32` Uses UTF-32 with the big-endian byte order.
115	* `Byte` Encodes a set of characters into a sequence of bytes.
116	* `Default` Uses the encoding that corresponds to the system&#39;s active code page (usually ANSI).
117	* `Oem` Uses the encoding that corresponds to the system&#39;s current OEM code page.
118	* `String` Same as `Unicode`.
119	* `Unicode` Uses UTF-16 with the little-endian byte order.
120	* `Unknown` Same as `Unicode`.
121	* `UTF32` Uses UTF-32 with the little-endian byte order.
122	* `UTF7` Uses UTF-7.
123	* `UTF8` Uses UTF-8 (with BOM).
124
125	In general, Windows PowerShell uses the Unicode UTF-16LE encoding by default. However, the default encoding used by cmdlets in Windows PowerShell is not consistent.
126
127	Note
128
129	Using any Unicode encoding, except `UTF7`, always creates a BOM.
130	</excerpt>
131	</source>
132	<omitted_sources count="68">Additional source records were omitted from this bounded result.</omitted_sources>
133	</source_evidence>
134
135	Citations:
136
137	- 1: https://github.com/PowerShell/PowerShell?utm_source=openai
138	- 2: https://github.com/MicrosoftDocs/PowerShell-Docs/blob/main/reference/5.1/Microsoft.PowerShell.Core/About/about_PowerShell_exe.md?utm_source=openai
139	- 3: https://learn.microsoft.com/en-us/dotnet/api/microsoft.powershell.consoleshell?view=powershellsdk-7.6.0&utm_source=openai

---

🌐 Web query:

official .NET Console.InputEncoding default redirected standard input code page Windows

💡 Result:

1	<source_evidence>
2	<source kind="open_page">
3	<title>referencesource/mscorlib/system/console.cs at main · microsoft/referencesource · GitHub</title>
4	<location>https://github.com/Microsoft/referencesource/blob/main/mscorlib/system/console.cs</location>
5	<excerpt>citeturn1view0 [wordlim: 200] Crawled: yesterday; Content type: text/html; Source: open({&quot;ref_id&quot;:&quot;turn0search10&quot;,&quot;lineno&quot;:null}); Total lines: 3791
6	L2626: // Set up Console.In
7	L2627:
8	L2628: Stream s = OpenStandardInput(DefaultConsoleBufferSize);
9	L2629:
10	L2630: TextReader tr;
11	L2631:
12	L2632: if (s == Stream.Null)
13	L2633:
14	L2634: tr = StreamReader.Null;
15	L2635:
16	L2636: else {
17	L2637:
18	L2638: // Hopefully Encoding.GetEncoding doesn&#39;t load as many classes now.
19	L2639: #if FEATURE_CORECLR
20	L2640:
21	L2641: Encoding enc = Encoding.UTF8;
22	L2642:
23	L2643: #else // FEATURE_CORECLR
24	L2644:
25	L2645: Encoding enc = InputEncoding;
26	L2646: #endif // FEATURE_CORECLR
27	L2647:
28	L2648: tr = TextReader.Synchronized(new StreamReader(s, enc, false, DefaultConsoleBufferSize, true));
29	L2649:
30	L2650: }
31	L2651:
32	L2652: System.Threading.Thread.MemoryBarrier();
33	L2653:
34	L2654: _in = tr;
35	L2655:
36	L2656: }
37	L2657:
38	L2658: }
39	L2659:
40	L2660: }
41	L2661:
42	L2662: return _in;
43	L2663:
44	L2664: }
45	L2665:
46	L2666: }
47	L2667:
48	L2668: public static TextWriter Out {
49	L2669:
50	L2670: [HostProtection(UI=true)]
51	L2671:
52	L2672: [ResourceExposure(ResourceScope.None)]
53	L2673:
54	L2674: [ResourceConsumption(ResourceScope.Process, ResourceScope.Process)]
55	L2675:
56	L2676: get {
57	L2677:
58	L2678: Contract.Ensures(Contract.Result&lt;TextWriter&gt;() != null);
59	L2679:
60	L2680: // Hopefully this is inlineable.
61	L2681:
62	L2682: if (_out == null)
63	L2683: InitializeStdOutError(true);
64	L2684:
65	L2685: return _out;
66	L2686:
67	L2687: }
68	L2688:
69	L2689: }
70	L2690:
71	L2691: public static TextWriter Error {
72	L2692:
73	L2693: [HostProtection(UI=true)]
74	L2694:
75	L2695: get {
76	L2696:
77	L2697: Contract.Ensures(Contract.Result&lt;TextWriter&gt;() != null);
78	L2698:
79	L2699: // Hopefully this is inlineable.
80	L2700:
81	L2701: if (_error == null)
82	L2702:
83	L2703: InitializeStdOutError(false);
84	L2704:
85	L2705: return _error;
86	L2706:
87	L2707: }
88	L2708:
89	L2709: }
90	L2710:
91	L2711: // For console apps, the console handles are set to values like 3, 7,
92	L2712:
93	L2713: // and 11 OR if you&#39;ve been created via CreateProcess, possibly -1
94	L2714:
95	L2715: // or 0. -1 is definitely invalid, while 0 is probably invalid.
96	L2716: // Also note each handle can independently be invalid or good.
97	L2717:
98	L2718: // For Windows apps, the console handles are set to values like 3, 7,
99	L2719:
100	L2720: // and 11 but are invalid handles - you may not write to them. However,
101	L2721:
102	L2722: // you can still spawn a Windows app via CreateProcess and read stdout
103	L2723:
104	L2724: // and stderr.
105	L2725:
106	L2726: // So, we always need to check each handle independently for validity
107	L2727:
108	L2728: // by trying to write or read to it, unless it is -1.
109	L2729:
110	L2730: // We do not do a security check here, under the assumption that this
111	L2731: // cannot create a security hole, but only waste a user&#39;s time or
112	L2732:
113	L2733: // cause a possible denial of service attack.
114	L2734:
115	L2735: [System.Security.SecuritySafeCritical] // auto-generated
116	L2736:
117	L2737: [ResourceExposure(ResourceScope.None)]
118	L2738:
119	L2739: [ResourceConsumption(ResourceScope.Process, ResourceScope.Process)]
120	L2740:
121	L2741: private static void InitializeStdOutError(bool stdout)
122	L2742:
123	L2743: {
124	L2744:
125	L2745: // Set up Console.Out or Console.Error.
126	L2746:
127	L2747: lock(InternalSyncObject) {
128	L2748:
129	L2749: if (stdout &amp;&amp; _out != null)
130	L2750:
131	L2751: return;
132	L2752:
133	L2753: else if (!stdout &amp;&amp; _error != null)
134	L2754:
135	L2755: return;
136	L2756: TextWriter writer = null;
137	L2757:
138	L2758: Stream s;
139	L2759:
140	L2760: if (stdout)
141	L2761:
142	L2762: s = OpenStandardOutput(DefaultConsoleBufferSize);
143	L2763:
144	L2764: else
145	L2765:
146	L2766: s = OpenStandardError(DefaultConsoleBufferSize);
147	L2767:
148	L2768: if (s == Stream.Null) {
149	L2923: private static bool GetUseFileAPIs(int handleType) {
150	L2924:
151	L2925: switch(handleType) {
152	L2926:
153	L2927: case Win32Native.STD_INPUT_HANDLE:
154	L2928:
155	L2929: return !IsStandardConsoleUnicodeEncoding(InputEncoding) || IsInputRedirected;
156	L2930:
157	L2931: case Win32Native.STD_OUTPUT_HANDLE:
158	L29…[truncated]</excerpt>
159	</source>
160	<source kind="open_page">
161	<title>Console.InputEncoding Property (System) | Microsoft Learn</title>
162	<location>https://learn.microsoft.com/en-us/dotnet/api/system.console.inputencoding</location>
163	<excerpt>citeturn1view1 [wordlim: 200] Crawled: 2 days ago; Content type: text/html; Source: open({&quot;ref_id&quot;:&quot;turn0search0&quot;,&quot;lineno&quot;:null}); Redirected to URL: https://learn.microsoft.com/en-us/dotnet/api/system.console.inputencoding?view=net-10.0; Total lines: 164
164	L85: [&lt;System.Runtime.Versioning.UnsupportedOSPlatform(&quot;tvos&quot;)&gt;]
165	L86: static member InputEncoding : System.Text.Encoding with get, set`
166	L87:
167	L88: `[&lt;System.Runtime.Versioning.UnsupportedOSPlatform(&quot;browser&quot;)&gt;]
168	L89: static member InputEncoding : System.Text.Encoding with get, set`
169	L90:
170	L91: `static member InputEncoding : System.Text.Encoding with get, set`
171	L92:
172	L93: `Public Shared Property InputEncoding As Encoding`
173	L94: #### Property Value
174	L95:
175	L96: 【11†Encoding】
176	L97:
177	L98: The encoding used to read console input.
178	L99:
179	L100: Attributes
180	L101:
181	L102:
182	L103: 【12†UnsupportedOSPlatformAttribute】
183	L104:
184	L105: #### Exceptions
185	L106:
186	L107: 【13†ArgumentNullException】
187	L108:
188	L109: The property value in a set operation is `null`.
189	L110:
190	L111: 【14†IOException】
191	L112:
192	L113: An error occurred during the execution of this operation.
193	L114:
194	L115: 【15†SecurityException】
195	L116:
196	L117: Your application does not have permission to perform this operation.
197	L118: ## Remarks
198	L119:
199	L120: The console uses the input encoding to translate keyboard input into a corresponding character. The input encoding incorporates a code page that maps 256 keyboard character codes to individual characters. Different code pages include different special characters, typically customized for a language or a group of languages.
200	L121: Starting with the .NET Framework 4, a property get operation may return a cached value instead of the console&#39;s current input encoding. This can occur if the value of the 【16†InputEncoding】 property is modified by some means other than an assignment to the 【16†InputEncoding】 property, such as calling the Windows `SetConsoleCP` function or using the `chcp` command from a PowerShell script.
201	L122: ## Applies to
202	L123:
203	L124: ## See also
204	L125:
205	L126: * 【11†Encoding】
206	L127:
207	L128: Collaborate with us on GitHub
208	L129:
209	L130: The source for this content can be found on GitHub, where you can also create and review issues and pull requests. For more information, see 【17†our contributor guide】.
210	L131:
211	L132: 【18†Image】 【18†Image】
212	L133:
213	L134: .NET
214	L135:
215	L136: 【2†Open a documentation issue】 【19†Provide product feedback†aka.ms】
216	L137:
217	L138: * * *
218	L139: ## Feedback
219	L140:
220	L141: Was this page helpful?
221	L142:
222	L143: Yes No No
223	L144:
224	L145: Need help with this topic?
225	L146:
226	L147: Want to try using Ask Learn to clarify or guide you through this topic?
227	L148:
228	L149: Ask Learn Ask Learn
229	L150:
230	L151: Suggest a fix?
231	L152:
232	L153: ### In this article
233	L154:
234	L155: Was this page helpful?
235	L156:
236	L157: Need help with this topic?
237	L158:
238	L159: Want to try using Ask Learn to clarify or guide you through this topic?
239	L160:
240	L161: Ask Learn Ask Learn
241	L162:
242	L163: Suggest a fix?
243	</excerpt>
244	</source>
245	<source kind="search">
246	<title>Console Class (System) | Microsoft Learn</title>
247	<location>https://learn.microsoft.com/en-us/dotnet/api/system.console?view=netcore-3.1</location>
248	<excerpt>citeturn0search2 [wordlim: 200] Crawled: last week; By default, the value of the In property is a System.IO.TextReader object that represents the keyboard, and the values of the Out and Error properties are System.IO.TextWriter objects that represent a console window. ... To redirect the standard input, standard output, or standard error stream, call the Console.SetIn, Console.SetOut, or Console.SetError method, respectively. ... You can also use the IsOutputRedirected, IsInputRedirected, and IsErrorRedirected properties to determine whether a standard stream is redirected before performing an operation that throws an System.IO.IOException exception. ... NET makes only a limited subset of code page encodings available, Encoding.UTF8 is used as the default encoding for the console.
249	These streams are presented to your application as the values of the Console.In, Console.Out, and Console.Error properties.
250
251	By default, the value of the In property is a System.IO.TextReader object that represents the keyboard, and the values of the Out and Error properties are System.IO.TextWriter objects that represent a console window. However, you can set these properties to streams that do not represent the console window or keyboard; for example, you can set these properties to streams that represent files. To redirect the standard input, standard output, or standard error stream, call the Console.SetIn, Console.SetOut, or Console.SetError method, respectively. I/O operations that use these streams are synchronized, which means that multiple threads can read from, or write to, the streams. This means that methods that are ordinarily asynchronous, such as TextReader.ReadLineAsync, execute synchronously if the object represents a console stream.
252
253	Note
254
255	Do not use the Console class to display output in unattended applications, such as server applications. Calls to methods such as Console.Write and Console.WriteLine have no effect in GUI applications.
256
257	Console class members that work normally when the underlying stream is directed to a console might throw an exception if the stream is redirected, for example, to a file. Program your application to catch System.IO.IOException exceptions if you redirect a standard stream. You can also use the IsOutputRedirected, IsInputRedirected, and IsErrorRedirected properties to determine whether a standard stream is redirected before performing an operation that throws an System.IO.IOException exception.
258
259	It is sometimes useful to explicitly call the members of the stream objects represented by the In, Out, and Error properties. For example, by default, the Console.ReadLine method reads input from the standard input stream. Similarly, the Console.WriteLine method writes data to the standard output stream, and the data is followed by the default line termination string, which can be found at Environment.NewLine. However, the Console class does not provide a corresponding method to write data to the standard error output stream, or a property to change the line termination string for data written to that stream.
260
261	You can solve this problem by setting the TextWriter.NewLine property of the Out or Error property to another line termination string. For example, the following C# statement sets the line termination string for the standard error output stream to two carriage return and line feed sequences:
262
263	`Console.Error.NewLine = &quot;\r\n\r\n&quot;;`
264
265	You can then explicitly call the WriteLine method of the error output stream object, as in the following C# statement:
266
267	`Console.Error.WriteLine();`
268
269
270	* Get or set the foreground and background colors by using the ForegroundColor and BackgroundColor properties, or reset the background and foreground to their default colors by calling the ResetColor method.
271
272	* Play the sound of a beep through the console speaker by calling the Beep method.
273
274	### Default encodings
275
276	In cases where .NET makes only a limited subset of code page encodings available, Encodi…[truncated]</excerpt>
277	</source>
278	<source kind="search">
279	<title>referencesource/mscorlib/system/console.cs at main · microsoft/referencesource · GitHub</title>
280	<location>https://github.com/Microsoft/referencesource/blob/main/mscorlib/system/console.cs</location>
281	<excerpt>citeturn0search10 [wordlim: 200] Crawled: 2 weeks ago; Stream s = OpenStandardInput(DefaultConsoleBufferSize); ... IsStandardConsoleUnicodeEncoding(InputEncoding) || IsInputRedirected; ... new UIPermission(UIPermissionWindow.SafeTopLevelWindows). ... // _out reinitialize the console code page.
282	#endif // FEATURE_CODEPAGES_FILE
283
284	} // public static Encoding InputEncoding
285
286	public static Encoding OutputEncoding {
287
288	[System.Security.SecuritySafeCritical] // auto-generated
289
290	get {
291
292	Contract.Ensures(Contract.Result&lt;Encoding&gt;() != null);
293
294	if (null != _outputEncoding)
295
296	return _outputEncoding;
297
298	lock(InternalSyncObject) {
299
300	if (null != _outputEncoding)
301
302	return _outputEncoding;
303
304	uint cp = Win32Native.GetConsoleOutputCP();
305
306	_outputEncoding = Encoding.GetEncoding((int) cp);
307
308	return _outputEncoding;
309
310	}
311
312	}
313
314	#if FEATURE_CODEPAGES_FILE // if no codepages file then locked into default
315
316	[System.Security.SecuritySafeCritical] // auto-generated
317
318	[ResourceExposure(ResourceScope.Process)]
319
320	[ResourceConsumption(ResourceScope.Process)]
321
322	set {
323
324	if (value == null)
325
326	throw new ArgumentNullException(&quot;value&quot;);
327
328	Contract.EndContractBlock();
329
330	new UIPermission(UIPermissionWindow.SafeTopLevelWindows).Demand();
331
332	lock(InternalSyncObject) {
333
334	// Before changing the code page we need to flush the data
335
336	// if Out hasn&#39;t been redirected. Also, have the next call to
337	</excerpt>
338	</source>
339	<source kind="search">
340	<title>Console.InputEncoding Property (System) | Microsoft Learn</title>
341	<location>https://learn.microsoft.com/en-us/dotnet/api/system.console.inputencoding</location>
342	<excerpt>citeturn0search0 [wordlim: 200] Crawled: 4 weeks ago; The input encoding incorporates a code page that maps 256 keyboard character codes to individual characters. ... This can occur if the value of the InputEncoding property is modified by some means other than an assignment to the InputEncoding property, such as calling the Windows `SetConsoleCP` function or using the `chcp` command from a PowerShell script.
343
344	# Console.InputEncoding Property
345
346	## In this article
347
348	1. Definition
349	2. Remarks
350	3. Applies to
351	4. See also
352
353	## Definition
354
355	Namespace:
356	System
357
358	Assemblies:
359	netstandard.dll, System.Console.dll
360
361	Assembly:
362	System.Console.dll
363
364	Assembly:
365	mscorlib.dll
366
367	Assembly:
368	netstandard.dll
369
370	Source:
371	Console.cs
372
373	Source:
374	Console.cs
375
376	Source:
377	Console.cs
378
379	Source:
380	Console.cs
381
382	Source:
383	Console.cs
384
385	Important
386
387	Some information relates to prerelease product that may be substantially modified before it’s released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
388
389	Gets or sets the encoding the console uses to read input.
390
391	`public:
392	static property System::Text::Encoding ^ InputEncoding { System::Text::Encoding ^ get(); void set(System::Text::Encoding ^ value); };`
393
394	`[System.Runtime.Versioning.UnsupportedOSPlatform(&quot;android&quot;)]
395	[System.Runtime.Versioning.UnsupportedOSPlatform(&quot;browser&quot;)]
396	[System.Runtime.Versioning.UnsupportedOSPlatform(&quot;ios&quot;)]
397	[System.Runtime.Versioning.UnsupportedOSPlatform(&quot;tvos&quot;)]
398	public static System.Text.Encoding InputEncoding { get; set; }`
399
400	`[System.Runtime.Versioning.UnsupportedOSPlatform(&quot;browser&quot;)]
401	public static System.Text.Encoding InputEncoding { get; set; }`
402
403	C#
404
405	Copy
406
407	`public static System.Text.Encoding InputEncoding { get; set; }`
408
409	`[&lt;System.Runtime.Versioning.UnsupportedOSPlatform(&quot;android&quot;)&gt;]
410	[&lt;System.Runtime.Versioning.UnsupportedOSPlatform(&quot;browser&quot;)&gt;]
411	[&lt;System.Runtime.Versioning.UnsupportedOSPlatform(&quot;ios&quot;)&gt;]
412	[&lt;System.Runtime.Versioning.UnsupportedOSPlatform(&quot;tvos&quot;)&gt;]
413	static member InputEncoding : System.Text.Encoding with get, set`
414
415	`[&lt;System.Runtime.Versioning.UnsupportedOSPlatform(&quot;browser&quot;)&gt;]
416	static member InputEncoding : System.Text.Encoding with get, set`
417
418	`static member InputEncoding : System.Text.Encoding with get, set`
419
420	`Public Shared Property InputEncoding As Encoding`
421
422	#### Property Value
423
424	Encoding
425
426	The encoding used to read console input.
427
428	Attributes
429
430
431	UnsupportedOSPlatformAttribute
432
433	#### Exceptions
434
435	ArgumentNullException
436
437	The property value in a set operation is `null`.
438
439	IOException
440
441	An error occurred during the execution of this operation.
442
443	SecurityException
444
445	Your application does not have permission to perform this operation.
446
447	## Remarks
448
449	The console uses the input encoding to translate keyboard input into a corresponding character. The input encoding incorporates a code page that maps 256 keyboard character codes to individual characters. Different code pages include different special characters, typically customized for a language or a group of languages.
450
451	Starting with the .NET Framework 4, a property get operation may return a cached value instead of the console&#39;s current input encoding. This can occur if the value of the InputEncoding property is modified by some means other than an assignment to the InputEncoding property, such as calling the Windows `SetConsoleCP` function or using the `chcp` command from a PowerShell script.
452
453	## Applies to
454
455	Product | Versions
456	--- | ---
457	.NET | Core 1.0, Core 1.1, Core 2.0, Core 2.1, Core 2.2, Core 3.0, Core 3.1, 5, 6, 7, 8, 9, 10, 11
458	.NET Framework | 2.0, 3.0, 3.5, 4.0, 4.5, 4.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2, 4.8, 4.8.1
459	.NET Standard | 1.3, 1.4, 1.6, 2.0, 2.1
460
461	## See also
462
463	* Encoding</excerpt>
464	</source>
465	<omitted_sources count="9">Additional source records were omitted from this bounded result.</omitted_sources>
466	</source_evidence>
467
468	Citations:
469
470	- 1: https://github.com/Microsoft/referencesource/blob/main/mscorlib/system/console.cs
471	- 2: https://learn.microsoft.com/en-us/dotnet/api/system.console?view=netcore-3.1&utm_source=openai
472	- 3: https://github.com/Microsoft/referencesource/blob/main/mscorlib/system/console.cs

---

🌐 Web query:

official Node.js child_process spawnSync input string encoding stdin documentation

💡 Result:

1	<source_evidence>
2	<source kind="search">
3	<title>Child process | Node.js v26.12.1 Documentation</title>
4	<location>https://nodejs.org/api/child_process.html</location>
5	<excerpt>citeturn0search0 [wordlim: 200] Crawled: 3 days ago; The `child_process.spawnSync()`, `child_process.execSync()`, and `child_process.execFileSync()` methods are synchronous and will block the Node.js event loop, pausing execution of any additional code until the spawned process exits. ... * `input` `&lt;string&gt;` | `&lt;Buffer&gt;` | `&lt;TypedArray&gt;` | `&lt;DataView&gt;` The value which will be passed as stdin to the spawned process. ... * `encoding` `&lt;string&gt;` The encoding used for all stdio inputs and outputs.
6	### Synchronous process creation#
7
8	The `child_process.spawnSync()`, `child_process.execSync()`, and `child_process.execFileSync()` methods are synchronous and will block the Node.js event loop, pausing execution of any additional code until the spawned process exits.
9
10	Blocking calls like these are mostly useful for simplifying general-purpose scripting tasks and for simplifying the loading/processing of application configuration at startup.
11
12	#### `child_process.execFileSync(file[, args][, options])`#
13
14	Added in: v0.11.12 History
15	Version | Changes
16	--- | ---
17	v16.4.0, v14.18.0 | The `cwd` option can be a WHATWG `URL` object using `file:` protocol.
18	v10.10.0 | The `input` option can now be any `TypedArray` or a `DataView`.
19	v8.8.0 | The `windowsHide` option is supported now.
20	v8.0.0 | The `input` option can now be a `Uint8Array`.
21	v6.2.1, v4.5.0 | The `encoding` option can now explicitly be set to `buffer`.
22
23	* `file` `&lt;string&gt;` The name or path of the executable file to run.
24	Default: `&#39;SIGTERM&#39;`.
25	* `maxBuffer` `&lt;number&gt;` Largest amount of data in bytes allowed on stdout or stderr. If exceeded, the child process is terminated and any output is truncated. See caveat at `maxBuffer` and Unicode. Default: `1024 * 1024`.
26	* `encoding` `&lt;string&gt;` The encoding used for all stdio inputs and outputs. Default: `&#39;buffer&#39;`.
27	* `windowsHide` `&lt;boolean&gt;` Hide the subprocess console window that would normally be created on Windows systems. Default: `false`.
28	* Returns: `&lt;Buffer&gt;` | `&lt;string&gt;` | `&lt;null&gt;` If `stdio` is `&#39;pipe&#39;`, the stdout from the command, otherwise null.
29
30	The `child_process.execSync()` method is generally identical to `child_process.exec()` with the exception that the method will not return until the child process has fully closed. When a timeout has been encountered and `killSignal` is sent, the method won&#39;t return until the process has completely exited. If the child process intercepts and handles the `SIGTERM` signal and doesn&#39;t exit, the parent process will wait until the child process has exited.
31
32	If the process times out or has a non-zero exit code, this method will throw. The `Error` object will contain the entire result from `child_process.spawnSync()`.
33
34	Never pass unsanitized user input to this function. Any input containing shell metacharacters may be used to trigger arbitrary command execution.
35
36	#### `child_process.spawnSync(command[, args][, options])`#
37
38	Added in: v0.11.12 History
39	Version | Changes
40	--- | ---
41	v16.4.0, v14.18.0 | The `cwd` option can be a WHATWG `URL` object using `file:` protocol.
42	v10.10.0 | The `input` option can now be any `TypedArray` or a `DataView`.
43	v8.8.0 | The `windowsHide` option is supported now.
44	v8.0.0 | The `input` option can now be a `Uint8Array`.
45	v6.2.1, v4.5.0 | The `encoding` option can now explicitly be set to `buffer`.
46	v5.7.0 | The `shell` option is supported now.
47
48	* `command` `&lt;string&gt;` The command to run.
49	* `args` `&lt;string&gt;`[] List of string arguments.
50	* `options` `&lt;Object&gt;`
51	* `cwd` `&lt;string&gt;` | `&lt;URL&gt;` Current working directory of the child process.
52	* `input` `&lt;string&gt;` | `&lt;Buffer&gt;` | `&lt;TypedArray&gt;` | `&lt;DataView&gt;` The value which will be passed as stdin to the spawned process. </excerpt>
53	</source>
54	<source kind="search">
55	<title>node/doc/api/child_process.md at main · nodejs/node · GitHub</title>
56	<location>https://github.com/nodejs/node/blob/main/doc/api/child_process.md</location>
57	<excerpt>citeturn0search1 [wordlim: 200] Crawled: today; For convenience, the `node:child_process` module provides a handful of synchronous and asynchronous alternatives to `child_process.spawn()` and `child_process.spawnSync()`. ... The `encoding` option can be used to specify the character encoding used to decode the stdout and stderr output. ... The stream passed in the `stdin` position is the source from which the child process reads its input, and the streams in the `stdout`/`stderr` positions receive the output the child writes.
58	## Synchronous process creation
59
60	The `child_process.spawnSync()`, `child_process.execSync()`, and `child_process.execFileSync()` methods are synchronous and will block the Node.js event loop, pausing execution of any additional code until the spawned process exits.
61
62	Blocking calls like these are mostly useful for simplifying general-purpose scripting tasks and for simplifying the loading/processing of application configuration at startup.
63
64
65	### `child_process.execFileSync(file[, args][, options])`
66
67	* `file` {string} The name or path of the executable file to run.
68	* `args` {string[]} List of string arguments.
69	* `options` {Object}
70	* `cwd` {string|URL} Current working directory of the child process.
71	* `input` {string|Buffer|TypedArray|DataView} The value which will be passed as stdin to the spawned process. If `stdio[0]` is set to `&#39;pipe&#39;`, Supplying this value will override `stdio[0]`.
72	* `stdio` {string|Array} Child&#39;s stdio configuration. See `child_process.spawn()`&#39;s `stdio`. `stderr` by default will be output to the parent process&#39; stderr unless `stdio` is specified. Default: `&#39;pipe&#39;`.
73	* `env` {Object} Environment key-value pairs. Default: `process.env`.
74	* `uid` {number} Sets the user identity of the process (see setuid(2)).
75	* `gid` {number} Sets the group identity of the process (see setgid(2)).
76	* `timeout` {number} In milliseconds the maximum amount of time the process is allowed to run. Default: `undefined`.
77	* `killSignal` {string|integer} The signal value to be used when the spawned process will be killed. Default: `&#39;SIGTERM&#39;`.
78	* `maxBuffer` {number} Largest amount of data in bytes allowed on stdout or stderr. If exceeded, the child process is terminated. See caveat at `maxBuffer` and Unicode. Default: `1024 * 1024`.
79	* `encoding` {string} The encoding used for all stdio inputs and outputs. Default: `&#39;buffer&#39;`.
80	* `windowsHide` {boolean} Hide the subprocess console window that would normally be created on Windows systems. Default: `false`.
81	* `shell` {boolean|string} If `true`, runs `command` inside of a shell. Uses `&#39;/bin/sh&#39;` on Unix, and `process.env.ComSpec` on Windows. * `timeout` {number} In milliseconds the maximum amount of time the process is allowed to run. Default: `undefined`.
82	* `killSignal` {string|integer} The signal value to be used when the spawned process will be killed. Default: `&#39;SIGTERM&#39;`.
83	* `maxBuffer` {number} Largest amount of data in bytes allowed on stdout or stderr. If exceeded, the child process is terminated and any output is truncated. See caveat at `maxBuffer` and Unicode. Default: `1024 * 1024`.
84	* `encoding` {string} The encoding used for all stdio inputs and outputs. Default: `&#39;buffer&#39;`.
85	* `windowsHide` {boolean} Hide the subprocess console window that would normally be created on Windows systems. Default: `false`.
86	* Returns: {Buffer|string|null} If `stdio` is `&#39;pipe&#39;`, the stdout from the command, otherwise null.

1	Learnt from: CR
2	Repo: pingdotgg/t3code PR: 0
3	File: CONTRIBUTING.md:0-0
4	Timestamp: 2026-10-14T08:05:39.195Z
5	Learning: Applicability reference:
6	AGENTS.md: # T3 Code
7	## Pull requests
8	- One request is one PR. Split it only when the maintainer asks. Outside contributions follow the stricter [one problem per PR](CONTRIBUTING.md#one-problem) rule.
9
10	AGENTS.md: # T3 Code
11	## Plans and work artifacts
12	- Track active maintainer work in the GitHub issue or project item that owns it. External proposals follow `CONTRIBUTING.md` and belong in Ideas discussions.
13
14	Source excerpt:
15	# Contributing
16
17	## Provide evidence for the changed behavior
18
19	Explain how you established the problem, how you checked the change, and what you observed. Give the
20	relevant reproduction steps, environment, focused test commands or manual checks, and their results.
21	State what you could not check. A checkbox or "tests pass" alone does not show that the change works.

1	Learnt from: CR
2	Repo: pingdotgg/t3code PR: 0
3	File: CONTRIBUTING.md:0-0
4	Timestamp: 2026-10-14T08:05:39.195Z
5	Learning: Applicability reference:
6	AGENTS.md: # T3 Code
7	## Pull requests
8	- One request is one PR. Split it only when the maintainer asks. Outside contributions follow the stricter [one problem per PR](CONTRIBUTING.md#one-problem) rule.
9
10	AGENTS.md: # T3 Code
11	## Plans and work artifacts
12	- Track active maintainer work in the GitHub issue or project item that owns it. External proposals follow `CONTRIBUTING.md` and belong in Ideas discussions.
13
14	Source excerpt:
15	# Contributing
16
17	## Provide evidence for the changed behavior
18
19	Match the evidence to the change. Use focused tests for behavior that can be tested and manual evidence
20	where appropriate. Do not substitute broad test runs for checking the affected behavior, or run
21	repo-wide checks just to satisfy this guide. A backend fix does not need unrelated UI evidence.

1	Learnt from: CR
2	Repo: pingdotgg/t3code PR: 0
3	File: AGENTS.md:0-0
4	Timestamp: 2026-10-16T06:14:31.198Z
5	Learning: Source excerpt:
6	# T3 Code
7
8	## Verifying
9
10	- Backend behavior changes ship with focused tests for that behavior.