What Campfire does and does not try to be

Campfire tries to be a focused workspace for AI-assisted work in a folder. It provides local context, tools that can act on the workspace, and approval boundaries that keep the user in control.

Campfire Tries To Be

Campfire is meant to be:

• A place to open a local folder and work from the files that are really there.
• A practical workspace for questions, edits, reviews, Git workflows, and follow-up work.
• A workspace-aware tool surface where reads, edits, shell commands, and external actions can be scoped and approved.
• A home for workspace-specific settings, memories, approvals, cache, and skills.
• A bridge between local work and connected tools, accounts, or publishing workflows where appropriate.

Campfire Does Not Try To Be

Campfire is not meant to be:

• A replacement for every specialized editor, design tool, terminal, or source-control client.
• A place where CodeBot silently changes files or publishes externally without approval.
• A system that assumes one particular language, framework, build tool, or repository layout.
• A cloud-only workspace that separates your work from your local folder.
• A magic layer that removes the need to review changes, understand approvals, or keep important work under version control.

The goal is not to hide the workspace from you. The goal is to make the workspace easier to understand, change, and move forward.