What do you want to do?
6 use cases
-
Turn a feature idea into a verified task plan
Create a spec, lint it, and mark tasks done only after the graph and history agree.
- Hyperfide
- Software and DevOps
- Intermediate
View prompt
In the Hyperfide repository at <repo path>, create a spec for <feature name> using `hyperfide spec new` and `hyperfide spec add`, then run `hyperfide spec lint`. Report the task list with dependency waves and any lint errors. Verify that every task lists the paths it touches.
-
Give an agent a compact brief of a code area
Pull matching symbols, callers, callees, and routes into one budgeted context call.
- Hyperfide
- Software and DevOps
- Intermediate
View prompt
In the Hyperfide repository, run `hyperfide context` on <symbol or area> and summarize the matching symbols, callers, and callees. Then run `hyperfide changes` and list the affected symbols. Verify that any omitted items are reported as omitted, not silently dropped.
-
Fan a task wave out to parallel Codex or Claude Code sessions
Claim conflict-free tasks and run each in its own sandboxed agent process.
- Hyperfide
- Codex
- Claude Code
- Software and DevOps
- Advanced
View prompt
In the Hyperfide repository, run `hyperfide spec run` for wave <wave number> using Codex CLI or Claude Code. Report each claimed task, its log location, and its final status. Verify that no two tasks declare overlapping paths before the run starts.
-
Run a supervised agent fleet across a spec hierarchy
Start a detached supervisor that drives every wave, manager, and worker until work merges.
- Hyperfide
- Codex
- Claude Code
- Software and DevOps
- Advanced
View prompt
In the Hyperfide repository, start the fleet with `hyperfide fleet up` and follow `hyperfide events --follow` for <N> minutes. Report which waves merged, which tasks were escalated, and whether any approval gate is waiting. Verify that completion is reported only for merged work.
-
Generate release notes from git history
Build a changelog grouped by commit prefix, with optional model-written highlights.
- Hyperfide
- Software and DevOps
- Intermediate
View prompt
In the Hyperfide repository, run `hyperfide changelog` and report the number of releases and the groups used. Verify that each task reference from the commit history appears in the output.
-
Save project decisions so the next session recalls them
Store decisions and constraints in project memory and recall them at session start.
- Hyperfide
- Software and DevOps
- Beginner
View prompt
In the Hyperfide repository, save the decision <decision text> with `hyperfide remember`, then run `hyperfide recall` for <topic>. Report which notes were returned and their order. Verify that the saved note appears in the recall output.
How to use Hyperfide
- Check you have what it needs: A Hyperfide binary built or installed from the repository (install steps are not in the README excerpt, so check the full README); A git repository or a project folder you want indexed; Codex CLI or Claude Code installed if you plan to use spec run or fleet up.
- Open Sidiora-Labs/hyperfide on GitHub and read the README and license.
- Run
hyperfide spec newto create the plan for the feature. - Run
hyperfide spec addto add tasks, declaring the paths each task touches. - Run
hyperfide spec lintto confirm the plan is executable. - Run
hyperfide spec nextto see the next task to work on.
These steps come from our top use case, Turn a feature idea into a verified task plan, which also has a copy-paste agent prompt.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeHyperfide alternatives · Best AI repos for Software and DevOps
About this repo
- Who it is forDevelopers and engineering leads who want AI coding agents to work from a verified plan, shared code context, and persistent project memory.
- Why it is hot
- LanguagePython
- Sourcegithub.com/Sidiora-Labs/hyperfide · Back to Hot repos
Requirements
- A Hyperfide binary built or installed from the repository (install steps are not in the README excerpt, so check the full README)
- A git repository or a project folder you want indexed
- Codex CLI or Claude Code installed if you plan to use spec run or fleet up
- OPENROUTER_API_KEY or CENTRA_API_KEY only if you want the optional model-backed features
Maintain Hyperfide? Add the Featured on Deduped badge
Paste this into your README:
[](https://dedupedai.com/use-cases/sidiora-labs-hyperfide/?ref=badge)
Questions about Hyperfide
What is Hyperfide?
Hyperfide is a local agent workflow CLI that indexes a code repository into a graph, runs planned task loops, and keeps decisions and release notes for humans and AI agents. It is an open-source project on GitHub: https://github.com/Sidiora-Labs/hyperfide.
Who is Hyperfide for?
Developers and engineering leads who want AI coding agents to work from a verified plan, shared code context, and persistent project memory.
What can I do with Hyperfide?
6 use cases so far, for example: Turn a feature idea into a verified task plan; Give an agent a compact brief of a code area; Fan a task wave out to parallel Codex or Claude Code sessions. Each has steps and a copy-paste agent prompt.
What do I need to run Hyperfide?
A Hyperfide binary built or installed from the repository (install steps are not in the README excerpt, so check the full README); A git repository or a project folder you want indexed; Codex CLI or Claude Code installed if you plan to use spec run or fleet up; OPENROUTER_API_KEY or CENTRA_API_KEY only if you want the optional model-backed features.
What are alternatives to Hyperfide?
Other hot AI repos in Software and DevOps: Harness2, iFixAi, Orca, Diagram Design, AI Memory.
Is Hyperfide 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.