Campfire Documentation Outline

This is the initial working outline for the Campfire documentation site. The goal is to document Campfire as a product while keeping shared CodeBot material easy to reuse later from Fire, Water, and Elements docs.

Documentation Strategy

Keep Campfire docs focused on the workspace product: opening folders, understanding workspace state, using CodeBot in that folder, approving actions, and managing workspace-specific settings.

Keep reusable CodeBot docs concept-focused and host-neutral wherever possible: what CodeBot is, how chats/runs/tools/approvals work, how models and accounts are used, and how shared concepts appear in Fire, Water, and Campfire.

When a page needs both, write it in two layers:

  1. A shared CodeBot concept page that explains the behavior without assuming a host.
  2. A Campfire page that explains where the UI lives, which files/folders are used, and which workspace-specific choices apply.

Proposed Site Structure

Welcome

  • What is Campfire?
  • Who is Campfire for?
  • What Campfire does and does not try to be
  • Current product status and availability
  • How Campfire differs from Fire & Water

Getting Started

  • Installing Campfire
  • Opening a workspace folder
  • Understanding the main window
  • Starting the first CodeBot chat
  • Letting CodeBot inspect files safely
  • Where Campfire stores workspace data

Workspace Basics

  • Workspaces and folders
  • The .campfire folder
  • Workspace settings
  • Workspace cache and restore behavior
  • Workspace memories and approvals
  • File tree activity and tool feedback
  • Protecting chat context

CodeBot in Campfire

  • What CodeBot can do in a workspace
  • Chat, background work, and tracked runs
  • Asking questions about the current folder
  • Editing and creating files
  • Searching the workspace
  • Running git-oriented workflows
  • Reviewing changes
  • Using skills and connected tools

Tools and Approvals

  • Why Campfire asks for approval
  • Approval types and what they mean
  • Safe file reads versus file edits
  • Shell commands and guarded actions
  • Workspace-scoped permissions
  • Remembering or revoking approvals
  • Dangerous actions and how Campfire marks them

Functions

  • Workspace function overview
  • Image analysis functions
  • Native pHash and image hygiene checks
  • Vision face detection
  • ArcFace face identity matching
  • CLIP image similarity
  • Model resource provenance and preprocessing notes

Models, Accounts, and Settings

  • Choosing a model
  • Account setup
  • Setting up local image generation with ComfyUI
  • ComfyUI workflows and variants for local media generation
  • Workspace-level CodeBot settings
  • Time awareness
  • Location awareness
  • Proactive mode
  • Sound and attention behavior
  • Power and sleep behavior during long runs

Git and Source Control

  • Reading repository state
  • Reviewing local changes
  • Creating commits
  • Working with branches
  • Pushing changes
  • Using CodeBot for reviews and summaries

Automation and Proactive Work

  • Scheduled prompts
  • Background runs
  • Proactive planning
  • Notifications and attention states
  • Sleep prevention and wake behavior
  • When to use Campfire versus external automation

Integrations

  • MCP tools and connectors
  • Skills
  • Notion, Slack, and other workspace-connected tools
  • Account Manager integration
  • Workspace-specific grants

Social Publishing

  • Social account setup
  • Instagram account requirements
  • Drafting posts
  • Approval-gated publishing
  • Posts, reels, and stories
  • Media requirements and failure handling

Troubleshooting

  • CodeBot cannot see expected files
  • A tool is unavailable
  • Approval prompts look stuck
  • Cached chat restore looks wrong
  • Model or account errors
  • Git command failures
  • Resetting or clearing workspace state

Reference

  • File and folder locations
  • Workspace settings reference
  • Approval storage reference
  • Supported tools
  • Keyboard shortcuts
  • Command and prompt examples
  • Release notes

Shared CodeBot Candidates

These pages should be written so they can later live in shared Fire/Water/Elements docs, with small Campfire-specific notes linking back here.

  • What is CodeBot?
  • Chats, runs, and background activity
  • Tool calls and tool results
  • Approvals and user confirmation
  • Questions CodeBot may ask
  • Skills and context selection
  • Model/account selection
  • Memory and protected context
  • Cache and restore
  • Orchestration and child agents
  • Reviewing, editing, and creating files
  • Source control assistance
  • Troubleshooting CodeBot sessions

Campfire-Only Pages

These should stay in CampfireDocs because they depend on the workspace product shape.

  • Opening and managing folders
  • The .campfire workspace folder
  • Workspace-scoped approvals, memories, and settings
  • Workspace file tree activity
  • Workspace CodeBot tools
  • Campfire-specific proactive settings
  • Campfire social publishing
  • Campfire product onboarding and download pages

Writing Guidelines

  • Prefer task-first pages over architecture-first pages.
  • Start each user-facing page with what the user is trying to do.
  • Keep shared CodeBot pages host-neutral; use host notes only where behavior differs.
  • Keep Campfire pages concrete: name the menu, setting, folder, or visible UI surface.
  • Avoid documenting implementation classes in product docs unless the page is explicitly for developers.
  • When implementation details matter, link to a developer note instead of burying them in user-facing docs.