> ## Content Index
> Fetch the complete content index at: https://blog.brokk.ai/llms.txt
> Use this file to discover other available public pages before exploring further.

# Accelerating Development with Brokk BlitzForge
- URL: https://blog.brokk.ai/accelerating-development-with-brokk-blitzforge/
- Published: 2025-07-09T18:47:53.000Z
- Updated: 2025-07-10T19:01:15.000Z
- Author: Alex Swearingen
- Tags: Blog

Modern codebases often span hundreds, if not thousands, of files. Even the fastest LLMs like the Gemini Flash family become a bottleneck when tasked with processing or performing tasks across that many files. BlitzForge, a new feature in Brokk, removes this constraint and accelerates your development speed so an LLM (even models much smarter than Flash) can work on many files simultaneously. 

## The Core Workflow

![](https://storage.ghost.io/c/f5/e4/f5e49182-2f16-4855-8727-fde7524e784f/content/images/2025/07/Screenshot-2025-07-09-125457.png)

You can access BlitzForge in the Tools menu (Tools → BlitzForge). Here's what the different sections do.

Parallel processing is the core of BlitzForge:

- **Instructions**: Specify the prompt to apply to each file.
- **Action**: Code or Ask. As with [the normal Brokk actions](https://brokk.ai/documentation/actions-toolkit?ref=blog.brokk.ai), Ask will answer questions without making changes, while Code will edit your files.
- **Model**: the model to perform the parallel edits with. Models are color-coded by the parallel throughput you can expect.
- **Per-file command**: Optionally attach the output from this command to each request to send to include in the LLM's context; for example, `git show commit-ish –- {{filename}}` will pull out the changes from `commit-ish` that affected the given file.
- **Related files**: Optionally include the Code Intelligence summaries of the most closely related files for each target file.
- **Workspace**: Optionally attach your current workspace context to each request.
- **Scope**: Specify which files should be targeted by the prompt. You can choose the entire project, manually add files from the file tree, or give a list of files, where Brokk will automatically extract file names from a large block of text.
- **Post-Processing**: once the parallel processing finishes, you can optionally kick off a postprocessing task that can see the entire body of changes and adjust as necessary. Here's what these options do:
- **Action**: select the Architect, Brokk's tool-using agent that can autonomously update the Workspace and invoke Code Agent to make changes, or Ask, a simpler single-round tool for questions or summarization. The default model from your Settings will be used for the post-processing action.
- **Build project first**: when enabled, runs the build and provides its output to the Action agent.
- **Parallel processing output**: select from None, All, or Changed Files Only.
- **Filter**: an optional natural-language classification directive to further narrow down the output provided.

## Try it Out!

BlitzForge ships in Brokk v0.12.0\. [Create a worktree](https://brokk.ai/documentation/using-git?ref=blog.brokk.ai#git-worktree-support), configure your request, and watch your LLM tear through hundreds of files at light speed, turning a large-scale refactor into a background task during a coffee break.