Before you start
This personal development candidate is suitable for isolated test projects. Keep backups and prepare Windows x64 with the required installed, signed-in clients.
The candidate is unsigned, clean Windows VM installation is untested, and final feature/live UI gates are unfinished. Release details →
Install and open
- After obtaining the local candidate ZIP, check its version, size and SHA-256. There is no public distribution link yet.
- Use the candidate installer to select a new empty version directory and preserve the previous version and app data. Do not overwrite a running installation.
- Open desktop/Peru.exe in the installed version or its shortcut. Connect to the local service, then open an isolated project folder.
This static website does not start a local service, read your projects or install software.
Run a task
- Open a workspace and choose or create a project conversation; describe a concrete goal.
- Name reference sources and the output location. Keep references read-only and outputs in the current workspace.
- Review planner, executor and reviewer roles. Codex models come from the current account catalog; unreported client-inherited models remain unknown.
- Inspect scope, validation commands, permissions and budget in preflight. Approve only the actions required for this run.
- Review native execution, actual checks and independent review separately. A “done” reply alone is not acceptance.
Pause and reconcile
Pausing first stops future dispatch. The original native receipt determines whether the current turn has stopped; wait for real quiescence before editing.
Reconcile the original run, session, turn and logs when results are unknown. Do not submit the same goal again to guess success. Failure, missing permissions or receipts can leave work safely waiting.
Resuming does not reset calls, failures or deadlines. Extending time is a separate explicit authorization and does not increase the original call allowance.