Keep related repositories together
Group by product, customer, platform, or environment while each repository keeps its own Git identity.
Multi-repository IDE
Multi-repository IDE: Work across multiple Git repos in one workspace.
Keep frontend, APIs, workers, infrastructure, and shared packages independent in Git and connected in the place where you search, run, debug, and delegate work.
One workspace, separate repositoriesKeep branch, package, change, and runtime state visible for every project.
The problem
A repository is more than another folder in the file tree.
Frontend, API, worker, infrastructure, and shared-library repositories each have an active branch, uncommitted state, dependency manager, startup command, test suite, and terminal history. Separate windows hide those states from one another.
A multi-root file tree exposes files, but it does not tell you which repository is dirty, which service is running, where a failed command belongs, or which agent branch is waiting for review.
How Flame solves it
Connect the workflow while keeping repository boundaries intact.
Every result opens in the project, branch, worktree, and runtime context that produced it.
- 01
Add each repository as a project
Keep every codebase available with its own path, branch, changed-file count, package metadata, terminals, and runtime state.
- 02
Group repositories that ship together
Create a project group for one product or platform without combining Git history, dependencies, permissions, or releases.
- 03
Define shared operations
Reuse group run configurations and worktree defaults while preserving each repository's working directory and environment.
- 04
Search and execute across projects
Find files and symbols or broadcast a command without stopping at the currently active repository.
- 05
Review changes in repository context
Keep every branch, diff, test result, and agent task attached to the project that owns it.
Cross-project searchOpen each result in its real repository context.
Search the product
Find code beyond the active folder.
Search files and symbols across projects when names, types, routes, or configuration keys repeat across services.
- File and symbol indexes stay ready as projects change.
- Commands can target one project or several repositories.
- AI conversations can attach additional projects or worktrees when broader context is required.
Project groups
Share how the product runs without combining its repositories.
Start the stack from one recipe
Run scripts or commands, open files and URLs, start test watchers, and send HTTP requests.
Reuse worktree defaults
Share setup expectations while each project keeps the paths and local files it needs.
Track agent work across the group
Open the exact task, conversation, worktree, diff, or permission request from one manager.
Keep real boundaries
A connected workflow does not erase repository ownership.
Flame does not combine histories, permissions, dependency graphs, or release processes. It gives developers one operational view while the Git repositories remain separate.
When work also needs parallel branches, use first-class Git worktrees. For workspace-wide automation, use Agents Manager.
Product walkthrough
Watch one command run across multiple repositories.
Official Flame demo
Broadcast Commands Across Repositories & Fix Failures with AI
See Flame execute the same check across projects, preserve each working directory, and send a failing result to AI in the repository that owns it.
FAQ
Multi-repository workspace questions
Keep the architecture distributed and the workflow connected.
Download Flame and work across repositories, branches, tools, and agents from one workspace.
Free to use on macOS, Windows, and Linux.