What do you want to do?
4 use cases
-
Hand an agent a task card with the graph context
Turn a piece of work into a board card and give the agent a brief with the dependency facts attached.
- Flare
- Claude Code
- Codex
- Software and DevOps
- Intermediate
View prompt
In the Flare board for <project>, call tasks_list for the first lane, then task_get on the card <task id> and carry out the brief it returns. Expected output: a progress note sent with task_update and the card moved to review. Verify that the card now shows the new status in the Tasks panel.
-
Review and revert agent edits from shadow history
Compare what an agent changed in a file or tree and revert the parts you reject.
- Flare
- Software and DevOps
- Beginner
View prompt
In the project <project>, open the shadow history for <file path> in Flare and compare the latest snapshot with the one before it. Expected output: a short plain-language list of what changed in that file. Verify the list matches the task card the agent was given before you keep the change.
-
Keep two agents from colliding on the same files
Have agents announce the files they take in the Channel tab and check who wrote what.
- Flare
- Claude Code
- Codex
- Software and DevOps
- Advanced
View prompt
In the project <project>, before editing any file, call chat_post with kind taking and the paths you will change, then call chat_read when you finish. Expected output: a confirmed post and a short list of anything other agents said they were taking. Verify that no other agent has announced the same paths before you start editing.
-
Keep Claude working through the board when it wants to stop
Set the routine so the agent checks the board again instead of ending its session early.
- Flare
- Claude Code
- Software and DevOps
- Intermediate
View prompt
In the project <project>, call working_agreement and report how many cards are waiting to be picked up and which card to take next. Expected output: those counts and the card name. Verify that the card is still in the first lane before you start it, and move it to in-progress when you claim it.
How to use Flare
- Check you have what it needs: Flare, either as the desktop app or served to a browser from the machine the agent runs on; A terminal agent such as claude, codex or opencode, run inside Flare's terminal; A local project repo for the agent to work on.
- Open AlgoNoRhythm/Flare on GitHub and read the README and license.
- Open Flare on the project, either as the desktop app or in a browser served from the machine the agent runs on.
- In the control panel, open Tasks and add a card for the work.
- In the graph, select the relevant files, right-click and choose New task with these files to file the card from the selection.
- Click Copy for agent on the card and paste the brief into a session started with
claudeorcodexin Flare's terminal.
These steps come from our top use case, Hand an agent a task card with the graph context, which also has a copy-paste agent prompt.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeAbout this repo
- Who it is forDevelopers who run coding agents on a real repo and need to see what they change, hand them work, and keep several of them from colliding.
- Why it is hot
- LanguageTypeScript
- Sourcegithub.com/AlgoNoRhythm/Flare · Back to Hot repos
Requirements
- Flare, either as the desktop app or served to a browser from the machine the agent runs on
- A terminal agent such as claude, codex or opencode, run inside Flare's terminal
- A local project repo for the agent to work on
Maintain Flare? Add the Featured on Deduped badge
Paste this into your README:
[](https://dedupedai.com/use-cases/algonorhythm-flare/?ref=badge)
Questions about Flare
What is Flare?
Flare is a graph-first IDE for agentic coding that maps a codebase as a live graph, runs a terminal for agents like claude, codex or opencode, keeps a shadow history of changes, and holds a shared task board and chat for agents. It is an open-source project on GitHub: https://github.com/AlgoNoRhythm/Flare.
Who is Flare for?
Developers who run coding agents on a real repo and need to see what they change, hand them work, and keep several of them from colliding.
What can I do with Flare?
4 use cases so far, for example: Hand an agent a task card with the graph context; Review and revert agent edits from shadow history; Keep two agents from colliding on the same files. Each has steps and a copy-paste agent prompt.
What do I need to run Flare?
Flare, either as the desktop app or served to a browser from the machine the agent runs on; A terminal agent such as claude, codex or opencode, run inside Flare's terminal; A local project repo for the agent to work on.
What are alternatives to Flare?
Other hot AI repos in Software and DevOps: Harness2, iFixAi, Orca, Diagram Design, AI Memory.
Is Flare safe to run?
Deduped does not own, audit or vouch for it. Read the README and license, run it on your own systems first and review every command before you run it.