Docs / Agents

Instructions

Give agents standing team guidance, keep personal preferences separate, and sync your local setup.

Use Instructions for guidance that should apply across conversations, such as how the team reviews changes or where incident reports go.

Team instructions

Open Settings → Instructions. Add a clear, scoped rule and check who it affects before saving. Team instructions are shared with every agent in the team. Keep personal secrets, temporary command output and credentials out of them.

Personal instructions

Open Settings → My preferences → Personal instructions. Keep preferences for your own work here instead of applying them to the whole team. When personal and team guidance differ, make the intended scope clear. Neither can bypass provider permissions or Pangea's access controls.

For work in a repository, keep repository guidance in the files its runtime reads, such as CLAUDE.md or AGENTS.md. Name the repository and working folder in the conversation, so the runtime reads the right files.

Sync my setup

Settings → My preferences → Sync my setup brings your local Claude Code setup into Pangea. It reads the skills in ~/.claude/skills and your CLAUDE.md, and saves them as your personal skills and personal instructions. Choose Sync now, or turn on Keep in sync to sync while Pangea is open.

Review what it found before you sync. Syncing does not copy your whole computer, your local credentials or your environment. Never put secrets in instructions or skills in place of a credential connection.

Use Skills for reusable procedures and Memory for durable facts learned from finished work. A one-time task belongs in the conversation, not in a standing instruction.