Start with the complaint.
Record the customer’s words and device context without copying secrets or unrelated files.
Offline-first · Windows
Keep the diagnostic thread intact—even with no signal.
Turn a customer complaint and each test result into a persistent repair case. Get one useful next test at a time, keep completed work visible, and leave every action to the technician.
Preparing Windows installer
See how it works
Checking the latest verified build…
- Local by default
- No account
- No telemetry
- Never executes commands
How it works
One case. One next test. A record you can trust.
Record what happened.
Observations and test results are saved locally before the model reasons.
Follow the evidence.
The copilot ranks hypotheses and proposes one useful next test without silently repeating completed work.
The workbench
The whole diagnostic thread, without digging through chat.
See the current assessment, next test, ranked hypotheses, local sources, and completed work in one place. Cases survive restart and export to a readable Markdown record.
- Persistent stateCase history stays in local SQLite storage.
- Grounded cardsProcedure references come from the bundled local index.
- Visible guardrailsRepeat and data-risking steps cannot pass silently.
Advisory by design
Advice stays advice.
Field Tech Copilot never runs a command or changes a customer’s machine. It blocks silent repeat tests, labels risky steps, and requires technician confirmation before destructive or data-risking work.
Pre-alpha software can be wrong.
A trained technician must verify every recommendation and remains responsible for customer data and repair decisions.
Do not enter passwords, recovery keys, payment data, or unrelated customer files.
Windows bundle
Preparing the field kit.
The page enables the installer only when a release contains the pinned app, runtime, model, starter knowledge, licenses, and checksum.
Preparing Windows installer