20 stable releases
|new 1.1.9||Jun 5, 2023|
|1.1.8||May 25, 2023|
|1.0.5||Apr 30, 2023|
#40 in Web programming
491 downloads per month
Google Bard CLI
A simple command line interface for interacting with Google Bard, written in Rust.
This CLI allows you to save chat history as a Markdown file at a specified absolute or relative path in realtime
and handles graceful exit with Ctrl+C.
You need to have Rust and Cargo installed on your system. If you don't have them, you can install them from the official Rust website.
Install from cargo.
cargo install bard-rs
Clone the repository to your local machine:
git clone https://github.com/Alfex4936/Bard-rs
Change the working directory:
Build the project:
cargo build --release
The executable binary file will be located in the
Before using the Google Bard CLI, you need to obtain your session cookie. To get the session cookie, follow these steps:
- Go to Google Bard in Chrome.
- Open Chrome Developer Tools (F12 or
Ctrl + Shift + I).
- Go to the "Application" tab.
- Under "Storage" > "Cookies", click on "https://bard.google.com".
- Find the cookie with the name
__Secure-1PSID, and copy its value. (it includes "." usually)
Now you can use the Google Bard CLI:
-m(if present, it'll print other Bard's responses for your prompt),
-p(if present with path, it'll save your chat history as markdown.),
-e(if present with .env file location, it'll use that session cookie)
It'll save as your first prompt message. (eg: "Hey yo" -> bard_hey_yo.md)
bard-rs --session <your_session_cookie> --path ./
<your_session_cookie> with the value you copied from the Developer Tools.
If you don't want to save the chat history as a Markdown file, skip
bard-rs --session <your_session_cookie>
If you don't want to pass that long session in terminal, use
bard-rs -e .env -p ./
If you prefer not to specify a path,
bard-rs will automatically search for the .env file in the following locations: the argument-provided path, the current working directory, and the directory of the bard-rs binary.
-p is still required if you want to save the chat history as markdown file.)
above command is same as
bard-rs -e .env
.env file must contain
SESSION_ID key. (the keys being used for the
-s value and
SESSION_ID are identical, they are both derived from
echo SESSION_ID=... > .envmight cause encoding problem that
dotenvcannot read and end up causing no session key error.
- Type your message and press Enter to send it to Google Bard.
!resetto reset the conversation.
!exitto exit the CLI.
!showto see other Bard's answers for your last message.
This project is licensed under the MIT License.
- acheong08 - Inspired by this Python version.