Turn (almost) any CLI program into a Tox bot
git clone git://
Log | Files | Refs | README | LICENSE (4115B)

      1 # toxio: turn (almost) any CLI program/script into a Tox bot
      3 Toxio is a small Nim program that aims to do one thing: wrap any line-oriented CLI program or script to be able to communicate with it via the [Tox]( network. Toxio spawns any shell command of your choice as a subprocess and redirects your messages to its standard input and its output lines to the chat replies.
      5 ## Building
      7 To build toxio, you obviously would need a working Nim compiler, as well as [toxcore]( library and [nim-toxcore]( package installed. The latter is available using Nimble package manager (`nimble install toxcore`). You will also need any POSIX-compatible `make` command, although nothing prevents you from compiling the `toxio.nim` file manually.
      9 Once you have all dependencies sorted out, just run `make` in the project directory. If everything is successful, a `toxio` binary file should appear.
     11 ## Usage
     13 The overall command syntax is like this: `toxio [bot_name] [save_file] [r|w] [cmd]`. Now, let's go through the stages to set up your bot.
     15 ### 1. Obtain a Tox save data file
     17 First, you will need an existing toxcore-compatible save file. For safety reasons, toxio does not create any save files, you have to supply it externally. They may or may not already have friendlists, but if they do, beware that all the friends will have the access to the process running inside your bot. Thus, it's recommended to create a new profile save file (it must be unencrypted) in a client like Toxic and then use it solely for the purposes of this bot.
     19 ### 2. Add the bot users as friends
     21 Now that you have your save file (e.g. `save.tox`), you should run toxio in the **write-enable** mode with the `w` command line parameter and a dummy command like `cat` (which will essentially make toxio function as an echo bot for you to test it):
     23 ```
     24 toxio "My new bot" /path/to/save.tox w cat
     25 ```
     27 In the write-enable mode, the bot accepts all friend requests and saves them to your save file. This mode must only be used for initial set up and testing phase, never for normal usage!
     29 After running, the bot will print out its Tox ID that you can use to add as a friend to all your Tox identities you need to use the bot from. After you added this bot as a friend to every required ID, terminate it with Ctrl+C and make sure your save file is backed up in a safe place.
     31 ### 3. Run the bot normally
     33 Now, you can run the bot normally (in the **read-only** mode) like this (where "My new bot" is just its displayed name and `"cmd"` is the command line you need to run):
     35 ```
     36 toxio "My new bot" /path/to/save.tox r "cmd"
     37 ```
     39 When toxio gets online, every connected friend will be able to communicate with the subprocess using the chat with this bot. The status message will display the command line of the process the bot is currently serving.
     41 Keep in mind that you only start getting the program's output if you initially send a message. What to do with your messages is fully up to the program.
     43 You can also pause the program's output. If you run, for instance, some monitoring service and want to temporarily stop receiving messages from the bot, just send `/toxiostop` to it. The output will resume automatically whenever you send any other message.
     45 ## Limitations
     47 - Text messages only.
     48 - Single subprocess per bot by design. This means that every connected friend will communicate with exactly the same subprocess and receive identical output from it.
     49 - The program's output must end with newline characters.
     50 - Every output line is sent as a separate message.
     51 - The stdout and stderr streams are merged. This is hardcoded: find `poStdErrToStdOut` option in the `toxio.nim` file and remove it if you don't need this behavior.
     52 - You need an external client to initially set up the bot's Tox ID and generate the save file.
     53 - Only one DHT bootstrap node hardcoded for now.
     54 - Only tested on Unix-like OSes, compatibility is not guaranteed for others.
     56 ## Credits
     58 Created by Luxferre in 2024, released into public domain.
     60 Made in Ukraine.