---
title: "Remote Control"
id: "660"
type: "page"
slug: "remote-control"
published_at: "2026-06-07T17:50:40+00:00"
modified_at: "2026-09-21T01:36:28+00:00"
url: "https://xedant.com/agents/agent/docs/remote-control"
markdown_url: "https://xedant.com/agents/agent/docs/remote-control.md"
excerpt: "Remote Control lets other programs drive Xedant Agent for you — no browser needed. There…"
---

# Remote Control

[https://xedant.com/agents/agent/docs/remote-control.md](https://xedant.com/agents/agent/docs/remote-control.md)

Remote Control lets other programs drive Xedant Agent for you — no browser needed. There are two ways: an **HTTP API** (a standard way for programs to talk to each other) — creating chats, sending prompts, managing the queue, and live SignalR events (real-time updates pushed to your program); and a **file queue through Yandex.Disk** (AgentRemote) — exchanging files that carry tasks and transcripts. The HTTP side has a page of its own, [API](/agents/agent/docs/api)
: authentication with a key, every `/api/remote` command, the prompt queue, the bot list, the wider set of endpoints the same key unlocks, and live event updates. This page covers the file-based way through Yandex.Disk.

## Remote Control through Yandex.Disk (AgentRemote)

Xedant Agent can work as a “file queue” through **Yandex.Disk**: drop a file with a task into the folder — the agent creates a chat, does the work, and puts the finished transcript back. You can steer the agent from any device that has Yandex.Disk, with no web interface and no SSH. A separate desktop app, **AgentRemote** (Windows), is built on the same mechanics: it watches the folder on Disk and shows chats and messages in a friendly interface.

**How it works**

1. Turn the feature on: set the `AGENT_YANDEX_DISK_TOKEN` environment variable (your Disk OAuth token) — a background monitor starts by itself and begins watching the folder.
2. Drop a `.txt` file with a task into the folder root — it joins the queue and is processed in order. A numeric prefix in the file name (for example, `01-fix-auth.txt`) sets that order. Each prompt gets its own chat.
3. For follow-up messages, drop a `.txt` file inside the chat’s own folder (a subfolder named after the chat number) — it runs next in that chat.
4. Transcripts are saved back to Disk as `.md` files, one next to each prompt. Autofix runs are logged the same way, as `autofix-*.txt`/`.md` files.

**Environment variables**

- `AGENT_YANDEX_DISK_TOKEN` — your Yandex.Disk OAuth token; setting it turns the feature on;
- `AGENT_YANDEX_DISK_FOLDER` — the root folder of the queue (defaults to `app:/Yandex.Disk`);
- `AGENT_YANDEX_DISK_POLL_INTERVAL` — how often to check for new files, in seconds (defaults to `10`).

For programmatic access to chats, prompts, and the queue over HTTP, see the [API](/agents/agent/docs/api)
 page.

**[← .xedant Folder](/agents/agent/docs/xedant-folder)**

**Next:** [Telegram Bot](/agents/agent/docs/telegram)
 →