PandaOSPandaOS
Account and help

Credentials

See the secrets in your project's .env files, and decide for each one whether Panda may read or change it.

Feature Updated 20 Nov 2026

Warning: Read and Full show Panda the value

When Panda reads a variable, the value is part of the chat from then on. Keep a secret Panda does not need at None.

What Credentials is

Projects keep their secrets, such as API keys and passwords, in .env files: plain text files with one NAME=value line per secret. Credentials lists those files with the values hidden, and lets you decide for each variable whether Panda may see it. Use it when Panda needs a key to do its job, or to make sure it never sees one.

Where to find it

Open a project and press Credentials in the dock. It shows there in projects with coding tools on, and in any project that has a .env file. Pick a .env file from the list at the top. Each file shows its number of variables. If the project has none yet, press Create .env file.

What you can do

  • Add a variable to the open file.
  • Reveal a value, and Hide it again.
  • Edit a name or value, or Delete variable.
  • Filter variables by name.
  • Refresh, after you changed a file outside PandaOS.

Access, per variable

Each variable has its own level:

LevelWhat Panda can do
NoneNothing. It cannot read the value.
ReadRead the value, not change it
FullRead and change it

A variable PandaOS finds in a file starts at None. A variable Panda creates for you starts at Full. When Panda needs a variable it cannot reach, it says so and asks you to change the level here. A task that fails tells you why.

The Access Control switch

Access Control at the top is on from the start, and it is what makes the levels count. Turn it off and Panda can read, write and delete every variable in the project without restriction. The panel shows a warning while it is off.

Credentials in worktrees

A project and its worktrees can share .env files. A folder picker in Credentials switches between the main folder and a worktree. When a worktree has no .env files of its own, the panel says so and shows the main folder's files.

When you change a shared value from a worktree, choose whether the change is for every worktree or only this one. A value for only this worktree stays there, and Use main value removes it again. If a shared file was changed outside the panel, syncing pauses and asks you how to go on.

Limits

PandaOS tells Panda to go through Credentials and never open a .env file directly. On OpenCode, opening one directly is refused. On Claude Code and Codex it is an instruction Panda follows, not a lock.