Need out?
Start here.
On desktop, hold Escape for ten seconds.
The overlay exits and the session counts as failed. That is an intentional recovery path, including when you need to repair your local setup.
If you need another way out
The hardware
is still yours.
Android: pull down the status bar, open Settings → Apps → CodeLock → Force stop. Safe Mode, uninstall and revoked permissions also defeat the overlay.
Windows: Ctrl+Alt+Del and ending the process defeat the lock. Relaunching CodeLock restores the stored lock; killing it does not erase the session.
The full limits ledger distinguishes known escapes from behavior that is still unverified.
If something is not working
Check the mechanism.
- Every test passes. Why am I still locked?
- Correctness is one condition. Your measured runtime must also meet the language-specific budget: best × 1.35 + 40ms. The faster of two timed runs counts. Calibrate on your own judge hardware if correct answers consistently miss the budget.
- The API cannot be reached.
- Check that the local API, database and judge are running. An unreachable API is not proof that a session has ended. On desktop, use the ten-second Escape exit if you need to leave the overlay while you repair the stack.
- The desktop shell refuses to lock.
- Check its configuration dialog. The desktop shell needs the same unlock-signing secret as the API, or the corresponding public key for RS256 verification. A shell without verification configuration deliberately refuses to lock.
- The unsigned Windows installer did not install anything.
- Smart App Control can refuse an unsigned build. Check Windows Security → App & browser control and verify the installed binary’s timestamp. A successful installer exit code alone is not evidence that the app was installed.
- Reboot recovery or the Android overlay did not work.
- Reboot recovery has not been verified on hardware, and Android has not been verified on a device. On Android, check overlay permissions and battery controls. Do not depend on either behavior until you have checked it on your own machine.
- Where does my code go?
- To your local API and bundled judge. Submissions and history are stored in your CodeLock database. There are no accounts, GitHub pushes, LeetCode connections or metered application APIs. Keep the stack on your machine or a trusted private network.
If you find a bug
Leave a useful trail.
Include your platform, the action you took, what you expected and what happened. If the API returned a request ID, include it. Leave secrets and submitted code out of public reports.
Email tommydeleon104@gmail.com.
No release is configured here. See installation from source.