Question 1

What exactly does Bugsby show me?

Accepted Answer

It traces each MCP tool your server exposes and draws it as an interactive flowchart — every function it calls, the branches it takes, and which steps touch the outside world. Click any node to drill in or read a plain-English narration.

Question 2

Does my code leave my machine?

Accepted Answer

No. The engine runs on your machine and narration goes to whichever model you choose — a local Ollama model keeps analysis fully on-device. Your source is never uploaded. The one network call is license activation, which sends only your key and an anonymous machine id — never your code.

Question 3

Is this a subscription?

Accepted Answer

No. One-time payment, perpetual license, no expiry — the tool keeps working forever.

Question 4

Which models does it support?

Accepted Answer

Groq (free tier, default when a key is present), a local Ollama model, or your existing Claude Code subscription. It falls back to local Ollama automatically if a cloud provider is unreachable.

Question 5

What can it read?

Accepted Answer

TypeScript and JavaScript packages that register MCP tools. More entry points (API routes, CLI commands, Lambda handlers) are on the way.

Question 6

Does it work with Python or other languages?

Accepted Answer

Not yet — Bugsby is for TypeScript and JavaScript packages today. More languages are on the roadmap.

Question 7

How does the license work?

Accepted Answer

Checkout issues a signed key. Run `bugsby activate <key>` once and it's saved for every project. The key is verified locally — no account, no phone-home.

Contact us