Letting CodeBot inspect files safely

CodeBot often needs to read files before it can give a useful answer. Reading files in the current workspace is different from changing files, running commands, or publishing something externally.

For ordinary questions, CodeBot may inspect relevant workspace files so it can answer from the actual project instead of guessing. This is the expected workflow for tasks such as summarizing a folder, explaining code, finding configuration, or preparing an edit.

Reads Before Writes

A good CodeBot workflow usually starts with inspection:

1. Identify the relevant files.
2. Read the files needed for context.
3. Explain the finding or propose a change.
4. Make approved edits or run approved tools only when needed.

This keeps answers grounded in the workspace and helps avoid changes based on assumptions.

Actions That Need More Care

Some actions deserve an approval prompt or an explicit user decision. Examples include:

• Editing or creating files.
• Renaming or deleting files.
• Running shell commands.
• Running Git commands that may change repository state.
• Connecting accounts or publishing externally.
• Reading or writing outside the opened workspace.

Campfire uses approvals so you can decide when CodeBot is allowed to move from understanding the workspace to changing it.