ghfs
ghfs.dev- Category
- Developer Tools
- Rank
- No. 3944Tools index
Previous survey · No. 3647 ·
- Pricing
- Freemium
- Type
- TOOL
- Use case
- Coding
- Interfaces
- CLI
- Date
About
ghfs syncs a GitHub repository's issues to a local .ghfs/ directory as plain read-only markdown files before a coding agent starts working, split into open and closed folders by issue number. Because agents like Claude Code, Cursor, Copilot, and Aider can read them as ordinary files, ghfs removes the need for a tool call mid-task to fetch or search issue content, and it writes project rule files so each agent knows where to find them.
At a glance
ghfs mirrors GitHub issues as read-only local files for coding agents. It is worth trying if an agent needs issue context repeatedly and you want it available before the session starts.
Good fit
Developers who work from GitHub issues and want an agent to read them alongside project files.
Consider something else when
Query GitHub directly when you need current issue state at every step or cannot keep a local copy.
Start here
Use a public test repository, find a known issue in the local files and compare it with GitHub. Check how quickly an issue edit is reflected.
Cost and requirements
The publisher offers free setup and documents macOS, Linux and Windows through WSL 2. Native Windows is on its roadmap.
Limits to know
The local view is read-only and can lag the remote issue. Check which repositories are mirrored and who can read the resulting files.
Sources checked 2026-11-05. Source-based assessment.
Why it made the leaderboard
ghfs pre-fetches GitHub issues to local files so a coding agent reads them like any other file instead of making a tool call mid-task, cutting a common source of failed or repeated fetches during agent runs.
Tags
Media
Comments (0)
No comments yet
Editorially curated, with community endorsements as a secondary signal. Corrections welcome.