OWNER ACCESS
Your assistant, your choices.
Sign in to connect your accounts and choose how your assistant reasons.
Each person uses a separate PA instance. Your accounts, credentials and database belong to this instance.
CONNECT YOUR ACCOUNTS
Make this assistant yours.
Start with a model and Telegram. Google and Maps are optional. Keys stay encrypted on the server and are never shown again.
1 · Add a reasoning provider
2 · Connect your Telegram bot
Create a dedicated bot with Telegram’s @BotFather. Send your new bot a message first, then add its token and your numeric Telegram user ID.
3 · Connect Gmail and Calendar
In Google Cloud, create a Web application OAuth client, enable Gmail and Calendar APIs, and add this exact authorized redirect URI:
For an external app in Google’s testing mode, add your account as a test user. Google may expire test-mode refresh tokens after seven days; publish or reconnect as appropriate.
Google asks for read access and account identity. This connection cannot send mail or create calendar events.
4 · Add Google Maps
Use a separate server API key with Routes API enabled. Restrict it to Routes API and your server IP. Configure quotas and billing alerts in Google Cloud.
5 · Save another API or MCP connection
Store connection details for a future integration. Saved connections remain disabled until a reviewed adapter and permissions are available.
PROVIDER SETTINGS
Choose how PA reasons.
New runs use your latest settings. A running conversation keeps the configuration it started with.
OBSERVABILITY
See what actually ran.
| Started | Workload | Status | Provider / actual model | Usage | Failure / fallback |
|---|