Skip to content

buzz-dev-mcp: configure PowerShell UTF-8 pipes - #7607

Open
bernhardkaindl wants to merge 1 commit into
block:mainfrom
youkeep-code:dev-mcp-configure-PowerShell-UTF-8-pipes
Open

buzz-dev-mcp: configure PowerShell UTF-8 pipes#7607
bernhardkaindl wants to merge 1 commit into
block:mainfrom
youkeep-code:dev-mcp-configure-PowerShell-UTF-8-pipes

Conversation

@bernhardkaindl

@bernhardkaindl bernhardkaindl commented Sep 12, 2026

Copy link
Copy Markdown

Summary

Configure UTF-8 native-pipe output for PowerShell commands launched by the Buzz MCP shell.

Fixes:

Problem

Windows PowerShell encodes text sent to native processes as US-ASCII.

As result, PowerShell replaces all non-ASCII message characters messages sent by agents when the message is piped from PowerShell to buzz:

... | buzz messages send --content -

For details, see

Solution

Prepend a UTF8Encoding OutputEncoding assignment when the resolved shell is powershell.exe or pwsh.exe. Git Bash and other shells retain their existing command text. Add a regression test for both paths.

Summary
-------
Configure UTF-8 native-pipe output for PowerShell commands launched by the Buzz MCP shell.

Fixes:
------
- block#5070
- block#6527

Problem
-------
Windows PowerShell encodes text sent to native processes as US-ASCII.

As result, PowerShell replaces all non-ASCII message characters messages
sent by agents when the message is piped from PowerShell to buzz:

```ps1
... | buzz messages send --content -
```

For details, see
- block#6527

Solution
--------
Prepend a UTF8Encoding OutputEncoding assignment when the resolved shell
is powershell.exe or pwsh.exe. Git Bash and other shells retain their
existing command text. Add a regression test for both paths.

Signed-off-by: Bernhard Kaindl <bernhardkaindl7@gmail.com>
@bernhardkaindl
bernhardkaindl requested a review from a team as a code owner September 12, 2026 18:49
@github-actions

Copy link
Copy Markdown

🔐 Codex Security Review

Status: review required for the current range.

The current range is 6c35e82bd50f4ad6587554eeb429e7378d474ba7...2a0c1c00cfe856c6d9a79987b11fa3f94e415bbd.
A new review must complete for this exact range. When manual authorization
is required, a Block organization member must comment exactly
@buzz-security-review 2a0c1c00cfe856c6d9a79987b11fa3f94e415bbd to authorize a new review.
Any previous review applies only to its recorded range.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant