Skip to main content
Software has bugs. Open source software has bugs that are public bugs. You can either pretend otherwise and hope nobody notices, or write them down where everyone can find them. We chose door number two.

​
At a glance

48 open

Known issues across Gateway and Bindu Core today

11 fixed

Graduated into the postmortem archive, kept forever

7 high

Severity you should read before you deploy

​
How to read this section

1

Read the scenario first

High-severity entries open with a short story — what the bug looks like from the outside. If your debugging matches, you’ve probably found it.
2

Glance at the cause

The technical explanation. Which file, which line, which wrong assumption.
3

Apply the workaround

Something you can do today, while we work on the real fix.
When we ship a fix, the issue disappears from this page. If the fix taught us something, it graduates into a postmortem — kept forever so the next maintainer can learn.
The source of truth lives in the Bindu repo at bugs/known-issues.md. This site mirrors it. Same content, same severities, same slugs. Filing a GitHub issue? Reference the slug and we’ll know exactly what you mean.

​
Severity — what each level means

High

Real problems you’ll hit in production. Stop and read the scenarios.

Medium

Real bugs with narrower blast radius or a decent workaround. Worth skimming.

Low

Things that are off, but unlikely to wake you up at 2am.

Nit

Not really bugs. Dead code, pointless types, small rainy-day cleanups.

​
Gateway

The layer between your clients and your Bindu agents. Sessions, compaction, the planner LLM, routing tool calls to peers. When something breaks end-to-end, it’s often here.

High

3 bugs

Medium

13 bugs

Low

16 bugs

Nits

4 items

​
Bindu Core (Python)

The runtime bindufy() wraps around your handler. Most of what’s here is security-adjacent: the x402 payment path and the Hydra auth middleware.
Using x402 to charge money? Read the four Core High-severity bugs first. The short version: don’t rely on x402 as your only revenue protection in the current release. There’s detail on the Core High page.

High

4 bugs

Medium

7 bugs

Low

1 bug

SDKs / FE

Nothing yet

​
Postmortems

The other side of this page. Known Issues shrinks as we fix things — but the fixes worth remembering don’t vanish into git history. They graduate into the postmortem archive. One file per bug, kept indefinitely. Each one explains what broke, why, and where else the same shape could hide.

Browse the postmortems

11 fixed bugs so far — 5 in Core, 6 in Gateway. Each one teaches something about how this codebase fails.

​
One last thing

We think you deserve to know this stuff upfront. We’d rather you find x402-no-signature-verification here, on a page we wrote on purpose, than in a panicked Slack message after a Monday morning incident. If you hit one of these and want to help fix it, open a GitHub Issue referencing the slug. That’s all we need.