GitHub repositories across projects
Flame’s multi-project workspace keeps repository state, branches, terminals, files, and task context available across related services.
Flame connects GitHub work to the environment where it is implemented: repository state, issues, branches, worktrees, agent tasks, tests, diffs, pull requests, and GitHub Actions status.
A developer often moves from an issue to a branch, then between editor, terminal, CI logs, and pull-request review. When independent tasks are active, it becomes difficult to keep each issue and working directory aligned.
Flame can show GitHub Issues in its Tasks panel, turn an item into an AI task, keep work in an optional worktree, and keep GitHub pipeline status and pull-request actions beside the code.
The tool remains the system you know. Flame provides the local workspace where the work moves forward.
Connect GitHub Issues to the Tasks panel, inspect assigned work, and use the issue as the starting context for implementation.
Launch an AI task or work manually, choosing a branch and optional isolated worktree for the issue.
Use terminals, test tooling, and the Git diff while the repository stays associated with the task.
See GitHub Actions pipeline status, trigger supported jobs, open the run, then open a pull request or choose another landing action.
Flame’s multi-project workspace keeps repository state, branches, terminals, files, and task context available across related services.
GitHub Issues are supported task-provider items in the Tasks panel. An agent handoff can prepare a task and generate a sanitized branch name from the item.
Use a worktree per issue or agent task to keep independent changes out of the active checkout and avoid manual stashing.
Flame can show GitHub CI pipelines, trigger supported jobs, and open the run. That keeps the path from a failure back to the code, terminal, and diff short.
Download Flame to keep implementation, verification, review, and the final Git decision in one workspace.
Free to use on macOS, Windows, and Linux.