> ## Documentation Index
> Fetch the complete documentation index at: https://docs.axottle.com/llms.txt
> Use this file to discover all available pages before exploring further.

# WARP in Flow

> Local SOCKS Proxy and Native WireGuard: Configuration, Verification and Limitations

The WARP block supports two runtimes, and the selected settings are incorporated into the application plan and the Agent configuration on Apply.

| Backend | Release Xray | Check runtime |
| - | - | - |
| `cloudflare_proxy` (default) | Local SOCKS proxy, usually `127.0.0.1:40000` | Cloudflare client and local proxy port |
| `native_wireguard` | Out via WireGuard interface, by default `warp` | Interface WireGuard and Cloudflare trace via it |

For native mode, the installer supports Debian/Ubuntu with `apt-get`.
systemd and amd64/arm64 architecture. It installs WireGuard, downloads.
a fixed version of `wgcf` with SHA-256 verification and launches
`wg-quick@<interface>.service`. Interface name - 1-15 ASCII-letters, numbers,
Dots, accents or hyphens.

The configuration is stored in `/etc/wireguard/<interface>.conf`, registration -
in `/var/lib/axottle-agent/warp-native`. Installer refuses to overwrite
existing config without Axottle control marker. `Table = off` retains
system routing table; Xray directs the desired outbound through
`sockopt.interface`.

Native Installation Success Requires an Accessible Interface and Cloudflare Response
trace from `warp=on` or `warp=plus`. One open SOCKS port for this
Update the Agent and its helper before using it.
new backend.

Health only takes WARP into account where it is required by the route used.
For native mode, the corresponding `wg-quick` is checked, not the mandatory one.
presence of `warp-svc`. If there is no service or route information, no
Measurement is not considered a successful test.

## Verification

Check the selected backend and node in the plan, complete the Agent installation
and the result of the diagnosis is the branch with WARP. In native mode, check
The work of the selected interface. Green check of the next branch of the route
It does not confirm that the desired exit traffic passes through WARP.

## Rollback

Return the previous block settings or the previous verified version of Flow
And do the usual application. Check the result and the client's route.
Removing the block from the canvas does not in itself mean removing the installed
WireGuard or Cloudflare client from the node. remove them manually only after
Check that other Flow users are no longer using this runtime.

Capabilities depend on the installed build; live network run within this reconciliation was not performed.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.