Error Services

Three error-tracking integrations — SolidErrors, Sentry, and Honeybadger — give your agent visibility into application errors.

SolidErrors

Database-backed error tracking. Runs in your Rails database — no external API needed.

gem "ask-solid_errors"

Prerequisites:

gem "solid_errors"

bin/rails solid_errors:install:migrations
bin/rails db:migrate

Then use:

# Recent errors
errors = Ask::SolidErrors.recent(limit: 10)
errors.map { |e| [e.id, e.exception_class, e.message.truncate(200)] }

# Find a specific error
Ask::SolidErrors.find(42)

# Unresolved errors (needs attention)
Ask::SolidErrors.unresolved

# Resolved errors
Ask::SolidErrors.resolved

# Filter by class or severity
Ask::SolidErrors.by_class("ActiveRecord::RecordNotFound")
Ask::SolidErrors.by_severity("error")

# Search messages
Ask::SolidErrors.search("timeout")

# Count occurrences
Ask::SolidErrors.occurrence_count(error)

No authentication needed — reads from your Rails database.

Sentry

Cloud-based error tracking. Requires a Sentry API token.

gem "ask-sentry"

Then use:

# Recent errors
Ask::Sentry.recent_errors(organization: "myorg", project: "myapp", limit: 10)

# Issue events
Ask::Sentry.issue_events(12345, limit: 10)

Authentication

Generate a token at sentry.io/settings/account/api/auth-tokens/.

The Sentry client resolves credentials through the ask-auth chain — any of these will work:

  1. Environment variable: SENTRY_TOKEN
  2. Credentials file: ~/.ask/credentials.yml with sentry_token: <value>
  3. Rails credentials: rails credentials:edit and add sentry_token
  4. Database-backed tokens (via Ask::Auth)
  5. OAuth flow (via Ask::Auth)

Honeybadger

Cloud-based error tracking. Requires a Honeybadger API token.

gem "ask-honeybadger"

Then use:

# List all projects
Ask::Honeybadger.projects

# Recent faults
Ask::Honeybadger.recent_faults(project_id: "PROJECT_ID", limit: 10)

# Fault summary
Ask::Honeybadger.fault_summary(project_id: "PROJECT_ID")

# Single fault
Ask::Honeybadger.fault(project_id: "PROJECT_ID", fault_id: 42)

Authentication

Get your token at app.honeybadger.io/users/edit.

The Honeybadger client resolves credentials through the ask-auth chain — any of these will work:

  1. Environment variable: HONEYBADGER_TOKEN
  2. Credentials file: ~/.ask/credentials.yml with honeybadger_token: <value>
  3. Rails credentials: rails credentials:edit and add honeybadger_token
  4. Database-backed tokens (via Ask::Auth)
  5. OAuth flow (via Ask::Auth)

Example: Debug with Error Context 

session = Ask::Rails::Harness.agent_session

# The agent can check errors and debug
response = session.run(
  "Check the recent errors and find out what's causing the spike in timeouts"
)

# The agent might:
# 1. Ask::SolidErrors.recent to check errors
# 2. ReadLog to correlate with log messages
# 3. QueryDatabase to check if there's a slow query
# 4. ReadModel on the affected model
# 5. Propose a fix

Next Steps

This site uses Just the Docs, a documentation theme for Jekyll.