Short answers, without the fog.
Do I need an account to use the workspace?
No. The sample workspace is open, and the workflow does not require a sign-in. The optional demo sign-in adds a role badge and, for the Judge role, a read-only operations view. It is not a registered user account and creates no profile.
What are the demo passwords?
The User demo password is TESTUSER. The default Judge demo password is STUDYADMIN. Both appear in the sign-in form when the default Judge password is active. Deployments can set a custom Judge password with the server-side ADMIN_PASSWORD variable; custom passwords are not shown in the application.
What does the Judge role change?
It opens the Judge console, which shows whether the live model path is configured, the current safe limits, and links back into the workspace. It does not expose the provider key, change settings, or unlock arbitrary repositories.
What happens when I sign in or out?
A successful sign-in sets one essential HttpOnly session cookie for up to eight hours. It records only the selected role. Logging out deletes the cookie. There is no account database, no tracking cookie, and no analytics. The privacy policy has the full explanation.
Does CodeRunway run tests or compile code?
No. The checks compare fixed file contents against static fixture criteria. They do not compile TypeScript, execute generated code, or prove runtime behavior. A matched criterion is a content signal, not proof that a patch works in a real project.
Can I point it at my own repository?
Not in this build. The sample issue and its two editable files are fixed so the demonstration stays small and its evidence stays honest. The app does not connect to GitHub or accept arbitrary file contents.
How do I reset the workflow?
Refresh the tab, or use the restart action at the end of a run. Workflow state lives in page memory and resets on refresh. A signed-in session can last longer than the workflow because it is stored in the session cookie.