Compare

BugTape vs Condux

Condux is Sentry-SDK-compatible, self-hostable monitoring whose Conductor drafts fix PRs. BugTape adds browser replay and user reports for your agent.

Short answer: Condux is Sentry-SDK-compatible error monitoring you can self-host (source-available, FSL-1.1-ALv2) or use hosted at condux.ai. Its Conductor turns an issue into a draft pull request with a test, and after the merge it watches the error and resolves it once it stays silent. Pick Condux if you want to keep your Sentry SDK, run it yourself, or have the tracker write the fix with your own model key. Pick BugTape if you want browser replay and user reports in the evidence, and your own coding agent (Claude Code, Cursor, Codex) picking bugs up over hosted MCP. Both send fixes through human review.

No account: npx -y bugtape --help prints the commands and does not sign you in. The demo MCP at https://app.bugtape.ai/demo/mcp needs no sign-in. Your own workspace needs one.

Page owner: Jaco Veldsman, hi@bugtape.ai. Last checked 2026-11-02. I build BugTape. Every Condux row below is from condux.ai, its Sentry migration page and its GitHub README on 2 November 2026.

What Condux publishes

Keep your Sentry SDK. "Just change the DSN." Condux accepts Sentry's envelope and store formats. It also has first-party SDKs (JavaScript and Node, browser, edge, Next.js, Python, Go, Ruby, PHP, JVM and .NET) and accepts OTLP/HTTP logs, plus OpenTelemetry traces.
Self-host or hosted. Docker Compose for a single host or a Helm chart, with PostgreSQL, ClickHouse and a Kafka-API broker. The server is FSL-1.1-ALv2 (each release becomes Apache-2.0 after two years); the SDKs are Apache-2.0.
The Conductor. Opens draft pull requests only, scoped to the files in the stack trace, with a test, and never auto-merges. Repository access is a GitHub App with short-lived installation tokens, which the model is not given. You bring your own model: Anthropic, OpenAI or a self-hosted endpoint.
After the merge. Condux compares later event counts and resolves the issue once it stays silent for a configured window. Its homepage says it "verifies the error actually stopped, then resolves with evidence".
MCP. A project-scoped token for Claude, Cursor or any MCP client: list issues, read de-minified stack traces, page through occurrences. The README calls the endpoint read-only with no write tools; the homepage says a triage grant also lets the agent resolve an issue and leave a note.
Agent failures. With an OpenTelemetry trace exporter, a failing tool, a refused model call or an MCP tool error becomes a grouped issue.
Pricing. Free: 50k events a month and 3 AI draft-PR fixes a month. Team $29 a month: 500k events and 25 draft-PR fixes a month, pooled. Condux compares this with Sentry plus Seer.
Session replay and a user bug button are not stated on the pages checked.

What BugTape does

BugTape does not record every visit. The browser SDK keeps a short buffer and sends it with an uncaught error, a failed or hung request, or a user's report. Repeats of the same failure become one issue. DOM replay is rebuilt from events; it is not a screen video. Server SDKs (Node.js, Python) add route, service and release.

BugTape does not write the fix itself. Your own agent connects to hosted MCP at https://app.bugtape.ai/mcp (OAuth, or a bt_pat_ token), reads list_recommended_critical and get_repro_context, and calls ack_bug with working, then with prUrl, so your team sees Picked up and PR opened. A human reviews the pull request. When you approve the fix it is anchored to that release, and if real users hit the same failure on a later release BugTape reopens it as a regression.

Facts

	Condux (its pages, 2026-11-02)	BugTape (our docs)
Sentry SDK drop-in	Yes, change the DSN	No, BugTape does not accept a Sentry DSN
Self-hosting	Yes, Docker Compose or Helm; FSL-1.1-ALv2	No, hosted only, data in Sydney
SDKs	JS/Node, browser, edge, Next.js, Python, Go, Ruby, PHP, JVM, .NET; OTLP	Browser, Node.js, Python; Swift package in alpha with no replay
Session replay	Not stated	DOM replay around each failure
User bug button	Not stated	Yes
Who writes the fix	The Conductor: draft PR with a test, your model key	Your own coding agent
MCP	Project-scoped token; read-only per README, triage grant per homepage	Hosted, OAuth or `bt_pat_`; ranked inbox, repro pack, `ack_bug`, `listen`
After the fix	Resolves once the error stays silent for a set window	Fix anchored to the release; a recurrence from real users on a later release reopens as a regression
Agent failures (OTel)	Yes	Not a BugTape feature
Free plan	50k events, 3 AI fixes a month	Free, no card, 150 credits a month
Paid	Team $29/month	$10 prepaid = 2,000 credits; Pro $29/month

When each fits

Pick Condux when you want to keep a Sentry SDK, self-host, track AI-agent failures through OpenTelemetry, or let the tracker draft fixes with your own model key. Pick BugTape when the failures that matter happen in users' browsers, you want the replay and the user's report in the evidence, and you want your own coding agent to take the bug and show the team its progress. Both keep a human on the merge.

FAQ

Does Condux verify fixes?

Yes. After a Conductor pull request merges, Condux compares later event counts and resolves the issue once it stays silent for a configured window. BugTape checks a fix by watching whether real users hit the same failure on a later release, and reopens it as a regression if they do.

Does Condux have an MCP server?

Yes. A project-scoped token lets Claude, Cursor or any MCP client list issues and read stack traces. Its README calls it read-only; its homepage says a triage grant also lets the agent resolve an issue.

Can I self-host BugTape?

No. BugTape is hosted only, with data in Sydney. Condux can be self-hosted.

Can I keep my Sentry SDK with BugTape?

No. BugTape does not accept a Sentry DSN. Condux does.

Can I try BugTape free?

Yes, on the Free plan with no credit card.

Try the commands

npx -y bugtape connect claude   # or cursor, codex

Then click Allow once. Start free. No card.

Your team reviews the PR. Agents do not silent-ship.