Help us improve
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
By dlt
Query and manage Faultline error tracker from Claude Code — investigate error groups with full backtraces and local variables, compare occurrences to isolate root causes, inspect APM traces for slow endpoints and N+1 queries, and manage error lifecycle (resolve, ignore, reopen, delete) with confirmation guards.
npx claudepluginhub dlt/faultline --plugin faultlineApply one action (resolve/unresolve/ignore/delete) to many Faultline error groups in a single call.
Diff several occurrences of the same Faultline error group to see what varies between them.
Investigate a specific Faultline error group with full occurrence detail.
Investigate Rails production errors using the Faultline MCP server. Use when the user mentions a production exception, asks to look at recent errors, debugs a specific error group/occurrence, or wants to trace a slow endpoint.
Permanently delete a Faultline error group and all of its occurrences. Destructive and irreversible.
Share bugs, ideas, or general feedback.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
This plugin requires configuration values that are prompted when the plugin is enabled. Sensitive values are stored in your system keychain.
faultline_urlBase URL of your Faultline mount, including the engine path. Example: http://localhost:3000/faultline (no trailing slash). The plugin appends /mcp.
${user_config.faultline_url}faultline_tokenOne of the tokens you set in config.mcp_tokens in your Faultline initializer.
${user_config.faultline_token}Bugsnag API integration: view and manage errors, organizations, projects
Sentry Plugin for Claude Code to help with debugging including MCP, commands, and skill capabilities.
Monitor and analyze application error rates
Intelligent error tracking and solution recall system. Learns from every error you solve, providing instant access to past solutions with multi-level matching and confidence scores.
Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`. Originally from OpenAI's curated skills catalog.
Skills for using the Sentry CLI to interact with Sentry from the command line




A self-hosted error tracking engine for Rails 8+ applications. Track errors, get notified, and resolve issues—all without external services.
Add to your Gemfile:
gem "faultline", git: "https://github.com/dlt/faultline.git"
# Or from RubyGems (when published)
# gem "faultline"
Run the installer:
bundle install
rails generate faultline:install
rails db:migrate
Edit config/initializers/faultline.rb:
Faultline.configure do |config|
# Devise with admin role
config.authenticate_with = lambda { |request|
user = request.env["warden"]&.user
user&.admin?
}
# Or any authenticated user
config.authenticate_with = lambda { |request|
request.env["warden"]&.authenticated?
}
end
Create GitHub issues directly from the error dashboard with full context including stack traces, local variables, and source code snippets.
# Store in credentials: rails credentials:edit
# faultline:
# github:
# token: "ghp_xxxxx"
config.github_repo = "your-org/your-repo"
config.github_token = Rails.application.credentials.dig(:faultline, :github, :token)
config.github_labels = ["bug", "faultline"] # default labels for created issues
Notifications are optional. Faultline will track all errors and display them in the dashboard regardless of whether any notifiers are configured. Add notifiers only if you want to be alerted when errors occur.
# Store in credentials: rails credentials:edit
# faultline:
# resend:
# api_key: "re_xxxxx"
config.add_notifier(
Faultline::Notifiers::Resend.new(
api_key: Rails.application.credentials.dig(:faultline, :resend, :api_key),
from: "errors@yourdomain.com",
to: "team@example.com" # or array: ["dev@example.com", "ops@example.com"]
)
)
Use your app's existing mail configuration (SMTP, SendGrid, Postmark, Mailgun, etc.) without any external API:
config.add_notifier(
Faultline::Notifiers::Email.new(
to: ["team@example.com", "oncall@example.com"],
from: "errors@yourdomain.com" # optional, defaults to ActionMailer default
)
)
Emails are sent asynchronously via deliver_later, so Active Job must be configured. The email includes:
# Store in credentials: rails credentials:edit
# faultline:
# telegram:
# bot_token: "your-bot-token"
# chat_id: "your-chat-id"
# message_thread_id: 123 # optional, for forum topics
config.add_notifier(
Faultline::Notifiers::Telegram.new(
bot_token: Rails.application.credentials.dig(:faultline, :telegram, :bot_token),
chat_id: Rails.application.credentials.dig(:faultline, :telegram, :chat_id),
message_thread_id: Rails.application.credentials.dig(:faultline, :telegram, :message_thread_id)
)
)