Skip to content
Docs

Features

CodeForge turns your DevContainer into a fully equipped AI development environment. Every feature is pre-configured and ready to use the moment your container starts — no setup scripts to run, no extensions to install, no configuration files to write.

This section is your reference guide to everything CodeForge provides. Whether you need a specialized AI agent to audit your security posture, a skill pack to guide your FastAPI development, or a CLI tool to search your session history, you will find it documented here.

Out of the box, CodeForge gives you:

  • 19 specialized AI agents with focused expertise and safety-calibrated tool access
  • 34 domain knowledge packs (skills) for frameworks, patterns, and workflows
  • 23 CLI tools for session management, code quality, and development
  • 3 layers of code intelligence — AST-based search, syntax parsing, and LSP semantic analysis
  • Visual analytics dashboard with session replay, cost tracking, and activity heatmaps
  • Memory management for reviewing and curating agent-generated observations
  • 17 plugins that wire everything together with hooks, guards, and automation

All of these features work together. An agent can load skills for domain expertise, use CLI tools for code quality checks, and leverage code intelligence for precise navigation — all orchestrated automatically.

CodeForge includes 19 specialized AI agents, each with focused expertise, calibrated tool access, and a detailed system prompt that shapes its behavior. When you ask Claude a question, the agent system automatically delegates to the right specialist — an architect for design questions, a security auditor for vulnerability reviews, a test writer for coverage gaps.

Agents fall into two categories:

  • Read-only agents (11 total) — can search, read, and analyze your codebase but never modify it. These include the architect, explorer, investigator, security auditor, researcher, dependency analyst, and spec-writer.
  • Full-access agents (8 total) — can read, write, and execute commands. These include the implementer, documenter, test writer, refactorer, migrator, and generalist.

A key distinction: CodeForge doesn’t just add new agents — it replaces Claude Code’s six built-in agent types entirely. A PreToolUse hook intercepts every agent spawn and transparently redirects stock agents (Explore, Plan, general-purpose, Bash, claude-code-guide, statusline-setup) to enhanced custom specialists with frontloaded skills, calibrated models, and safety hooks. You never interact with a generic agent — every request is silently upgraded. The remaining 13 agents (test-writer, refactorer, security-auditor, and others) are entirely new specialists with no built-in equivalent.

Key safety features set CodeForge agents apart:

  • Worktree isolation — agents like the refactorer, test-writer, migrator, and implementer work in git worktrees, so their changes never touch your working branch until you merge them.
  • Background execution — agents like the security auditor, dependency analyst, and perf profiler run asynchronously, returning results while you continue working.
  • Hook enforcement — read-only agents have bash guards that block any command that could modify files. The refactorer runs tests after every single edit. The test writer verifies all tests pass before completing.
  • Built-in replacement — all six of Claude Code’s stock agents are intercepted at the hook level and replaced with strictly better specialists. This is enforced, not suggested.

View all 19 agents →

34 domain-specific knowledge packs give Claude deep expertise in frameworks, patterns, and workflows. The skill engine provides 23 core skills covering frameworks, practices, and Claude/CodeForge topics. Additional skills come from the spec-workflow (3), ticket-workflow (4), git-workflow (2), agent-system (1), and prompt-snippets (1) plugins. When you start discussing FastAPI routes or Svelte 5 runes, the skill engine detects the context and auto-suggests the relevant skill. Once loaded, the skill injects structured knowledge — best practices, code patterns, API references, and common pitfalls — directly into Claude’s context for the current task.

Each skill is built around a “mental model” — a concise explanation of how a technology works, followed by concrete patterns, code examples, and guidance. This is not generic documentation; skills encode the kind of working knowledge a senior specialist carries.

Skills cover three categories:

CategoryExamplesWhat They Provide
FrameworksFastAPI, Svelte 5, Docker, Pydantic AI, SQLiteFramework-specific patterns, API usage, and testing guidance
PracticesTesting, Debugging, Security, Refactoring, API DesignMethodology, checklists, and established patterns
Claude & CodeForgeAgent SDK, Headless Mode, Skill Building, Spec WritingGuidance for building on and extending CodeForge itself

View all 34 skills →

CodeForge pre-installs 23 tools and utilities covering session management, code quality, language runtimes, and development infrastructure. Every tool is available on your PATH from the first terminal session — run cc-tools to see everything installed and its version.

Highlights include:

  • cc — Launch Claude Code with full CodeForge configuration (plugins, system prompt, agents)
  • ccms — Search your Claude Code session history with boolean queries, role filtering, and time scoping (currently disabled — replaced by codeforge session search)
  • ccusage / ccburn — Track your Claude API token usage and burn rate
  • ruff, biome, shellcheck — Code quality tools for Python, JS/TS, and Shell
  • sg (ast-grep), tree-sitter — Structural code search and syntax tree operations

View CLI tools reference →

Understanding code requires more than text search. CodeForge provides three complementary layers of code intelligence that give Claude (and you) progressively deeper understanding of your codebase:

LayerToolStrength
Pattern matchingast-grep (sg)Find code patterns across files using AST-aware search
Syntax parsingtree-sitterParse files into syntax trees, extract symbols and structure
Semantic analysisLSP serversType information, go-to-definition, find-references, and more

CodeForge installs LSP servers for Python (Pyright), TypeScript/JavaScript, and Go (gopls), giving Claude access to the same semantic operations your IDE uses — but available programmatically from the terminal.

View code intelligence features →

A visual analytics dashboard (Svelte 5 SPA + Bun backend) gives you a complete picture of your Claude Code usage. Browse sessions with full conversation replay, track costs and token consumption across projects, view activity heatmaps, and monitor active sessions with real-time SSE updates. The dashboard runs on port 7847 and auto-launches when your container starts.

View dashboard features →

The memory management system lets you review and curate the observations Claude generates during sessions. Analysis runs extract patterns, preferences, and decisions from conversations. You review each observation in the dashboard — approve it as a permanent memory or dismiss it — and maintenance runs keep the memory store clean. Approved memories sync back to your project’s MEMORY.md for use in future sessions.

View memory management →

CategoryCountHighlights
Agents19Architect, Explorer, Security Auditor, Test Writer, Refactorer, and 14 more
Skills34FastAPI, Svelte 5, Docker, Testing, Debugging, Security, and 28 more
CLI Tools23Session search, token tracking, code quality, formatters, and runtimes
Code Intelligence3ast-grep, tree-sitter, LSP servers for Python/TS/Go
DashboardSession replay, cost tracking, activity heatmaps, real-time SSE updates
MemoriesObservation review, approval workflow, analysis and maintenance runs

All CodeForge features are delivered through the plugin system. Agents come from the Agent System Plugin, skills from the Skill Engine Plugin, and code quality tools are automated by the Auto Code Quality Plugin. CLI tools are installed as DevContainer features during container build.

This architecture means you can enable, disable, or customize any feature without modifying the others:

  • Add an agent — drop a Markdown file in the agents directory with the right frontmatter
  • Create a skill — write a SKILL.md file following the skill template
  • Install a tool — add a DevContainer feature to your devcontainer.json
  • Disable anything — set "version": "none" for features, or remove plugins from the enabled list

Everything is modular and extensible. See Customization for the full guide.