Choose the coding environment
Retvest Code covers repository work through the app and Retvest terminal. Native local execution uses the employee’s operating-system authority; a server worker has a different isolation boundary. Select the intended environment, project root and tools for the task.
Scope the repository context
Identify the task, relevant instructions and files that may be changed. Preserve existing local edits. The model’s context window and the selected client’s limits affect how much material can be considered; an omitted file must not be treated as reviewed.
Make commands deliberate
Permission to inspect a file is not permission to run every command. Review the exact command, directory, network access and expected effects. Company API permissions and local operating-system permissions are separate boundaries.
Review changes before accepting them
The coding workflow requires visible changes, meaningful execution outcomes and a way to reason about checkpoints or undo. Proposed code must be distinguished from a successful run. The product’s general coding quality and complete installed recovery are not yet qualified.
Reconcile uncertainty
An interrupted command may have changed files even if its response was lost. Read the retained operation outcome and current workspace before repeating a write. Do not overwrite unrelated changes to make an AI task appear successful.
Record the authorised workflow
Agree capture of the acting identity, task, permitted project context, approval, command or edit attempt and result. Access to coding records must respect the same source and workspace boundaries.