Find: how long does a sign-in last in production?
How long does a sign-in session stay valid in production, and which file decides it?
Support say venue staff are being signed out "every quarter of an hour" and want to know whether that is the configured behaviour or a bug. Find the value the production deployment actually runs with, in seconds, and the file that sets it.
The repo is forty files, and the words session and TTL appear in a dozen of them: bearer tokens, password-reset links, the page cache and the session cookie all have lifetimes of their own. The setting you want is set in more than one place, and docs/configuration.md says which place wins, including a detail about deployment variables that still use their old names. An agent that greps for the setting's name and reads the first file mentioning it will answer with a number that is wrong for production, and will not find the file that decides it at all.
The agent's context window is small: about four files alongside its instructions. It has a grep tool. A prompt that tells it what to search for, where, and which document explains precedence gets the answer in a few calls; "find the session timeout" sends it reading.
Done when
ANSWER.mdexists, its first line is the value in seconds, and its second line is the path of the file that decides it.- The value is the one production actually runs with, after every override.
- No other file in the repo was changed.
You have a coding agent with tools to list, read and grep files, and to write ANSWER.md. It has been given the question above, and nothing else: not this page, not the hints below. Prompt it. It is graded on the ANSWER.md it writes (the value on the first line, the file that decides it on the second) and on leaving every other file as it found it, and ranked on model calls.