Ideas, tutorials, and updates from our team.
Error tracking for a small web app comes down to four things: catch what breaks, group the repeats, read the stack in your own code, and keep the minute before the crash. How each one works in the browser, what to throw away, and when you need a full monitoring tool.
A notification nobody acts on teaches people to ignore the next one. How we decided who hears about a task change in BugDump: recipients worked out from the task itself, nothing about your own edits, and a burst of triage clicks sent as one.
Claude's custom connectors and ChatGPT have nowhere to paste a token, so BugDump's MCP server now lets them sign in. How the flow works, and the four decisions behind it: one connection for every project, known clients only, checks on every request, and changes that stay attributed.
An embedded widget can read the page's html lang, the visitor's navigator.languages, or what the site tells it. They often disagree. The order we chose for BugDump's widget, why the page goes first, and the small things that broke along the way.
Ask an agent for a weekly status report and watch it open every ticket one at a time. It is not being dumb — it is doing exactly what your API forced it to do. The N+1 problem, moved from your ORM to your MCP server, and the three questions that fix it.
We gave every priority a stable key so integrations could rely on it. That key quietly became the value we sent to clients too — so making priorities editable meant finding nine readers, four switch statements that fail silently, and one assumption that was wrong in the plan.
Custom fields are the feature every team asks for and then regrets. The test that separates a field worth adding from one that will be empty in six weeks, and the four that pay for themselves.
Every bug tracker ships low/medium/high/critical, and every team quietly renames them in their heads. What a priority scale is actually for, how many levels you need, and why the words have to be yours.
A shared API key is fine while an AI agent can only read. Once it can move tasks and post comments, "who did this?" matters. How to authenticate an MCP server with personal tokens, and what we changed in BugDump.
Your app has a dark mode toggle. The chat bubble, feedback widget, and cookie banner ignore it. Why prefers-color-scheme is the wrong signal for embedded widgets, and the small API that fixes it.
Most bug dashboards count things. The useful ones answer a single question: are we keeping up? Four metrics that do, the ones that quietly mislead, and a five-minute weekly review built on them.
A bug ID is not a database row number. It is a word people say to each other. Here is why per-project numbering and a short project key like BD-42 make a bug tracker easier to talk about, and the trade-offs behind the design.