Bito CLI (Command Line Interface) provides a command line interface to the Bito AI chat functionality. Over time, CLI will add more functions and new command options to support complex automation and workflows.

This is a very early Alpha version. We would love to get your feedback on the new features or improvements. Please write us at [email protected] or [email protected].

Terminal

• Bash (for Mac and Linux)
• CMD (for Windows)

• Execute Chat: Run bito command on command prompt to get started. Ask anything you want help with such as awk command to print first and last column.

  Note: Bito CLI supports long prompts through multiline input. To complete and submit the prompt, press Ctrl+D. Enter/Return key adds a new line to the input.

• Exit Bito CLI: To quit/exit from Bito CLI, type quit and press Ctrl+D .

• Terminate: Press Ctrl+C to Bito CLI.

Check out the video below to get started with Bito CLI

We recommend you use the following methods to install Bito CLI.

sudo curl https://alpha.bito.co/downloads/cli/install.sh -fsSL | bash (curl will always download the latest version)

Arch and Arch based distro users can install it from AUR

yay -S bito-cli or paru -S bito-cli

Note for the Mac Users: You might face issue related to verification for which you will have to manually do the steps from here (we are working on fixing it as soon as possible).

1. Install the Bito CLI through MSI using this installer.
2. On Windows 11 you might get notification related to publisher verification. Click on "Show more" or "More info" and click on "Run anyway" (we are working on fixing this as soon as possbile).
3. Once the installation is complete, start a new command prompt and run bito to get started.

sudo curl https://alpha.bito.co/downloads/cli/uninstall.sh -fsSL | bash (this will completely uninstall Bito CLI and all of its components)

For Windows you can uninstall Bito CLI just like you do for any other software uninstall from control panel. You can still refer the link provided here.

While it's not recommended, you can download the Bito CLI binary from our repository, and install is manually. The binary is available for Linux and Mac OS, x86 and ARM architecture.

1. Download Bito CLI binary specific to your OS platform from here (Please download the latest version for all new updates).
2. Start the terminal, go to the location where your downloaded the binary, move the downloaded file (in the command below use bito-* filename you have downloaded) to filename bito mv bito-<os>-<arch> bito
3. Make the file executable using following command chmod +x ./bito
4. Copy the binary to /usr/local/bin using following command sudo cp ./bito /usr/local/bin
5. Set PATH variable so that Bito CLI is always accessible. PATH=$PATH:/usr/local/bin
6. Run Bito CLI with bito command. If PATH variable is not set, you will need to run command with the complete or relative path to the Bito executable binary.

1. For using bito CLI, always move to the directory containing bito CLI prior to running it.
2. Set PATH variable so that bito CLI is always accessible.
   • Follow the instructions as per this link
   • Edit the "Path" variable and add new path of the location where bito CLI is installed on your machine.

• On MAC/Linux: run ./bito --help or ./bito config --help

• On Windows: run bito --help or bito config --help

• run ./bito – p writedocprompt.txt -f mycode.js for non-interactive mode in Bito (where writedocprompt.txt will contain your prompt text such as "Explain the code below in brief" and mycode.js will contain the actual code on which the action is to be performed).

• run cat file.txt | ./bito to directly cat a file and pipe it to bito and get instant result for your query.

• run cat inventory.sql | bito -p testdataprompt.txt > testdata.sql to redirect your output directly to a file (where -p can be used along with cat to perform prompt related action on the given content).

• run cat inventory.sql | bito -c runcontext.txt -p testdataprompt.txt > testdata.sql to store context/conversation history in non-interactive mode in file runcontext.txt to use for next set of commands in case prior context is needed. If runcontext.txt is not present it will be created. Please provide a new file or an existing context file created by bito using -c option. With -c option now context is supported in non-interactive mode

• run bito – p writedocprompt.txt -f mycode.js for non-interactive mode in Bito (where writedocpromot.txt will contain your prompt text such as "Explain the code below in brief" and mycode.js will contain the actual code on which the action is to be performed).

• run type file.txt | ./bito to take input from file in windows and pipe it to bito and get instant result for your query.

• run type inventory.sql | bito -p testdataprompt.txt > testdata.sql to redirect your output directly to a file (where -p can be used along with type to perform prompt related action on the given content).

• run type inventory.sql | bito -c runcontext.txt -p testdataprompt.txt > testdata.sql to store context/conversation history in non-interactive mode in file runcontext.txt to use for next set of commands in case prior context is needed. If runcontext.txt is not present it will be created. Please provide a new file or an existing context file created by bito using -c option. With -c option now context is supported in non-interactive mode

Use {{%input%}} macro in the prompt file to refer to the contents of the file provided via -f option

Example: To check if a file contains JS code or not, you can create a prompt file checkifjscode.txt with following prompt:

Context is provided below within contextstart and contextend
contextstart
{{%input%}}
contextend
Check if content provided in context is JS code.

Here are two examples for you to see My Prompt in action:

1. How to Create Git Commit Messages and Markdown Documentation with Ease using Bito CLI My Prompt:

2. How to generate test data using Bito CLI My Prompt:

1. Unicode characters (using other languages) might not be readily supported on command prompt if you are on Windows 10 or below. You can run command chcp 936 in cmd prior to using bito to support unicode characters in Windows 10 or below (To undo the settings done here you can follow this link).
2. IF you are on Windows 11 then you shouldn't encounter any such issues.

Copyright (C) 2021, Bito Inc - All Rights Reserved