Lock In Lab Intern, rank 1 of 9

What do you see?

Pick the closest one. Each goes to what to try first, the incident it looks like, and the ticket that teaches the fix.

The agent keeps going in circles

Try this first

  1. Stop it. Every new attempt on top of a broken one makes the next harder.
  2. Go back to your last good commit (git restore . or git reset --hard <commit> if you're sure).
  3. Start a fresh session and give it three things: what you want, what you tried, the exact error. Ask for a plan before code.

Tickets that teach the fix

Back to the list

I deployed and the site is down, or still shows the old version

Try this first

  1. Ask the live site what it's running (curl the version endpoint or look at the footer). Don't trust the deploy job's colour.
  2. Open the host's build log, not the agent. The real error is usually in the last 30 lines.
  3. Reproduce the build from a clean clone: git clone . /tmp/check && cd /tmp/check and build there.

It happened to us

Tickets that teach the fix

Back to the list

It works on my machine, not on the server

Try this first

  1. Check that every file the build needs is committed: git status --ignored shows files git is ignoring.
  2. Compare environment variables. An empty variable is not the same as a missing one.
  3. Run the same check inside the real container or host, not on your laptop.

It happened to us

Tickets that teach the fix

Back to the list

Connection error, or it can't reach an API

Try this first

  1. Print the error's underlying cause, not just its message (e.cause in JavaScript, __cause__ in Python).
  2. Print the URL it's actually calling. Look for empty or wrong base URLs.
  3. Try the same request with curl from the same machine.

It happened to us

Tickets that teach the fix

Back to the list

Sign-in says OK but I'm not signed in

Try this first

  1. curl -i the sign-in request and read the Set-Cookie header itself.
  2. Check the cookie's domain, path, Secure (needs https) and whether the value looks quoted or cut.
  3. Check the provider's allowed redirect URLs include the address you're on.

It happened to us

Tickets that teach the fix

Back to the list

The page loads but nothing responds to clicks

Try this first

  1. Open the browser console. A red error at load time usually explains it.
  2. Try the production build locally (build, then start), not the dev server.
  3. Only then look at the code.

It happened to us

Tickets that teach the fix

Back to the list

It says saved, but the data isn't there

Try this first

  1. Write one record and read it back from a different session or tool (database console, a second script).
  2. Don't trust counters or success messages the code prints about itself.
  3. Check whether something deletes or overwrites it later (rotation, cleanup jobs, migrations).

It happened to us

Tickets that teach the fix

Back to the list

All tests pass, but it's wrong

Try this first

  1. Ask who wrote the tests. If it was the same agent that wrote the code, they test what it already thought of.
  2. Write three cases from the spec yourself, combining conditions it lists separately.
  3. Or have a second agent write them without reading the code.

It happened to us

Tickets that teach the fix

Back to the list

Works for some inputs, wrong for others

Try this first

  1. Write down the failing input exactly, and the expected output.
  2. Look for order: rules checked in sequence where the first match wins.
  3. Turn the failing input into a test before fixing anything.

It happened to us

Tickets that teach the fix

Back to the list

I hit usage limits

Try this first

  1. Count how many sessions and subagents are running right now.
  2. Use a cheaper model for mechanical work; keep the strongest for planning and review.
  3. Shorter rules files and fresh sessions reduce what every call has to read.

It happened to us

Tickets that teach the fix

Back to the list

It's costing more than I expected

Try this first

  1. Look at the provider's usage page, not your own estimate. Check cached tokens separately.
  2. Find what gets reprocessed when you change a prompt.
  3. Log cost per task from now on.

It happened to us

Tickets that teach the fix

Back to the list

The agent deleted or killed something it shouldn't have

Try this first

  1. Stop the session. Check git status and git stash list; restore from your last commit.
  2. If it killed a process, find out what it was before restarting things.
  3. Add a hook or permission rule so it can't happen twice.

It happened to us

Tickets that teach the fix

Back to the list

I think a key or password leaked

Try this first

  1. Rotate it at the provider now. Deleting the file doesn't remove it from git history.
  2. Check the provider's usage for anything you don't recognise.
  3. Add a secret scanner before commits.

It happened to us

Tickets that teach the fix

Back to the list

My fix disappeared

Try this first

  1. git log -p <file> shows who changed it back and when.
  2. Look for automation that reverts or regenerates files: scripts, bots, other agents.
  3. Check two agents aren't working in the same folder.

It happened to us

Tickets that teach the fix

Back to the list

Tests stopped running before deploys

Try this first

  1. Open the CI workflow file and read its last change (git log -p .github/workflows).
  2. Check what your own setup scripts commit.
  3. Make the deploy job depend on the test job.

It happened to us

Tickets that teach the fix

Back to the list