Skip to main content
You’ve completed the quickstart and the bot is running. This guide covers the optional features you can enable next.

Google OAuth

Google Tasks, Calendar, and Gmail integration requires OAuth credentials from Google Cloud Console.
1

Create a Google Cloud project

Go to the Google Cloud Console and create a new project (or use an existing one).
2

Enable APIs

Enable the Google Tasks API, Google Calendar API, and Gmail API in the project’s API library.
3

Create OAuth credentials

Go to Credentials, click Create Credentials > OAuth 2.0 Client ID, and select Desktop application as the type. Download the credentials JSON.
4

Save the credentials file

mv ~/Downloads/client_secret_*.json ~/.ollim-bot/state/credentials.json
On first use of any Google service, ollim-bot opens a browser window for consent. The authorized token is saved to ~/.ollim-bot/state/token.json and reused automatically. Expired tokens are refreshed without interaction.
ollim-bot requests these OAuth scopes: tasks, calendar.events, and gmail.readonly. If scopes change after a code update, delete ~/.ollim-bot/state/token.json to re-consent.
See Google OAuth setup for a detailed walkthrough with screenshots.

Timezone

ollim-bot auto-detects your system timezone. If that doesn’t match where you are, set it explicitly:
.env
OLLIM_TIMEZONE=America/New_York
This affects all timestamps — scheduling, Google Calendar, Gmail, session history, and the system prompt.

Environment variables

The three required variables (DISCORD_TOKEN, OLLIM_USER_NAME, OLLIM_BOT_NAME) are covered in the quickstart. See the Configuration reference for all optional variables and their defaults.

Data directory

All persistent state lives in ~/.ollim-bot/, which is auto-created on first run and managed as a git repository. See Data directory for the full layout.
Back up ~/.ollim-bot/ to preserve your routines, reminders, session history, and Google credentials. Since it’s a git repo, you can push it to a private remote.

Next steps