Connect
Add Claude in AI settings and sign in, or configure a supported API, Bedrock, or Vertex connection. Flame installs the native runtime on demand.
Claude Code integration
Give Claude Code a worktree. Review the fix.
Claude Code remains the coding agent. Flame provides the workspace around it: projects, files, terminals, worktrees, tests, review, and the decision about how changes land.
The developer problem
Claude Code is powerful. An agent session is not the whole development environment.
A terminal session can implement a change, but production work still needs branch isolation, test output, browser and API evidence, Git review, and a clear merge decision.
Flame keeps Claude Code in that wider loop. You can start a task in the right project, choose whether it receives its own branch and worktree, watch its tool activity, then inspect the resulting diff before merging locally, pushing the branch, or pushing and preparing a PR/MR form for you to submit.
Try it on a real task
What Claude Code enables in Flame
Example task
Ask Claude to trace a failed webhook retry, add a regression test, and implement the fix in a dedicated worktree.
Inspect the result
Read the test output and changed files in that checkout. For supported native Claude sessions, Multi-agent mode can delegate read-only research or review while the lead makes the edits.
What to expect
Your provider account and model access are required. Delegated workers are distinct from independent worktree jobs; native capabilities depend on the installed runtime.
A connected workflow
A Claude Code task from issue to review
- 01
Start from the work
Open a task from the connected tracker or write a focused implementation prompt in the project that owns the change.
- 02
Choose isolation
Give Claude Code an optional dedicated branch and Git worktree so it does not alter the checkout you are using.
- 03
Keep moving
Follow task status, terminal output, token use, and tool calls from Agents Manager while you work elsewhere.
- 04
Verify and land
Run the relevant tests, inspect the diff and merge preview, then choose local merge, branch push, or push and prepare a PR/MR creation form.
How it works in Flame
What Flame adds around Claude Code
Several Claude Code tasks, without a pile of terminals
Agents Manager keeps running, queued, scheduled, and completed tasks in one cross-project view. Set a workspace-wide concurrency limit instead of manually tracking terminal windows.
Worktree isolation for parallel changes
Each task can work in its own Git worktree and branch. That makes it practical to have one task update an API while another changes a frontend without sharing a working directory.
Development context at the point of work
Flame can attach selected files, diffs, terminal output, test results, and browser state to an AI conversation under scoped permissions.
Human review stays explicit
Claude can make the changes, but Flame keeps landing policy under developer control. Review the diff and merge preview before deciding how work should reach the remote.
FAQ
Claude Code integration questions
Use Claude Code with Flame.
Download Flame to keep implementation, verification, review, and the final Git decision in one workspace.
Free to use on macOS, Windows, and Linux.