Preceptor

Preceptor supports you while you work on supported course assignments in VS Code. It provides guided feedback after a failed test and a short check-off interview after you pass a question.

Getting Started

After installing the extension:

1. Open a supported assignment folder in VS Code.
2. Run a question-specific test command in the integrated terminal.
3. Select Get started when Preceptor prompts you to finish setup.
4. Sign in with your Berkeley Google account and choose whether your de-identified activity may be used for research.
5. Return to VS Code and run the test command again.

Research participation is optional. Choosing either option gives you full access to the extension. Your sign-in and research choice are remembered, so you normally complete setup only once.

Two Modes

Problem Solving

When a question-specific test fails, the Problem Solving panel opens. On the first failure, you can choose whether to receive automatic feedback. When enabled, the feedback points you toward the issue without providing the solution. Use it with the terminal output, revise your code, and run the test again.

You can turn automatic feedback on or off from the panel. If feedback is off, your test still runs normally.

Interview

After you pass a question, the Interview panel opens for a short check-off. The interviewer asks about your solution and reasoning in your own words. Choose Start interview if you are ready, or Not yet to save the prepared interview. When you are ready later, run the question's passing test again to reopen it.

During the interview, stay in VS Code and do not consult external tools. If you close the panel or VS Code before finishing, your progress is saved. Run the question's passing test again when you are ready to resume. Use the Stop interview button only when you want to end the current attempt. For an interview labeled Incomplete, you may run the question’s passing test again to start another interview, depending on course policy.

Typical Workflow

1. Open the assignment in VS Code and work on one question.

2. Run that question's test in the integrated terminal, such as:

   python3 -m pytest -k a_plus_abs_b
   

   Depending on the assignment, Preceptor also recognizes targeted Gleam commands such as gleam test -- ascending and npm commands such as npm test -- -t q1.

3. If the test fails, review the terminal output and feedback, revise your code, and test again.

4. When the question passes, start the interview or choose Not yet and return after another passing test run.

5. Continue to the next question.

Use the question-specific test commands provided on the assignment page so the extension can identify the question you are working on.

Preceptor intentionally ignores unlock commands, score or full-suite commands, and standalone syntax-check commands. Those tests still run normally, but they do not open a Preceptor panel.

Account Options

Open the VS Code Command Palette with Cmd+Shift+P on macOS or Ctrl+Shift+P on Windows and Linux to access:

• Preceptor: Show Sign-In Status
• Preceptor: Review Research Consent
• Preceptor: Sign Out

Requirements

• VS Code 1.93 or newer
• A course assignment opened as a folder in VS Code; use one assignment folder per window
• The assignment's required Python, Gleam, or npm tools installed and working
• Test commands run in the VS Code integrated terminal with terminal shell integration enabled
• Windows: PowerShell must be allowed to run scripts for shell integration to activate. When every execution-policy scope is unconfigured, Preceptor can offer a one-click fix equivalent to running Set-ExecutionPolicy -Scope CurrentUser RemoteSigned once in PowerShell. Preceptor does not overwrite existing execution-policy settings; Git Bash and PowerShell 7 are the recommended alternatives
• Internet access and a Berkeley Google account

License

Preceptor is available under the MIT License included with the extension.