I make ghfs. It mounts a repository’s GitHub issues read-only at .ghfs/ inside the repo, one Markdown file per issue, fetched before you start working. So when you tell the agent “look at issue 42”, it opens .ghfs/github/issues/open/42.md like any other file in the project instead of calling GitHub in the middle of the task. It is paid and closed source: free for one repository, $5/month or $48/year for unlimited repositories.
Files on disk only help if the agent knows they are there, and that is the Cursor-specific part. ghfs rules --tool cursor writes .cursor/rules/ghfs.mdc, which starts with:
---
description: GitHub issues are available as read-only local files under .ghfs/
alwaysApply: true
---
Per Cursor’s rules docs, alwaysApply: true puts the rule in every chat, and a plain .md in .cursor/rules is ignored, so the extension matters. Below the frontmatter, the rule tells the agent where open and closed issues live, what an issue file looks like (YAML frontmatter, body, then comments), and to pick one way of reading per task: the individual {number}.md files for a few issues, or the hidden .index.json once for anything that spans many issues, not both.
Setup
curl -fsSL https://ghfs.dev/install.sh | sh
ghfs init
cd your-repo && ghfs
ghfs rules --tool cursor
ghfs init signs you in to GitHub and installs the background service. Running ghfs inside a repository registers it and offers to write rule files at the end. ghfs rules --tool cursor writes only the Cursor rule, and you can run it any time.
Requirements:
- macOS: Apple Silicon, macOS 26 or later, macFUSE 5.4.0 or later
- Linux: x86_64 or ARM64 with libfuse3
- Windows: inside WSL 2
On macOS, install macFUSE and enable its File System Extension in System Settings before the first command.
Limits
The files are as fresh as the last fetch, from a command or the background sync; they are not live. ghfs does not call GitHub’s write APIs, but the token it gets at sign-in has repo scope, which GitHub lets write, so the read-only part comes from ghfs and not from the token. Security and data handling - ghfs spells out what that does and does not cover. It handles GitHub Issues only.
The site is https://ghfs.dev/
If you try it, I would like to know whether the rule shows up as always applied under Customize > Rules on your setup, and where having issues as files gets in the way.