Bruno API Client | Blog & News

Between the Commits - October Edition

Written by Aditya | Nov 20, 2026

 

Welcome to the pilot edition of Between the Commits october edition. It's a new monthly post about what's happening in Bruno's GitHub community.

Bruno is an open source, so it doesn't only get better when the team ships something. It gets better when the people who use it every day report what's broken, ask for what's missing and send in fixes. In October, 105 people outside the team did exactly that.

Four people also got their first pull request merged into Bruno. A first PR means finding your way around code you didn't write, then asking strangers to review it. Between them, these four added a keyboard shortcut to tidy up JSON, made responses in Chinese and other languages display properly, fixed a variable tooltip that was hidden behind a dialog, and made sure an old bug can't come back.

Below are the month's numbers, what each of those PRs changed, and a few bugs the community helped track down.

October in numbers

The community opened 93% of October’s issues and 36% of its PRs.

105 people outside the Bruno team opened an issue or a pull request

Bugs led on both sides: 34 bug reports and 46 bug-fix PRs

What the community opened in October, by type

Put together, the community gave us 70 things to fix or build and 76 attempts at fixing or building them, in a single month. As of 31st October, 16 of those issues are closed and 5 of those PRs are merged. The rest are still open, and an open PR isn't a forgotten one.

The busiest threads were #9427, where Bruno showed no text on some Linux machines (7 comments), #9520, about naming a folder "folder" (6), and #9436, about using Bruno's AI features through an LLM gateway (6).

What the community shipped

Prettify with a keyboard shortcut

Shortcut: Option + Shift + F on macOS, Alt + Shift + F on Windows and Linux

PR: #8555 by @yume02kki · closes #1578 · yume02kki's first PR to Bruno

A lot of JSON arrives in Bruno already squashed onto one line: copied from a log, a browser's network tab or a teammate's message. Until now, tidying it up meant reaching for the mouse and clicking Prettify.

yume02kki made it a keystroke. On macOS and Windows it's the same shortcut VS Code uses to format a document. It works anywhere there was a Prettify button: request bodies, GraphQL, gRPC and WebSocket messages, and response examples, and it only acts on the editor your cursor is in.

Responses in Chinese, Japanese and other languages now show as JSON

PR: #9367 by @Mark007-R · fixes #9362 · Mark007-R's first PR to Bruno


Bruno decides how to show a response by looking at what came back. JSON gets the formatted view, with indentation and syntax colours, so you can read nested data at a glance.

That decision was going wrong for anyone whose API returns text in other languages. A response with Chinese, Japanese, Cyrillic or emoji in it could land in the raw view instead, as unformatted text, even though the server said it was JSON. It hit short responses hardest, and a body as small as {"a":"测试"} was enough. The user who reported it marked it as making Bruno unusable for them.

Mark007-R tracked down the cause and fixed it. These responses now open in the formatted JSON view like any other JSON.

It's an easy bug to miss when all your test data is in English.

Variable tooltips no longer hide behind the New Request dialog

PR: #9196 by @y0geshpatil · fixes #7927 · y0geshpatil's first PR to Bruno

Variables let one request work across environments: can point at staging today and production tomorrow. Hover a variable in a URL and Bruno shows you the value it will actually use, with a button to copy it.

In the New Request dialog, that popup was opening behind the dialog, so it was unreadable or partly covered, and you couldn't click copy.

y0geshpatil fixed it. The popup now opens on top of the dialog, the same as it does everywhere else in Bruno.

An old bug that can't quietly come back

PR: #9693 by @PaulooBarros · closes #2310 · PaulooBarros's first PR to Bruno

Back in 2024, people reported a confusing bug. Send a request that returns plain text, change it to return JSON, send it again in the same tab, and Bruno kept showing the response as plain text, without JSON formatting. The workaround was to click over to another tab and back.

We fixed that in v3.1.0. But nothing checked that it stayed fixed, so any later change to the response view could have quietly brought it back, and the original issue was still sitting open.

PaulooBarros added an automated test for exactly that scenario. It runs as part of Bruno's test suite, so if this bug ever returns, we'll catch it before it reaches you. And the old issue is finally closed.

Bugs the community helped track down

Rohan, who handles support on GitHub, replied on 29 issues opened in October. On these four, people from the community did a lot of the work.

No text at all on some Linux machines

#9427

After updating to 4.2.1, martin-casserly-bl opened Bruno on Kubuntu and saw no text anywhere. temptodev worked out that a broken font file on the system was to blame and shared a fix. FopherC found a second cause on Ubuntu and posted a way around it that doesn't uninstall anything.

runRequest() didn't match the docs

#9501

soerenkoehler found that bru.runRequest() didn't return what the docs said. aayushbaluni dug into the code and explained the mismatch, and the docs were fixed the same day.

Wrong response size in KB

#9648

ZhangTianCi noticed response sizes were showing wrong: a 1.09 KB response came up as 1.9 KB. siddiqueirshad sent a fix in #9673, merged on 3 November. It was their first PR to Bruno too.

A folder called "folder"

#9520

qwrttqr noticed you can create a folder called "folder" but can't rename one to it. Their team would rather not have, in their words, “one awful name” in their generated OpenAPI spec. geo-777 has offered to fix it.

Thanks

Thanks also to bboygun, ZXLyyds100 and aayushbaluni, who left the most comments on pull requests, and to qwrttqr, reefhound and tech-dipesh, who did the same on issues.

What happens after you open a PR?

Every PR gets read. Someone on the team picks it up, checks which issue it solves and tests it against the original problem. If it does what it says and it's right for Bruno, it goes to engineering for code review, and then it's merged.

That takes time, because whatever we merge ships to everyone who uses Bruno, and we'd rather take a little longer than ship something that breaks someone's setup. If your PR is still open, it's in that queue, and we'll reply in the thread when it moves.

Issues go through the same kind of check. New ones get read and labelled, the ones we can reproduce get tracked, and the ones that need more detail get a reply asking for it.

Getting involved

Every PR in this post was someone's first. If you want to send yours, issues labelled good first issue are a good place to start.

Thinking about submitting your first PR to Bruno? Consider this your nudge! 

We've put together a beginner-friendly guide to help you set up Bruno's open-source repository locally and get started with your first contribution.

How to contribute to Bruno - A Beginners Guide

Happy contributing, and see you in next month's community roundup! 🧡