Project copilot
The project surface binds a local folder at setup and reads its live tree with tools — for take-home walkthroughs and “explain this repo” rounds, not as a substitute for Live Coding.
INTERVIEWER
Walk me through how login talks to the API in this repo.
AI ANSWER
Start in src/auth/session.ts. login() posts credentials to /v1/auth/login, then setSession stores the JWT.
Where it attaches
src/api/client.tsreads the session and setsAuthorizationon each request.- The login form in
src/pages/Login.tsxonly callslogin()— it does not talk to the API itself.
Using it
Press ⌘4 to focus the project surface (or ⌘⌥4 to focus it and show the window). Questions still reach it the usual ways — transcribed audio, a screen snip, or typed draft — but the answers are grounded in the live tree. Teammate or git changes are visible on the next question.
Bind the folder at setup
- 1
Select Project and pick a folder
On the live-copilot setup form, check Project and choose a local folder. Role and job description stay required, same as Verbal and System design. There is no programming-language picker on this surface. - 2
Check for readable source
The app skips junk while checking the folder. Start is blocked until the folder has at least one readable source file. - 3
Start with the live tree
During the round, the overlay reads the live tree with tools, so teammate or git changes are visible on the next question. You cannot add Project after Start or re-bind the folder in this version.
What it is not
Project is overlay Q&A grounded in the live tree: locate a file, explain a flow, and walk the interviewer through the repo. It does not replace Live Coding when you are implementing on the interviewer's pad.