Sentry and Codex: add the MCP server and triage errors on a schedule

What Codex does for Sentry triage

• Reads unresolved Sentry issues that are new or regressed since its last run.
• Checks your board first, so a noisy error gets a comment instead of ten new issues.
• Files each new error with its impact, first and last seen, the release it started in, the top stack frames and a likely cause, marked as a guess.
• Fixes the small, obvious ones in a pull request with a test, and waits for review.

Codex features for Sentry triage

How to set up Codex for Sentry triage

1. Connect the tools

   Add Sentry as a streamable HTTP server, then sign in once. Sentry's own docs also show the mcp-remote bridge, which works too, but Codex doesn't need it.

   # ~/.codex/config.toml
   [mcp_servers.sentry]
   url = "https://mcp.sentry.dev/mcp"
   required = true
   
   # Then sign in with OAuth
   codex mcp login sentry

2. Write the rules in AGENTS.md

   Codex reads AGENTS.md before any work: ~/.codex/AGENTS.md, then the files from the repository root down to the folder it's working in. Put the job's rules there, or in a skill under .agents/skills/ if they're long. See the AGENTS.md guide.

   ## Sentry triage rules
   1. List unresolved production issues first seen or regressed
      since the last run.
   2. Search the board for the Sentry issue ID before filing.
   3. File new ones with users and events affected, first and last
      seen, the release, the top stack frames and a likely cause,
      marked as a guess.
   4. Urgent if it blocks sign-up, payment or data; High above 1%
      of sessions; otherwise Medium.
   5. Small, obvious fix: open a pull request with a test. Don't merge.
   6. Never resolve, ignore or delete anything in Sentry.

3. Run it without the interactive interface

   codex exec runs one task and exits. Progress goes to stderr and the final message to stdout; -o also writes it to a file and --json streams events. The sandbox is read-only unless you pass --sandbox workspace-write.

   # A triage pass from cron; the summary goes to a file
   codex exec --sandbox workspace-write \
     -o triage.md "Triage new Sentry errors with the rules in AGENTS.md"

4. Put it on a schedule

   Create a scheduled task in the ChatGPT desktop app or on the web (the CLI doesn't manage them), or run codex exec from cron. See how to make Codex proactive.

Source: Codex documentation

Limits and safety

• It needs to read Sentry issues, not change them. Leave resolving and ignoring to people.
• Its cause is a guess from the stack trace. A person confirms it before a fix ships.
• Errors can carry user data. Keep the issues it files on a private board or repository.
• Codex sandboxes commands by default: writes stay in the workspace and the network is off. Keep danger-full-access for an isolated runner or container.

Claude Code or Codex for Sentry triage?

The rules carry over. Write them once in AGENTS.md and put @AGENTS.md in CLAUDE.md, and both agents read the same file.

Step by step for the other agent: Sentry triage with Claude Code.

Make Sentry triage someone's job

Commands run when someone remembers to run them. Crewmark turns your own Codex into an AI employee with a role, a goal in numbers, working hours and a heartbeat, so the work happens on schedule and shows up on a board.

1. Start from the role

   The AI software engineer, with these rules in its brief.

2. Put the work on its board

   Add the job as a recurring issue. The employee wakes on its heartbeat, does it and reports in a comment.

3. Related

   The Sentry error triage page has the full brief and priority rules.

FAQ