Connecting an app
Connect an account once, confirm Panda can use it, and know what to check when it does not connect.
How-to guide Updated 18 Nov 2026What you get
A connected app gives Panda that app's actions in every chat, and a live tab beside the chat where you watch it work. You connect an account once. Afterwards you decide, action by action, what Panda may do on its own and what it must ask about first.
Connect an app

- Open Customize in the sidebar and pick Apps.
Yours lists what you connected and the built-in apps. Explore lists everything there is to connect. - Pick the app on Explore.
Google apps and Microsoft apps are grouped: the Google and Microsoft pages each list their apps under one sign-in. Tick the apps you want and one consent connects them all. - Sign in, or paste a token.
Most apps use OAuth: you sign in on the provider's own login screen and PandaOS receives a scoped token, with no keys to copy. Developer services such as Supabase and Vercel take an access token you generate in their settings and paste in. Jira takes your email, an API token and your site URL. - Look for the check mark beside the app on Yours.
The app's page says Connected as and your account. Apps that need no account, such as Git, say Built in on their page. Either way you connect once per account.
What you see when it worked
Ask Panda for something the app does, such as what is in your inbox. The app's tab opens beside the chat while Panda works, because Spotlight is on by default. Gmail, Google Calendar, Google Tasks, Google Drive and Google Chat can hold several Google accounts, added with Add account.
If it does not connect
- The app is marked Coming soon on Explore. Confluence, Google Analytics and Google Ads cannot be connected yet.
- The account connected but Panda cannot use the app in your project. Supabase, Vercel and other project-scoped apps stay inactive until you link the project to a resource, in the app's panel or on its page. See Apps linked per project.
- Anything else. Troubleshooting covers what to check and what to send if it is broken.
The Tools setting
Every connected app has one, on its page in Customize, Apps, in the column on the right. It decides whether Panda has the app's tools.
- Always ready. The tools sit in every chat.
- When a chat needs them. They load only when a task calls for them, which keeps chats lighter.
- Off. Panda cannot use the app. The account stays connected.
Per tool
On the same page, under What Panda can do, each tool sits at one of three levels.
- Auto. Runs when the task calls for it. Right for reading.
- Ask. Waits for you every time. Right for sending and deploying.
- Off. Panda cannot see or use it. Switch it back to Auto or Ask at any time.
Ask is the useful middle: Auto for reading, Ask for anything that leaves the building, an email or a deployment.
Whether the app's tab opens while Panda works is a separate Spotlight switch on the same page, see Spotlight.

Connect an app on a machine
On a remote machine, a cloud or server computer PandaOS runs for you, open the machine app and choose Connections. Under Apps, press Send beside the account you want to use there. For token-based apps such as Supabase and Vercel, that account's token is copied to the machine. A check mark beside the account means the machine has verified it. Project links travel separately with the project; send the project first if its row asks you to.
A browser sign-in is separate from a token transfer. Where the machine offers Sign in, authorize its own login. Your desktop browser login and refresh token are not copied. An app without a supported machine sign-in stays unavailable with a reason.
Disconnecting an app on this computer leaves its machine copy connected. Use Disconnect on that machine's account row to remove the copy there. Desktop-only connections, such as the local 1Password app, stay on this computer.