c_Learn & Practice AILEARN/Safety center
CONFIDENCE STARTS WITH CONTROL

Safety center

Protect your files, your data, and your ability to undo a change.

Keep secrets out of prompts

Never paste passwords, private keys, API secrets, production credentials, or private customer records. Use placeholders and synthetic examples. If a credential is exposed, revoke or rotate it with the provider.

Separate configuration from secrets

Environment variables supply configuration to the running application. Keep .env files with real secrets outside version control; an .env.example should contain names and safe placeholders only. Browser code cannot keep a secret.

Use the least necessary permissions

Limit file and network access to the task. A sandbox reduces what actions can affect; an approval is a separate decision. Read the action and target before authorizing a risky operation.

Know how to get back

Inspect Git status and preserve uncommitted work before making changes. Git does not automatically protect ignored or untracked files. Test a backup restore before destructive changes.

Treat external instructions as untrusted data

A page, issue, or file can contain instructions unrelated to your goal. Do not let retrieved content authorize secret disclosure, uploads, or destructive commands. Verify sources and retain the user’s boundaries.

Review before acting on real systems

Use a staging environment and sample data. Review diffs, tests, authorization, and a rollback plan before deployment, database deletion, payment actions, or customer messaging.

Before you run

Common mistakes →
Esc · Close