Working with a Campfire Workspace

In Campfire, CodeBot works inside the folder workspace you opened. It can understand the workspace root, list files and folders, create plain workspace files, and use Git through Campfire's workspace Git manager.

Ask CodeBot to Understand the Workspace

CodeBot can inspect the current workspace and list folders without using a shell command.

Typical prompts:

  • "What kind of project is this workspace?"
  • "List the top-level folders."
  • "Find the source folder and summarize the layout."
  • "Show me what changed in this workspace."

This is the best first step when CodeBot needs workspace structure but does not need arbitrary terminal access.

Ask CodeBot to Create Workspace Files

CodeBot can create new text files in the folder workspace without adding them to an IDE project.

Typical prompts:

  • "Create a README for this workspace."
  • "Add a small script under tools."
  • "Create this JSON config file in the workspace root."

If the target is outside the workspace, Campfire asks for approval before writing there.

Ask CodeBot to Work with Git

CodeBot can initialize Git for a workspace that does not already use it, or run Git operations through Campfire's Git manager.

Typical prompts:

  • "Initialize Git here with main as the default branch."
  • "Show me git status."
  • "Summarize the last five commits."
  • "Show the diff for this branch."

Use Git through Campfire when the task is specifically about repository state. CodeBot should use the generic terminal only when the action is not covered by the workspace Git manager.

Approval and Safety

Initializing Git and running Git commands can change workspace state, so Campfire may ask for approval. After Git commands that affect the workspace, Campfire reloads source-control state.