## TL;DR

With no RESEND_API_KEY set, the magic link prints to the terminal, but opening it in Safari 16.4.1 bounces you back to the magic-link page instead of into the dashboard. Issue triggerdotdev/trigger.dev#186 (closed, 19 comments): Logging into a locally-run Trigger.dev via magic link fails in Safari.

## Steps

1. Issue triggerdotdev/trigger.dev#186 (closed, 19 comments): Logging into a locally-run Trigger.dev via magic link fails in Safari. With no RESEND_API_KEY set, the magic link prints to the terminal, but opening it in Safari 16.4.1 bounces you back to the magic-link page instead of into the dashboard. Sending the link by real email did not reproduce it, which pointed at a cookie/session quirk with the terminal-printed link in Safari.

2. Resolved by a product change, per maintainer matt-aitken: when running the platform locally, Trigger.dev no longer sends a magic link at all and just logs you in directly. If you hit the Safari redirect loop on an older local build, upgrade to a release with this change. On current versions there is no magic-link step in local dev, so the Safari cookie issue cannot occur.

## When to use

You are seeing this: Sending the link by real email did not reproduce it, which pointed at a cookie/session quirk with the terminal-printed link in Safari. Use this skill when you run into "Magic link login loops in Safari on local Trigger.dev".

## When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

## Versions

Versions mentioned in the source: Safari 16.4.1. If you are on something much newer or older, the details may have shifted.

## Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.