Local and cloud are separate routes

Local and cloud are separate Agent RX routes in Mandarin. Select the route intentionally; opening the panel or seeing a previous answer does not prove the next request will use the route you expect.

Change routes only while idle

1. Inspect the active turn and queued requests.
2. Finish or stop the active turn, then remove waiting requests you do not intend to run. Preserve their task details first if needed.
3. With the panel idle and the queue empty, choose Use local or Use cloud.
4. Check the selected route before sending the next request.

Local mode needs a compatible local model server. Cloud mode has its own configuration and data boundary. Do not paste provider credentials into the request to establish either connection.

Failure is not permission to reroute

If a local request fails, inspect the error and the intended local server configuration. The documented behavior does not silently fall back to cloud. Choosing cloud yourself is a separate decision about processing the next request, not an automatic recovery step for a local error.

A route label identifies a choice; a successful response establishes that a particular request returned. Neither establishes that a proposed edit was accepted, saved, or tested.

Keep context bounded

Keep project code in files and ask for targeted reads. Older conversation and large outputs are not a promise of permanent model memory. If a crucial constraint must apply to the next turn, state it clearly in that turn and inspect the resulting work.

The editor/agent concept describes the request lifecycle. Review privacy and permissions when deciding what project information can cross a model boundary; a local file and a model request are distinct actions.