# One-click adaptive window arrangement

Arrange the windows of running browser profiles on screen.
- **Where it runs**: the MoreLogin desktop client handles this entirely on your machine. There is no server-side implementation, so there are no account, team or state preconditions beyond the client having the profile open, and nothing is recorded in the cloud.
- **Effect**: limited to local browser processes and windows. Profile data, fingerprints and cloud cache are untouched.
- **Completion**: synchronous — the client answers once it has acted.
- **Availability**: Local API only. There is no Open API equivalent, because the Open API has no local browser to operate on. Use the cloud runtime endpoints instead.
- **Note**: because the client owns this, the response shape depends on the installed client version rather than on a service contract.

Endpoint: POST /api/env/arrangeWindows
Version: 2026-09-05

## Request fields (application/json):

  - `arrangeType` (integer)
    Arrangement type: 1 for Tiled, 2 for Stacked, defaults to Tiled if not specified

  - `envIds` (array)
    Environment IDs, if not specified, all environment windows are selected by default

  - `screenIds` (array)
    Screen IDs, array type, if not specified, arrange on the screen where the mouse cursor is located

## Response 200:

  - `200` (unknown)
    Standard response envelope. Success is reported through `code`; this operation does not document an additional payload.

## Response 200 fields (application/json):

  - `code` (integer, required)

  - `msg` (string | null, required)
    Error message; null on success

  - `requestId` (string, required)
    Unique request identifier; include it when contacting support