Reset your Compute sandbox
How to reset the offline practice example for a clean start, without touching your account, files, keys or real work.
Your practice session is no longer clean
The documentation sandbox is an offline synthetic exercise whose session lives in the example program's memory. Resetting it starts a fresh practice session. It does not reset a Lithi account, revoke a credential, delete a real job or change live work.
Start with Reset the offline sandbox example and use the reset shown in that example.
Reset only the practice state
The eight-review quickstart defines a fresh_session() function. Recreate the session with that function, then check the example's final assertion.
A successful reset reports After reset: 0 outcomes; reviewed: False. The fictional fixture remains available so you can repeat the exercise from the same known input.
Do not run an invented lithi sandbox reset command. This documentation sandbox is not a live account-management surface.
Check what remains on your computer
Resetting the in-memory example does not erase a script you saved, terminal output, notes, screenshots, or backups. Remove only files you created through your normal file-management process when you no longer need them.
Closing the page or clearing the practice session is not proof that other copies were deleted. Do not use the sandbox reset as evidence about live retention or deletion.
Keep synthetic and live work separate
Use only the fictional inputs supplied by the exercise. Do not insert real API keys, account identifiers, customer data, private file paths, or destination credentials.
A sandbox success proves the local example behaved as described. It does not prove live admission, provider isolation, result delivery, pricing, payment, or production readiness.
Stop on a mixed or unclear state
Stop if the example contains real data, if you cannot tell whether a reference is synthetic, or if the reset assertion does not match the documented result. Do not delete a project folder or live account data to make the example look clean.
Use Contact Lithi with the name of the sandbox example, your local observation, and any safe error text. Leave out payloads, keys, signed URLs, customer files, and banking information.