Set up the workflow
Start from a failing behavior or a specific improvement. Give the local agent the smallest relevant scope and ask for evidence from the changed surface.
Keep the decision reviewable
Review the diff, run the project checks and distinguish local success from a later deployment.
Assess the result
A useful completion record identifies the changed files and the checks that passed. Optional cloud automation is separate from ordinary CLI and web conversation.
A practical starting point
Use the local agent for a bounded development task. These steps describe the GoCux workflow and its permission boundaries.
- Connect the customer CLI through the supported device flow and choose a specific local repository or working directory. Preserve unrelated files and existing work.
- Give the local agent a concrete goal and review its tool permissions. The CLI owns its local terminal, tool and MCP loop; model routing sits behind GOCUX Gateway.
- Read the resulting diff and run the checks appropriate to the changed surface. Keep local verification separate from any later publishing or deployment action.
What to verify
A useful completion record identifies the changed files and the checks that passed. Optional cloud automation is separate from ordinary CLI and web conversation.
Bring this workflow into your workspace.
Set the scope. Review the evidence. Approve the steps that need it.