# Attach the context triage actually needs

Errors that arrive with a stack and nothing else, given the fields that make triage possible.

Category: Error reporting and triage
Source: https://letsship.ai/use-cases/attach-triage-context
Published: 2026-08-25

## Goal

Attach tenant, user, request, and route context to reported error events.

## Acceptance criteria

- Each field is present on a seeded event
- Personal data is scrubbed before the event is sent
- Context is attached centrally rather than at each call site
- Fields use the same names as the logs so the two can be joined

## What lands as proof

A seeded event in the tracker carrying every field, with the scrubbed ones demonstrably absent.

## Prompt

Copy this to an agent to open the ticket:

```text
Create a Linear issue in my team and assign it to the SHIP agent.

Title: Add tenant, user, and request context to error events

Description: Attach tenant, user, request, and route context to reported error events.

Acceptance criteria:
- Each field is present on a seeded event
- Personal data is scrubbed before the event is sent
- Context is attached centrally rather than at each call site
- Fields use the same names as the logs so the two can be joined

Before you create the issue, look at a recent error in this repository's tracker and list which of these fields is missing.
```

## Questions

### What does the agent actually change?

The ticket is scoped to one outcome: attach tenant, user, request, and route context to reported error events. Work that serves that outcome is in scope, and anything outside it is left for a separate ticket, so the pull request stays reviewable.

### How do I know the work is done?

The pull request carries the evidence, not only the diff. Here that means each field present on a seeded event, so a reviewer can confirm the result without reproducing the work locally.

### How much oversight does this need?

None is required before the run starts. Every claim this ticket makes can be checked by machine, so the agent works straight through and a person reviews the finished pull request like any other.