burn-after-login

To bypass login walls for AI browser automation, you can generate dev-only authentication shortcuts that return 404 in production. These guarded endpoints or token generator scripts let agents authenticate instantly without filling forms or handling redirects.

A dev-only authentication shortcut is a guarded login endpoint or token generator script that works exclusively in development mode. It detects your existing session, cookie, or token auth system and calls those functions to authenticate instantly, remaining hidden in production.

Setting up session cookies for browser automation agents involves detecting your existing auth system and generating scripts that call your login functions directly. The process also updates agent instruction files with tool-specific authentication usage details.

Your existing authentication system works with dev-only login shortcuts if it relies on session, cookie, or token-based approaches. The setup validates dev-mode detection and builds shortcuts that integrate directly with your current auth functions.

You can automatically remove authentication shortcuts by using a self-destruct cleanup feature. After the skill generates the shortcuts and updates your agent instruction files, it removes the installed skill to ensure no leftover artifacts remain.

If deployed to production, dev-only auth endpoints return a 404 error. The system requires detecting development mode before generating the login shortcuts, ensuring the authentication bypass remains completely hidden and inaccessible outside development.