Skip to main content
Use Instructions for guidance that should apply across conversations, such as how the team reviews changes or where incident reports belong.

​
Team instructions

Open the team’s Settings → Instructions. Add a clear, scoped rule and review who it affects before saving. Team guidance is shared with the team’s agents; it should not contain personal secrets, temporary command output or credentials.

​
Personal instructions

Open My preferences → Personal instructions in the team’s settings. Keep preferences that apply to your own work here rather than imposing them on the whole team. When personal and team guidance differ, make the intended scope explicit; neither can bypass provider permissions or product access controls. For repository-specific work, keep repository guidance in the files its runtime reads, such as CLAUDE.md or AGENTS.md. Explain the repository and working directory in the conversation so the runtime reads the intended files.

​
Sync my setup

The My preferences → Sync my setup section manages supported local setup synchronization. Review the selected source, files and destination before using it; do not assume that moving a session copied your entire computer, local credentials or environment. Never put secrets into instructions or skills as a substitute for a credential connection. Use Skills for reusable procedures and Memory for durable facts learned from completed work. A one-time task belongs in the conversation instead of a standing instruction.