BinGo

A multi-platform, visual concurrency debugger for GO.

Status

Overview

BinGo is a standalone visual concurrency debugger for Go that helps you:

• Visualize and understand goroutines, channels, and synchronization behavior
• Capture detailed runtime events and turn them into clear, interactive visualizations
• Use in a terminal UI or inside editors like VS Code or Vim
• Track goroutine lifecycles
• Inspect channels and mutexes
• Replay timelines of concurrent execution
• Detect deadlocks and goroutine leaks
• Debug tricky concurrency issues that traditional tools miss
• Extend with new frontends and integrations thanks to a modular, UI-agnostic core

Supported Platforms

BinGo is currently built and tested on:

• darwin/arm64 (Apple Silicon) — build with -tags bingonative
• linux/amd64

Builds on other GOOS/GOARCH combinations will fail with undefined: newBackend and similar errors from the internal/debugger package.

Debug Adapter Protocol (DAP)

BinGo speaks the Debug Adapter Protocol alongside its native WebSocket protocol, so a standard IDE (VS Code, neovim) can drive a debug session over a TCP socket while BinGo's own visual clients observe — and optionally also drive — the same session in parallel.

Start the server with a DAP listener:

bingo -addr :6060 -dap-addr :4711

Point your editor's debug adapter at 127.0.0.1:4711. The DAP client creates a managed session on launch/attach; WebSocket observers join that same session via /ws?session=<id> (the id is discoverable through /api/sessions, and the adapter also prints it as a console output event). DAP covers the standard debug loop (breakpoints, stepping, stack/variables, continue/pause); BinGo's richer concurrency visualizations remain available to WebSocket clients on the same session. See AGENTS.md → DAP for the architecture.

BinGo also ships an interactive DAP client, cmd/dapcli, that mirrors the WebSocket CLI (cmd/cli) but drives a session over DAP:

just dapcli                       # create a session on launch (default -addr localhost:4711)
just dapcli -session <id>         # join an existing session as another client

Any number of dapcli and cli clients can drive and observe the same session at once — start one, launch a target, then join from other terminals with the announced session id.

Documentation

For detailed documentation, including client meeting minutes, existing solution comparision, project roadmap, installation instructions, usage guides, and API references, please read the Docs.