PandaOSPandaOS
Apps and integrations

Your app

Live with an app you built: change it in its own chat, decide what it may do, and delete it when you are done.

Feature Updated 18 Nov 2026

One app on Community

Community includes one app, or any number during a one-time 30-day trial. On the other plans you build as many as you like.

What your app is

Your app is a small tool you built with Panda. An example is a desk that lists bug reports and answers every affected customer with one button. It lives in your dock, uses the accounts you already connected, and is never published anywhere. This page is about using one. To build one, see Apps you build yourself.

Where to find it

Your app sits in the dock. In Customize, under Apps, it is listed in Your PandaOS apps, and that is where its page opens.

On the page, Dock decides whether the app shows in the dock with Show in the dock, and Opens in picks Sidebar or Full screen. The page also holds the app's Automations, its Notifications, the AI model it uses and Where it works.

Its own chat

Every app has a chat of its own, and that is where it changes. Press Edit in chat on the app's page, or the pencil in the app's header when it is open beside a chat. Right-clicking it in the dock offers Edit in chat too. Say what should be different, and Panda builds it there. Edit goes back to the app's edit chat from today when there is one, so one day's changes stay in one conversation.

When the app needs something it was not given, it asks in that chat with a card. The card says the app "would like to", with a switch per item, then Allow or Not now. Whatever you allow can be changed later on the app's page.

Setting it up

When an app is missing a connection or a setting, a row at the top of the app offers Set up. It opens the app's chat. There Panda helps you connect the accounts the app needs, fill in its settings and turn on the automations it offers. Requests for access still wait for your yes. An app can also offer a setup button of its own.

For an app your organization shared, setup changes only your own configuration, not the app the organization published. Edit in chat then offers Just set it up or Make it my own. Make it my own copies the app with your access, settings and automations, and opens the copy's edit chat.

What it may do

Two sections on the app's page decide this.

  • Connections lists what it may use: your connected apps, integrations, the web, APIs and folders. It asks in its chat before it uses anything else.
  • Actions lists what it can do, each set to Auto, Ask or Off. Reading runs on its own, and changing asks you first unless you set it to Auto. Available in other chats decides whether your other chats may use the app's actions too. Off, only its own chat and its automations can.

These choices are kept outside the app's own files, so the app cannot give itself more access.

Skills and rules

An app can carry know-how a chat would otherwise have to guess. Examples: how to read a symptom score, what counts as a flare-up, or how you like a report laid out. It keeps that as its own skills and rules, under Skills and rules on the app's page.

  • A skill is know-how Panda reads before it uses one of the app's actions, when the action alone is not enough to use it well.
  • A rule is one short line Panda always follows while it uses the app, for example "Scores run from 0 to 10". A rule holds up to 300 characters, and all rules together up to 1,000. Anything longer belongs in a skill.

They apply only while the app is in play. That is its own chat, its AI, and any chat that uses one of its actions. They never become part of a project, and a project's own rules win over an app's. They live in the app's folder, so they travel with the app when you move or share it.

Press Add in the section to write one, and use the buttons on a row to edit or delete it, at any time. The next chat that uses the app already knows the change. The app's chat can also write them for you, and does so on its own when an action needs more than its description.

It asks before it acts

When the app wants to do something set to Ask, PandaOS shows Permission Required with Allow and Deny. Always allow appears too when it runs in a project. Sending email always asks, even when the action is set to Auto, so nothing leaves your mailbox without your yes.

What it remembers

An app keeps what it needs between runs in its own storage, for example which customers were already told. An app that works per project keeps a separate store in each project and never reads another project's.

Delete it

On the app's page, Delete this app removes the app, its files and its automations. PandaOS asks first, because this cannot be undone. An app your organization shared with you cannot be deleted there.