Operator Guide

Use Looking Glass to supervise AI-assisted data entry, validate extracted values, and feed high-quality judgments back into evaluations. This guide walks through setup, daily workflow, and best practices.

Prerequisites

• Chrome with the Looking Glass extension loaded via chrome://extensions.
• Backend URL configured in the extension (defaults to http://localhost:8010).

1. Start a Session

1. Open the extension and choose Start Session.
2. Optional: enter your internal task id to correlate this session with your workflow.
3. Provide the backend entity identifier (e.g., a customer ID) so answers are fetched for the right record.
4. Navigate your target application; Looking Glass collects fields and candidate answers across pages.

2. Scan and Get Schema

• Click Scan on a page with a form to extract the schema (field names and types).
• Review the detected schema and remove irrelevant fields (e.g., marketing opt-ins). Use the Remove action to strike a field out so it’s excluded from judgments and autofill.
• Click Get Answers to request candidate answers from your connected backend.

3. Get Answers and Autofill

1. Mark each suggestion as correct, incorrect, or unknown.
   • If the suggestion is correct, you can mark the suggestion as correct.
   • If the suggestion is wrong, and you can determine the correct answer based on the supplemental information, you can provide a correction and mark the suggestion as incorrect.
   • If the suggestion is wrong, and you cannot determine the correct answer based on the supplemental information, you can mark the suggestion as unknown.
2. Click Submit Evals to send judgments to the backend.

4. Stop/Resume

• When you are finished with the form, click Stop Session to end the session.
• If you need to resume the session, click Resume Session to resume the session and pass the session id.

Troubleshooting

• No fields detected: Ensure the page contains a standard form; try rescanning after page load.
• Answers not returned: Verify the Backend URL in the extension and confirm the backend is running.
• CORS/Network errors: For local development, confirm the backend allows requests from the extension origin.
• Mismatched schema: Ask engineering to align field identifiers and types with what the backend expects.