Sentry

Developer tools

Sentry for AI agents. Managed auth, ready-made tools.

Triage errors in your users' Sentry organizations: list issues, read stack traces, and resolve or assign them.

About Sentry

With the Sentry connector, your agent triages errors in each user’s own Sentry organization through Agent200: it lists new issues, reads the stack trace of the latest event and resolves, ignores or assigns issues. Every user connects their own account through managed OAuth.

Sentry is an application monitoring service that groups errors and performance problems into issues, with the stack traces and context needed to fix them.

Tools

What your agent can do in Sentry.

Each tool is a capability the model can call. You decide which ones a project allows, and every call runs with the end user's own Sentry connection.

  • List projects

    Read
    sentry_list_projects

    List the projects in an organization.

  • List issues

    Read
    sentry_list_issues

    List a project's issues, filtered by a search query and time range.

  • Get an issue

    Read
    sentry_get_issue

    Read an issue's details, status and event counts.

  • Get the latest event

    Read
    sentry_get_latest_event

    Read the most recent event of an issue, with its stack trace and tags.

  • Update an issue

    Write
    sentry_update_issue

    Resolve, ignore or assign an issue.

Control

Limits you can set.

You decide what your agent may do in Sentry, and Agent200 runs every call within those limits.

  • Turn single tools on or off

    Let your agent read issues and events, and switch off sentry_update_issue if it should report but never change an issue's status.

  • Restrict what the agent reaches

    Choose the endpoints and scopes a project may use. A call outside them is refused.

Get started

Connect Sentry
in three steps.

  1. 1

    Set up the SDK

    Add the Agent200 SDK to the codebase you already have and authenticate with your API key. The key covers every connector enabled for the project.

    agent.js
    Conceptual example
    Set up the SDK with the Agent200 API key
    // One Agent200 API key covers every connector enabled for the project.
    const agent200 = new Agent200({
      apiKey: process.env.AGENT200_API_KEY,
    });
  2. 2

    Let your user connect Sentry

    Each end user authorizes their own Sentry account once. Agent200 runs the OAuth flow, handles the callback, stores the tokens and refreshes them.

    connect.js
    Conceptual example
    Let an end user connect their account (managed OAuth)
    // Each end user authorizes their own Sentry account, once.
    const connection = await agent200
      .user("user_123")
      .connect("sentry");
    
    if (connection.authorizationUrl) {
      // Show this link to your user; Agent200 handles the rest.
      console.log(connection.authorizationUrl);
    }
  3. 3

    Run with the Sentry tools

    Name the user, the model and the tools. The model decides which Sentry tools to call, and Agent200 executes them with that user's connection.

    run.js
    Conceptual example
    Run a request with the connector's tools
    const result = await agent200
      .user("user_123")
      .run({
        model: "openai/gpt-5.6-sol",
        input: "What are the top unresolved errors in the API project this week",
        tools: ["sentry"],
      });
    
    console.log(result.output);

Access

Sign-in and permissions.

  • Who signs in

    Each of your users, once, on Sentry's own page. You never see or store their Sentry password.

  • What access is requested

    Sentry lists the scopes on its consent screen, such as reading projects and events, and writing to issues when the agent updates them. The agent sees only the organizations and projects that user can already open.

For agents

Instructions for AI agents.

Using a coding agent? Paste this brief into it, or give it the address of this page. It describes the Sentry connector and how to use it.

Agent brief
Connector: Sentry, through Agent200. In code: "sentry".
What it does: Triage errors in your users' Sentry organizations: list issues, read stack traces, and resolve or assign them.
Page: https://www.agent200.com/tools/sentry/

1. Get an Agent200 API key. If the developer has none, send them to https://agent200.com/platform/apikeys/ and ask them to choose "Create an API key". Read the key from the AGENT200_API_KEY environment variable. Never ask for it in chat, and never write it into code, prompts or logs.
2. Sign-in is managed OAuth. Each end user approves access once, on Sentry's own page, through the authorization link Agent200 returns. Never ask a user for a Sentry password or token in chat.
3. Give every request a stable id for the end user. Agent200 uses only that user's own connection.
4. Read tools: sentry_list_projects, sentry_list_issues, sentry_get_issue, sentry_get_latest_event. Write tools: sentry_update_issue. Name "sentry" in the tools of a request; the model decides which tool to call.
5. Stay within the project's settings. If a tool is turned off or a call is refused, tell the user. Do not work around it.
6. Before a write, confirm with the user, unless they asked for that exact change.
7. For setup with a specific framework, follow its guide:
   https://www.agent200.com/tools/sentry/framework/claude/
   https://www.agent200.com/tools/sentry/framework/chatgpt/
   https://www.agent200.com/tools/sentry/framework/claude-code/
   https://www.agent200.com/tools/sentry/framework/muse/
   https://www.agent200.com/tools/sentry/framework/grok-bot/
   https://www.agent200.com/tools/sentry/framework/openai-dots/
   https://www.agent200.com/tools/sentry/framework/claude-duet/
   https://www.agent200.com/tools/sentry/framework/hermes-agent/
   https://www.agent200.com/tools/sentry/framework/openclaw/

The code on the connector page is a conceptual example of the SDK. SDK reference: https://docs.igpt.ai/

This page is also available as Markdown, for agents and LLMs: /tools/sentry.md

Guides

Use Sentry with the AI you build on.

Step-by-step setup for Sentry with a specific model, assistant or agent framework.

FAQ

Sentry and Agent200, answered.

Who handles the Sentry OAuth flow and the tokens?

Agent200. It runs the authorization, handles the callback on its own domain, stores the tokens and refreshes them. You do not build or maintain an OAuth integration for Sentry.

Does my agent act as the end user?

Within what that user authorized, yes. Every request names an end user, and Agent200 uses only that user's Sentry connection, never another user's. It cannot reach anything the user or Sentry has not authorized.

Can I limit what my agent can do in Sentry?

Yes. You choose which services, endpoints and authorization scopes are allowed in your Agent200 configuration, and the agent works only within them.

  • GitHub

    GitHub

    Read repositories and work with issues and pull requests as the connected user.

    Managed OAuth Developer tools
  • GitLab

    GitLab

    Review merge requests, file issues, read code and check pipelines in your users' GitLab projects.

    Managed OAuth Developer tools
  • Bitbucket

    Bitbucket

    List and open pull requests, comment, read code and check pipelines in your users' Bitbucket workspaces.

    Managed OAuth Developer tools
  • Jira

    Jira

    Search, create and transition Jira issues for the connected user.

    Managed OAuth Developer tools
200 OK

Start with Sentry.
Your agent does the rest.

Your users connect their own Sentry accounts. Agent200 handles the OAuth, the tokens and every tool call.

Book a demo.
See it in action.

Tell us who you are, then pick a time for a 1:1 session with an expert from our team.

We use your details only to email you about Agent200. See the Privacy Policy.

Pick a time. We'll take it from there.

A 1:1 session with an expert from our team, about what you are building.

Open in Calendly (opens in a new tab)