Workspaces

A workspace is the folder you open in Campfire. It can be a source repository, a documentation folder, a web site, a set of media assets, or any other folder where you want Campfire to help you work.

Campfire does not require any special project format before it can help. It starts from the folder itself, then discovers the files, Git state, settings, skills, and local conventions that make that folder meaningful.

Opening a Folder

When you open a folder, Campfire creates a workspace around that folder. The folder remains the boundary for normal file discovery and file edits. Campfire can inspect files in the workspace, search the folder tree, create or update files, and use workspace-aware tools such as Git when they are available.

If the folder is already a Git repository, Campfire uses that repository state when showing source-control information and when running Git-oriented workflows. If the folder is not a Git repository, Campfire should ask before initializing one.

Workspace State

Campfire stores workspace-local state in a .campfire folder at the root of the workspace. This lets each folder keep its own settings, approvals, memories, cache, and other workspace-specific data.

Typical workspace-local files include:

• .campfire/settings for workspace settings.
• .campfire/codebot.cache for restored CodeBot chat state.
• .campfire/codebot.approvals for workspace-scoped approvals.
• .campfire/codebot.memories for workspace memories.
• .campfire/skills for private workspace skills.

Some files in .campfire are local runtime state. Other folders, such as workspace skills or memories, may intentionally be useful to keep with the workspace. Do not ignore the entire .campfire folder unless that is explicitly what you want for the workspace.

Workspace Settings

Workspace settings let each folder decide how Campfire should behave there. Current settings include time awareness, location awareness, proactive planning, and protected chat context.

These settings are applied when Campfire starts CodeBot for the workspace, including before cached chat state is restored. This matters for settings such as protected chat context, where Campfire needs to know whether restoring or clearing a conversation should be blocked.

Workspace Tools

Campfire uses workspace tools that operate on the opened folder. It can list folders, read files, create files, perform targeted text replacements, run approved Git commands, and record file-tree activity as tools change the workspace.

For regular file edits, Campfire uses workspace file tools instead of shell commands. Shell commands are reserved for tasks that truly need external command execution and may require approval.

Workspace-First

Campfire is workspace-centered. It should not assume the folder uses any specific language, framework, build tool, or repository layout. It should inspect nearby files, infer the conventions in use, and keep actions scoped to the opened workspace unless you explicitly approve something broader.