Safety & privacy

Tool execution

e runs tools with your user permissions. It does not sandbox file edits or shell commands, and tool execution has no permission prompt by default.

Keep work in version control and review diffs and test output. Avoid exposing credentials or directories the task does not need.

Directory trust

Trust determines whether e loads a repository's instructions and resources. It is not a per-command approval system and does not constrain tool execution.

Review project instructions, skills, and extensions before trusting an unfamiliar checkout.

Model requests

Requests go to the provider you select. They can include conversation text, source files, and tool results used for the task. The provider's data-use and retention policies apply.

A local endpoint sends model requests to the machine or network where you host that endpoint. Local inference does not prevent shell tools or extensions from making their own network requests.

Local storage

~/.e/auth.json

Stored provider credentials. Do not commit or share this file.

~/.e/sessions/

Saved conversations, including tool activity.

HTML exports

The active conversation branch. Review exports for private code and data before sharing.

Extensions

Extensions are executable programs, not isolated plugins. They run with the permissions of the e process. Review their source and only install code you trust.

Report a vulnerability

Use the vulnerability reporting page. Do not put credentials or sensitive project data in a public issue.