Skip to content

FAQ

No. Typelets runs entirely in the browser - editing, the terminal, running code, and video. Any modern desktop browser works; phones get a read-only spectator view.

Your workspace files are durable - they are stored independently of any running sandbox and rebuilt into it on the next start. Anything written only inside the running sandbox at runtime (a local database file, scratch state) is not durable across a restart. Use an external store for data that must survive. See Core concepts.

Does the preview container really stay up?

Section titled “Does the preview container really stay up?”

With persistent preview on, yes - it opts out of idle eviction and stays warm while the workspace exists. Without it, a sandbox is idle-evicted after about 15 minutes.

SQLite or an in-process store works out of the box. A separate database server process can run, but its data lives in the sandbox and does not persist across a restart. For durable data, connect to an external database.

No. Recordings capture the code timeline and Run invocations, not video. The video call is live only.

No. Scoring is entered by a human interviewer against the rubric. The MCP tools can provide input to an assistant, but the score is always the interviewer’s.

The prompt, their own files, and public test cases. Never the rubric, hidden test expected-output, the reference solution, or scores. When the interview ends, the candidate loses access. See Sharing & roles.

Preview/hosting runs on the hosted platform. The self-hosted local Docker backend does not serve previews.

Create a personal access token and use the REST API or the MCP server.

Node, TypeScript, Python, Ruby, Java, Go, and C/C++ are installed. The Run button handles single-file entrypoints; multi-file projects run from the terminal. See Languages & runtimes.