SlashBots mobile: approve your PC's AI agents by phone

In short

The SlashBots phone app pairs with the SlashBots desktop app. From the phone you chat with the PC's bots, allow or deny the commands they want to run, answer their questions, stop a task, and edit bots, routines, memory, skills, rules and projects. The bots and models stay on the PC. The phone sends commands to an encrypted relay in Frankfurt that the PC calls out to, so nothing on the internet can reach the computer. Screens and video come from a test build with a sample PC.

Client: SlashBots · Phone app
Sector: AI agents, mobile
Where: Bogotá, Colombia
Year: 2026
Deliverables: Flutter app for Android and iOS
QR and code pairing, confirmed on the PC
Relay server with encryption at rest
Push notifications for approvals and questions
10 languages, Arabic RTL included
Services: Mobile apps
AI agents

137desktop actions mapped

152app tests

10languages

The context

Bots that wait when nobody is at the PC

SlashBots bots browse, write files and use the computer. In the Balanced permission mode, the desktop app asks before commands, code, desktop control and anything that sends or posts. When nobody is at the PC, a long task stops on that question and waits. Routines and settings could only be changed at the desk.

The team asked for the phone to do everything the PC does. We took that literally, except for anything that touches secrets, which stays on the computer.

Design and build

Every desktop action, checked one by one

We listed all 137 actions of the desktop app and decided, for each one, whether it runs from the phone as a command, arrives as synced data, or stays on the PC on purpose. Password vault contents, API keys, model providers and connector credentials never leave the computer; the phone can lock the vault but not open it. A script compares that table with the desktop code, so a new desktop feature shows up as a gap before a release.

Pairing starts on the PC, which shows a QR code and an 8-character code that works once and expires after 10 minutes. The phone claims it, and the PC asks whether to allow that phone, next to a 4-digit match code that must be the same on both screens. Nothing is linked until someone clicks Allow at the computer, so a code seen in a screen share is useless on its own.

The desktop app never opens a port. It makes outbound HTTPS calls to the relay, checks a small doorbell file in object storage every 3 seconds and syncs only when it rings, so an idle PC causes no database queries. Messages, cards and commands are encrypted at rest with AES-256-GCM. Push notifications carry generic text (“Operator needs your OK”), so no chat content goes through Apple or Google. Private chats are not relayed.

Test build: allow a command, open the running task, read a chat, then the inbox, Manage, routines, bots and settings. Sample PC.

01
Approve from anywhere

The card shows the exact command, such as a dir on the Documents folder, with Allow once, Always for this task and Deny. The PC records that it was allowed from a phone.
02
The full composer

Auto, Fast, Expert and Heavy modes, a model and reasoning level per message, @mentions, commands such as /browse and /remember, and attachments from the camera or files.
03
The PC stays in charge

A phone command has the authority of a click in the desktop app, within the PC's permission mode and its switches for allowing tasks and approvals from the phone.
04
Several computers

One phone pairs with several PCs, renames and unpairs them; an optional account keeps them when you change phones.

Gallery

The project in pictures

8 images · Open any image to see it full size.

Home: “Needs you” with an approval card, the running task with a stop button, the PC's bots and recent chats.

Inside the running chat, Operator asks to use run_command; the composer shows it is working, with a Stop button.

A chat with SlashBot: the answer is generated on the PC and synced to the phone.

New chat: pick the bot that answers and an optional project; the Auto, Fast, Expert and Heavy modes sit above the composer.

Inbox: everything waiting for you, with the same Allow once, Always for this task and Deny buttons.

Manage: bots, routines, memory, skills, rules, projects and the SlashBots folder of the paired PC.

Routines: a weekday morning brief at 08:00, with an on/off switch and Run now.

Computer: the PC's status and model queue, Stop everything, pairing another PC and the permission mode set on the PC.

Outcomes

Tested end to end against a real desktop

We paired an Android build with SlashBots desktop 1.2.6 running in an isolated profile. A message reached a bot and the model's answer came back; a run_command approval allowed from the phone created the file on the PC; a question was answered from the phone, and a memory added on the phone landed in the PC's memory. The phone also read a real desktop sync of 579 items with nothing dropped.

The app has 152 tests. All 19 screens render in English, right-to-left Arabic, German at 200 % text and Japanese in dark mode, and the accessibility guidelines (tap targets, labels, contrast) are checked on the main screens. A demo PC with sample replies lets someone try the app before pairing.

137 desktop actions mapped: each runs from the phone or stays on the PC on purpose
8-character pairing code, single use, 10 minutes; 4-digit match code confirmed on the PC
AES-256-GCM at rest, server in Frankfurt, no analytics, no ads
Screens and video: test build with a sample PC and invented chats

Frequently asked questions

The questions we hear often

Does the phone app run the AI?

No. The bots and models run on the PC in SlashBots desktop. The phone sends messages and commands, and the server that relays them calls no model.

Can someone take over my PC by seeing the pairing code?

Not with the code alone. Once a phone claims it, the PC shows a 4-digit match code and asks you to click Allow; nothing is linked without that click. The 8-character code works once and expires after 10 minutes.

Do my passwords reach the phone?

No. The password vault, two-factor codes and API keys stay on the PC. From the phone you can only lock the vault.