Local Transfer Without Cables: Send Files Between Your Devices

Weerocks — Mon, 26 Oct 2026 10:02:09 +0000

Moving files between your own devices should be simple. However, many people still rely on USB cables, cloud storage, or messaging apps to transfer photos, documents, and project folders.

A better option is local transfer: sending files directly between devices connected to the same Wi-Fi or Ethernet network.

In this tutorial, we will use LanSender to transfer files between computers and mobile devices without uploading them to the cloud.

Why choose Local transfer?

Local transfer has several advantages:

No USB cable is required
Files do not need to be uploaded to a cloud service
Large folders can be transferred directly
No account or password is required
Transfers work across Windows, macOS, Linux, and Android

This is especially useful when you want to move photos from your phone to your computer, share project files with a colleague, or migrate data from an old PC.

Step 1: Install LanSender

Download and install LanSender on the devices you want to connect.

The application supports Windows, macOS, Linux, and Android. After installation, open the app on both devices and connect them to the same local network.

A Wi-Fi connection is usually enough. Ethernet also works well, especially when transferring large files.

Step 2: Find another device

When both devices are running LanSender on the same network, they should appear automatically in the device list.

You do not need to enter an IP address or set up port forwarding. Select the device you want to communicate with and open a conversation. This conversation supports both text messages and file sharing.

Step 3: Send files or folders

You can send:

Photos and videos
Documents
Project files
Multiple files
Complete folders with their original structure preserved

Choose a file or folder, then click Send. The receiving device will show a transfer request. The recipient can review it and decide whether to accept.

This gives you more control than sending files through random chat groups or temporary file hosting websites.

Troubleshooting local transfer

If devices cannot discover each other, check these points:

Both devices are connected to the same Wi-Fi network.
LanSender is open on both devices.
The router does not enable wireless client isolation or guest isolation.
The operating system firewall allows LanSender’s network traffic.
No VPN is routing traffic into a separate network.

For large transfers, keep both devices powered up and avoid switching your mobile device to another network mid-transfer.

Direct and private file sharing

LanSender sends messages and files directly between devices over an encrypted connection. There is no cloud relay, so your files do not need to be stored on a third-party server first.

The recipient controls whether to accept incoming files. Files with identical names are not automatically overwritten, helping you avoid accidental data loss.

Final thoughts

Local transfer is a practical solution for everyday file sharing. It is fast, private, and easier to manage than cables or cloud storage when your devices are nearby.

If you frequently move files between your phone and computer, or across different operating systems, LanSender lets you chat and share files within the same app.

You can download it for free from lansender.com.

Give Your AI Agent Eyes and Hands on a Remote Desktop with rdp-cli

Weerocks — Thu, 22 Oct 2026 07:35:57 +0000

AI agents are good at generating text and calling APIs. But many real-world tasks still require interacting with graphical applications: editing a video, checking a spreadsheet, using legacy Windows software, or operating an Android phone.

rdp-cli provides a simple command-line workflow for letting an AI agent control RDP and VNC desktops—and verify every action through screenshots.

1. Install rdp-cli

On Linux x86_64, download the executable and make it runnable:

chmod u+x ./rdp-cli-linux-x86_64
./rdp-cli-linux-x86_64 --help

No additional runtime or administrator access is required. For Windows and macOS, see the quick start guide.

2. Connect to a Windows RDP session

Make sure RDP is enabled on the target computer. Then connect with your username and password:

IFS= read -r -s -p 'Password: ' rdp_password
printf '\n'
printf '%s' "$rdp_password" | \
  ./rdp-cli-linux-x86_64 connect \
  --host 192.0.2.20 \
  --user USER \
  --password-stdin

unset rdp_password

The command returns a session identifier. Save it as SESSION for the next steps. The password is passed through standard input rather than being written directly into the command line.

3. Let the agent see the desktop

Before taking an action, capture the current screen:

./rdp-cli-linux-x86_64 screenshot \
  --session SESSION \
  --out ./before.png

An AI agent can inspect before.png, locate a button or input field, and decide what to do next. This observe → act → observe pattern helps the agent verify the current state after every action.

4. Click, type, and verify

After locating an input field at coordinates X, Y:

./rdp-cli-linux-x86_64 click \
  --session SESSION \
  --desktop \
  --x X \
  --y Y \
  --observation OBSERVATION

./rdp-cli-linux-x86_64 screenshot \
  --session SESSION \
  --out ./focused.png

./rdp-cli-linux-x86_64 type \
  --session SESSION \
  --text "Remote task completed." \
  --observation NEW_OBSERVATION

./rdp-cli-linux-x86_64 screenshot \
  --session SESSION \
  --out ./after.png

The agent can inspect the final screenshot instead of assuming the command succeeded.

5. Watch or take over when needed

A person can open the same session in a native window or browser:

./rdp-cli-linux-x86_64 watch \
  --session SESSION \
  --viewer window

The viewer starts in read-only mode and supports pausing agent input, taking control, and handing the session back.

Why this workflow matters

With rdp-cli, an AI agent can work with existing desktop applications and remote environments without requiring a new API integration for every tool.

The basic loop is simple:

Connect → Screenshot → Act → Screenshot → Verify

Try the complete setup at rdp-cli.com.

Always use authorized computers and trusted networks. Review the connection and certificate settings before using rdp-cli in production.

DEV Community: Weerocks