Building Now

Reflex

Error Tracking

Give Claude eyes into your errors. AI investigates, diagnoses, and resolves—while you sleep.

Before

How Claude sees your app today

C
Claude
Y

You

There's an error spike in production. Can you check what's happening?

C

Claude

I'd like to help, but I don't have access to your error tracking system.

I can't see what errors are occurring, how many users are affected, or what's causing them.

Could you check Sentry and share the stack trace with me?

Y

You

*Opens laptop at 3am, logs into Sentry, copies stack trace...*

After

How Claude sees your app with Reflex

C
Claude
Reflex connected
Y

You

There's an error spike in production. Can you check what's happening?

C

Claude

Let me check the errors...

Using reflex.get_errors

reflex.get_errors(last: "1h", sort: "frequency")

Response

NoMethodError in UsersController#show

undefined method 'name' for nil:NilClass

247 occurrences · 89 users affected · HIGH

Found it. There's a nil user record causing 247 errors in the last hour. Let me get more context...

Using reflex.get_error_details

reflex.get_error_details(id: "err_abc123")

The error started right after the last deploy. It's affecting users created before the migration ran. The new_user_flow feature flag is the culprit.

Using cortex.disable_flag

cortex.disable_flag("new_user_flow")

Done. Flag disabled. Error rate is dropping.

I'll create a ticket to fix the underlying data issue and re-enable the flag safely.

Resolution time: 3 minutes

The Difference

Without Reflex

  • Claude can't see your errors
  • You copy-paste stack traces manually
  • You wake up at 3am to investigate
  • Hours to diagnose and fix

With Reflex

  • + Claude sees every error, instantly
  • + Full context: user, request, environment
  • + AI investigates while you sleep
  • + Minutes to diagnose and fix

How It Works

1

Your app throws an error

Reflex captures it automatically. No code changes needed.

NoMethodError: undefined method 'name' for nil
2

AI groups similar errors

Same bug, different entry points? Same group. No duplicate noise.

247

NoMethodError in UsersController

Grouped from 3 different stack traces

3

AI gets notified

Signal routes the alert to FORGE, your AI developer.

FORGE: "Error spike detected. Investigating..."
4

AI fixes it

Using MCP tools, AI investigates, diagnoses, and resolves.

Resolved in 3 minutes

The Tools AI Uses

Available via MCP (Model Context Protocol)

reflex.get_errors()

"Show me recent errors"

reflex.get_error_details(id)

"What caused this error?"

reflex.resolve_error(id)

"Mark this as fixed"

reflex.get_trends()

"Are errors increasing?"

Get Started

One gem. Zero config. Works in 30 seconds.

# Add to your Gemfile

gem 'brainzlab'

# Run bundle

$ bundle install

# That's it. Errors are being captured.

Coming Soon

We're building Reflex right now. Follow along to get early access and help shape the features.