Lock In Lab Intern, rank 1 of 9

SH-2featureSecond of 2 Shipper tickets

Sign-in, with a page only signed-in people can see

Takes
30 min in 3 steps
Checked
19 Nov 2026
min

Your estimate is optional. Your review compares it with how long it took; nothing is scored.

Only signed-in people can post, and there's a /mine page listing your own messages. You use a provider for the hard part. Your job is to check the parts the agent tends to skip: the server checks the session, not just the page.

You'll need The guestbook from SH-1 (or any app). An auth provider: Supabase Auth, Clerk, Auth.js or similar. Don't write password storage yourself. Prices checked this month are on Tools.

Pick a provider and write it down

Step 1 of 3, about 5 min

Add the provider and the sign-in method to AGENTS.md. Agents mix up libraries and versions; naming the exact one saves you a broken install.

The part of a video worth watching for this step

YouTube, Tech With Tim. Published Jul 2026.Checked 19 Nov 2026

Optional. The step counts when you've done it, whether or not you watch. Minutes from the creator's chapters; our notes on this video.

Add sign-in

Step 2 of 3, about 15 min

Add your public URL to the provider's list of allowed redirect URLs, or sign-in will work locally and fail once deployed.

Paste this to your agent
Add sign-in with <provider>, email magic link only. Protect POST /messages and add a /mine page. Check the session on the server for both.

The part of a video worth watching for this step

YouTube, Jason Lee. Published May 2026.Checked 19 Nov 2026

Optional. The step counts when you've done it, whether or not you watch. Minutes from the creator's chapters; our notes on this video.

the usual mistake

Sign-in answers 200 and the session never starts. Look at the actual Set-Cookie header (curl -i) before you look at the code. It happened to us in INC-08, "Login returns 200 and the session never starts".

Prove the server says no

Step 3 of 3, about 10 min

Sign out. Request /mine and post a message with curl, without cookies. Both must be refused. A page that only hides a button is not protection.

The part of a video worth watching for this step

YouTube, AI Engineer. Published Nov 2026.Checked 19 Nov 2026

Optional. The step counts when you've done it, whether or not you watch. Minutes from the creator's chapters; our notes on this video.

Check and ship

The whole ticket
Signed out:
curl -s -o /dev/null -w '%{http_code}\n' https://your-site.example/mine
curl -s -o /dev/null -w '%{http_code}\n' -X POST https://your-site.example/messages -d 'body=hi'

It passes when Both print 401, 403 or a redirect (302/303), never 200.

  • Signing in by email link or Google works on the public URL, not only on localhost.
  • /mine without a session is refused by the server (redirect or 401), not just hidden by the page.
  • Posting a message without a session is refused by the server.

No server checks your work in this version: you mark it, and your review says "Checked by you". Graded checks are planned for Plus.

Next: OC-1 Know which version is live

What do you see?

Pick the closest one. Each goes to what to try first and the incident it looks like.