Files and permissions

Project tools

Celo can read files, list folders, search text and write files. Large outputs may be truncated or summarized. Directories such as node_modules, .git, dist and build are excluded from normal scans. A missing item in a summary is not proof that it does not exist.

Choose your working folder

Terminal

cd my-project
celo

Paths are resolved from the folder where you started Celo. Open it at the project root, not your entire home directory. Path restrictions are not a security sandbox: review symbolic links and avoid untrusted projects with sensitive credentials available.

Review permissions

Interactive writes ask for confirmation. Check the file path before approving. In one-off mode, new files may be created without confirmation and overwrites require --yes. Writes replace file contents: keep backups or commits and review the Git diff. Only authorize terminal operations you understand.

Ask for specific deliverables

Terminal

Read package.json and update README with the commands this project actually provides.

Terminal

Find the login implementation and explain the relevant files. Do not change anything.

Terminal

Improve the login page on mobile while preserving the existing components and visual style. Read before overwriting.

Protect your data

File excerpts used in the conversation are sent to the API. Do not request reads of passwords, private keys, personal information or real .env values. Hidden files being excluded from scans does not prevent direct reads. Sanitize examples and logs before sharing.