The local runtime
Understand the server-backed path used by the visual workspaces and the dependencies it needs.
Start the agent server
The root start:server script launches the Python agent server. It expects the configured project environment. Run it from the repository root after completing the branch's setup instructions.
pnpm start:serverConnect the intended interface
The web and desktop workspaces use the server-backed runtime. A running server is one dependency, not the entire setup: the interface must point at the intended runtime, and that runtime must be able to reach the configured model service.
Package-specific interface launch commands can change. Use the scripts and README for the package you are evaluating instead of assuming the Python CLI flags apply everywhere.
Keep development local
The development runtime uses a localhost endpoint. Keep it local unless you deliberately configure and review a different deployment. Exposing a development server is a separate security decision, not a routine step in this guide.
A local application can still send data to a remote model or connector. Inspect those settings before working with private repositories.
A run is more than a response
The runtime records state, tool observations, approval decisions and verification. The model proposes language and actions; that proposal is not the sole authority on what may run or what counts as complete.
Completion checks depend on the evidence collected. An incomplete test can leave an important behavior unverified even if the process itself succeeded.