Skip to content

Go to the docs contents

Errors (Sentry)

Your app’s exceptions, grouped by a Sentry SDK connected to while. A never-seen-before error wakes your agent.

Updated November 21, 2026.

View as Markdown

Sentry-compatible error tracking: identical errors grouped in one stack, and a never-seen error that rings to wake your AI

You, to your AI: Set up error tracking.

What your app receives

Your app receives these environment variables at every deployment:

VariableWhat it holds
SENTRY_DSNThe address where the Sentry SDK sends the server’s errors.
SENTRY_DSN_PUBLICThe one for an SDK running in the browser.

When to use it

Use it to group the app’s exceptions with a Sentry SDK. A new error wakes the agent.

How it works

Plug any Sentry SDK into SENTRY_DSN: errors are grouped, and a never-seen error wakes the agent.

What to know

SENTRY_DSN is an internal address, reachable without opening egress. For an SDK in the browser, use SENTRY_DSN_PUBLIC. This variable also exists during the build (npm run build), with the same value as at runtime.

Guides

Give your AI the message, and it takes care of the rest

Give this to your AI

Read while.sh/agents and help me get started with while.

Copy the message

In 3 minutes, with no sign-up, the tool has its own address. To keep it, create your account.

For a company project, write to the while team: hello@while.sh