Proto

Getting started

Your first task in Proto

Go from installation to a reviewed result using a small task, clear inputs, and an explicit definition of done.

For Business teams. Based on Proto 0.2.122.

Start with a task you already understand. A weekly update, a comparison of two documents, or a summary of a spreadsheet makes it easier to assess the result before giving Proto a larger job.

Install the desktop app

Open the download section and choose your platform: macOS on Apple Silicon, Windows x64, or Linux x64. Use the installer linked there or the official release page.

Open Proto and complete the sign-in steps it presents. Proto’s managed model is the default, so you can begin without obtaining a model-provider API key. If your team uses its own provider account, follow Models and API keys.

Proto is alpha software. Keep original copies of important inputs and use a small sample for the first run.

Choose how Proto should act

New installs start in Uninterrupted mode, which lets Proto run confirmable actions without stopping for review. To have Proto request review when an action needs your input, open Settings → Permissions and turn Uninterrupted mode off.

Your choice applies to action approval; it does not grant access to an ERP.AI organization, a protected file, or an operating-system capability. Read Approval controls before a task that sends messages or changes records.

Give it one clear job

Provide the relevant files or name their location. Describe the outcome, the sources to use, and what should remain a draft.

Compare these two supplier quotes against the attached requirements. Make a table of price, delivery date, warranty, and missing information. Cite the source for each difference. Save the comparison as a new document and leave both quotes unchanged.

A useful request tells Proto:

  • What to produce: a comparison table and a new document.
  • What to use: the two quotes and the requirements.
  • What to check: the facts that affect the decision.
  • Where to stop: preparation, before any external communication or purchase.

You can work with local files and the web without connecting an ERP.AI app. When a task needs ERP.AI records, make the intended organization and app clear before it begins.

Review the result

Open the generated file and check its important conclusions against the inputs. Review the recorded actions to see what Proto read or changed. If a source was missing, ask it to resolve that gap rather than treating an estimate as a fact.

Follow up in the same task with a specific correction: “Use delivery to our warehouse, not the supplier’s dispatch date.” Once the process works, ask Proto to save it as a skill for the next run.

Need help applying this to your work?Get support