ghfs
ghfs is a background daemon that mounts GitHub Issues as read-only markdown files in a `.ghfs/` directory on disk, synced before AI agents start work. Developers and AI coding assistants like Claude Code, Cursor, and Windsurf read issues as ordinary local files instead of making API calls mid-task. ghfs generates rule files for each AI tool, telling agents where issues live and how to read them. The tool supports macOS, Linux, and Windows via WSL 2, and integrates with GitHub Copilot, Aider, Cline, and other coding assistants. Issues are searchable via grep, find, and jq without leaving the IDE.
ghfs is an AI code tool, priced at $5/month on the Hobby plan, integrating with Claude Code, Cursor, Windsurf, and Cline. InnovaAI scores it 4.2/10 for agency adoption, best for Developer, Tech Lead, and Project Manager roles handling weekly client-facing work.
Agency Audit
ghfs mounts GitHub Issues as read-only local files on disk, synced before AI agents start work, so coding tasks never pause for mid-task API calls to fetch context. Claude Code, Cursor, Windsurf, and Cline read issues as ordinary markdown files instead of tool calls. Best suited for software development agencies and engineering teams where developers spend 3+ hours weekly context-switching between GitHub and AI coding assistants, or where AI agents repeatedly re-fetch the same issue mid-task.
5recommended
40/mo
$2,995/mo
Low
Illustrative scenario. Not a guarantee. Net capacity is the value of reclaimed time at $75/hr, less the lowest verified paid base plan (flat plan cost is shared). Hours saved come from the service estimate; implementation, taxes, and unprovided usage charges are excluded.
- Developer handling ai-assisted code task execution
- Tech Lead handling github issue context retrieval
- Project Manager handling mid-task context switching
- Your agency does not use GitHub Issues as the primary task or backlog system, or relies on Jira, Linear, or Asana instead.
- Your team works exclusively on Windows without WSL 2 and cannot wait for native Windows support to roll out.
- Your developers rarely use AI coding assistants like Claude Code or Cursor, so the context-fetch optimization provides no workflow compression.
Internal Adoption Path
$5/mo
$5/mo flat plan
40 hr/mo
5 seats × 8 hr each
$3,000/mo
modeled at $75/hr labor rate
$2,995/mo
value − subscription cost
In this model, 5 seats reclaim 40 hours of team time each month. Valued at $75/hr that is $3,000/mo, and after the $5/mo subscription it leaves $2,995/mo of capacity for billable client work.
Illustrative scenario. Not a guarantee. Uses the lowest verified paid base plan. Implementation, taxes, and unprovided usage charges are excluded.
Platform Features
Core capabilities of ghfs
Pre-fetch GitHub Issues to disk
ghfs syncs GitHub Issues as markdown files in a `.ghfs/` directory before AI agents start, eliminating mid-task API calls. Developers and AI agents read issues as ordinary local files using grep, find, or jq instead of calling `gh issue view` repeatedly.
Background sync daemon
Once initialized, ghfs runs in the background and keeps issues current without developer intervention. Project Managers and Tech Leads can rely on fresh issue state being available to AI agents without manual refresh steps.
Auto-generate AI tool rule files
ghfs writes project-level rule files for Claude Code, Cursor, Windsurf, Cline, GitHub Copilot, and Aider, telling each agent where issues live and how to read them. Developers register the tool once and all AI agents immediately know to read pre-fetched issues instead of making tool calls.
Read-only filesystem mount
Issues appear as ordinary markdown files in the working tree, readable by any tool that opens files. No agent-side integration required; Claude Code, Cursor, and Copilot all read the same files without special configuration.
Multi-account and multi-org support
Developers can switch between multiple GitHub accounts and organizations, and ghfs mounts issues from each under separate namespaces. Teams with multiple GitHub orgs or personal accounts can access all issues in one working tree.
Searchable issue archive
All synced issues are searchable via grep, find, and jq without leaving the terminal or IDE. Developers and AI agents can locate related issues, closed tickets, or discussion threads without returning to GitHub's web UI.
What Makes ghfs Different
Unique advantages vs similar tools in this niche
Pre-fetches issues to disk before the agent starts
vs MCP servers that fetch issues mid-taskContext is on disk before the agent starts, so nothing in the middle of a task depends on a call succeeding.
Exposes issues as ordinary local files readable by any tool
vs gh issue view requiring correct flags and repeated callsAnything that can open a file can read an issue, and agents can grep across open issues without leaving the working tree.
Writes project-level rule files for multiple AI assistants
vs Manual configuration per AI toolghfs register offers to generate the rule; ghfs rules writes it any time, for the tools you pick.
Latest Updates
Recent releases and improvements for ghfs
v1.0.1
Fix2026-04-07A patch release with stability improvements and usability enhancements.
Fixed a readdir hang on Linux caused by incorrect fill offsets
Fix2026-04-07Bug fix for Linux readdir hang.
Fixed issue where exceeding project limit stopped polling entirely
Fix2026-04-07Polling now continues for allowed projects even when project limit is exceeded.
First fetch now skips activity_threshold check
Improvement2026-04-07Newly registered projects sync immediately on first fetch.
Release artifacts are now GPG-signed
Improvement2026-04-07Public key is available on the download page for verification.
Value Equation
Outcome-likelihood-time-effort assessment for ghfs
Limited agency channel
ghfs scored below the agency-resellability threshold (agency_fit_score < 50). The Value Equation projects agency-side outcomes, which don't apply to tools without a clear resell pathway.
Contact ghfsPricing
ghfs platform cost to your agency
Starts at $5/mo (Hobby), scales to $15/mo (Pro)
Free
- Issues
- 1 repository
- Background sync
Hobby
- Issues (all)
- Unlimited repositories
- Background sync
Pro
- Issues (all)
- Projects
- Discussions
- Pull Requests
Enterprise
- Everything in Pro
- Team license management
No verified white-label program for ghfs: client-facing delivery runs under the platform's native branding.
Market Intelligence
Offer + scale economics for ghfs
Limited agency channel
ghfs scored below the agency-resellability threshold (agency_fit_score < 50). It's a useful tool but not designed for white-labeled or retainer-based reselling, so we don't publish productized offer economics for it.
Contact ghfsInvestment Decision Framework
Strategic vetting analysis for ghfs
Situational Fit
Fit depends on your client mix
Buy If
4Your developers spend 2+ hours per week switching between GitHub Issues and AI coding assistants like Claude Code or Cursor to copy-paste issue context into prompts.
Your Project Managers or Tech Leads manage backlogs in GitHub Issues and want AI agents to read full issue descriptions and comments without halting mid-task for API calls.
Your engineering team uses Cursor, Windsurf, or Cline daily and currently works around missing context by manually pasting issue text into the chat.
You operate on macOS, Linux, or Windows with WSL 2 and your developers already have GitHub CLI familiarity or use GitHub as your source of truth for project state.
Skip If
5Your developers rarely use AI coding assistants like Claude Code or Cursor, so the context-fetch optimization provides no workflow compression.
Your engineering team is small (1-2 developers) and context-switching overhead is negligible compared to the operational cost of running a background sync daemon.
Your agency policy restricts running background daemons or mounting virtual filesystems on developer machines.
Your agency does not use GitHub Issues as the primary task or backlog system, or relies on Jira, Linear, or Asana instead.
Your team works exclusively on Windows without WSL 2 and cannot wait for native Windows support to roll out.
Bottom Line
ghfs mounts GitHub Issues as read-only local files on disk, synced before AI agents start work, so coding tasks never pause for mid-task API calls to fetch context. Claude Code, Cursor, Windsurf, and Cline read issues as ordinary markdown files instead of tool calls. Best suited for software development agencies and engineering teams where developers spend 3+ hours weekly context-switching between GitHub and AI coding assistants, or where AI agents repeatedly re-fetch the same issue mid-task.
Reality Check
Requires macOS/Linux or WSL 2 (native Windows support is roadmap-only), and team members must run a background sync daemon. Adoption friction is low for teams already using GitHub Issues as their primary task tracker, but adds operational overhead if your agency uses multiple issue systems or rarely leverages AI coding assistants.
Moderate effort: standard configuration with some customization needed
Academy for ghfs
Work through it in order: the course for this service first, then the modules behind it.
Course for this service
ghfs Agency Implementation, Automating Issue Context for AI Coding Teams
Learn how to set up ghfs as a production delivery tool for your agency, enabling AI coding assistants to read GitHub Issues as local files without API calls. This course covers daemon configuration, rule file generation for Claude Code and Cursor, retainer workflows for ongoing issue syncing, and productized services around AI-assisted development.
Open the courseNo Academy modules are published for this service yet. Browse the full Academy
Why this category matters
The commercial case before the tooling.
Core concepts
The mental model you need to price and scope the work.
- Scaffold, Don't SubstituteConcept
Scaffold, Don't Substitute is a framework for agencies adopting AI code tools: use them to generate scaffolding and handle maintenance, but never as a replacement for human architectural oversight. The strategic insight from the category description warns that over-reliance risks code quality inconsistency and vendor lock-in. For example, an agency might use Verdent to rapidly prototype a full-stack app from a natural language brief, then have senior engineers review and refactor the generated code before delivery. Similarly, Ripple can auto-fix consumer code when APIs break, but a human must verify the changes align with client contracts. This framework helps agencies capture speed advantages while protecting quality and client trust. It also aligns with recent market data showing that AI agent loops can run 100x cheaper via simulation, but accuracy tradeoffs demand human judgment for high-stakes tasks.
- Human Checkpoint RatioConcept
The Human Checkpoint Ratio is the proportion of AI-generated code that passes through human review before delivery. Agencies adopting AI code tools often see speed gains, but unchecked automation can introduce subtle bugs and architectural drift. The framework holds that the optimal ratio depends on task risk: scaffolding and boilerplate can run nearly autonomous, while core business logic and client-facing features demand human sign-off. For example, HumanLayer structures workflows with six phases, each requiring human checkpoints, ensuring alignment and early error catching. Similarly, Ripple automates API break fixes but relies on developers to review generated pull requests. Agencies should define explicit checkpoints per task type, balancing speed with quality. A 100x cost reduction in simulation-based agents, as reported by Marktechpost, suggests that high-volume, low-stakes tasks can tolerate lower ratios, freeing human oversight for critical paths.
- Maintenance Over BuildConcept
AI code tools shift agency value from greenfield builds to ongoing maintenance. Platforms like Ripple auto-fix breaking API changes across repos, while Verdent generates full-stack apps from prompts, making initial builds cheap and commoditized. The durable margin lies in keeping client systems healthy: dependency updates, security patches, and refactors. Agencies that sell maintenance retainers, not just launch fees, convert a one-off project into recurring revenue. A 100x cost reduction in agent loops, as reported in simulation research, makes automated upkeep affordable at scale. The framework: use AI for scaffolding and repairs, but anchor the commercial model on continuous care, where human oversight prevents the quality drift that pure automation introduces.
Decision and risk
How to judge the fit, and the ways it goes wrong.
- AI Code Tools Rule: Scaffold Fast, Architect SlowEvaluation Rule
Use AI code tools for scaffolding and maintenance tasks, but keep human architectural oversight for production decisions.
- AI Code Tools Rule: When Delivery Speed Is the Bottleneck, Automate Maintenance Before Greenfield BuildsEvaluation Rule
Use AI code tools for scaffolding and maintenance automation first, and reserve human architects for greenfield design and final review.
- The Scaffolding-Only Trap: Why AI Code Tools Stall in Agency DeliveryFailure Pattern
- The Unreviewed Merge Trap: Why AI Code Tools Fail in Agency DeliveryFailure Pattern
8 modules selected for ghfs
Frequently Asked Questions
Answers about pricing, setup, implementation
ghfs mounts GitHub Issues as read-only local files on disk, synced in the background before AI agents start work. Developers and AI coding assistants like Claude Code, Cursor, and Windsurf read issues as ordinary markdown files instead of making API calls mid-task. ghfs also generates rule files for each AI tool, telling agents where issues live and how to read them.
Hobby plan is $5 per month (or $4 per month annual) and includes unlimited repositories and background sync. Pro plan is $15 per month (or $12 per month annual) and adds Projects, Discussions, and Pull Requests. Enterprise pricing is custom; contact sales for a quote. A free tier is available for single-repository projects.
Developers and AI-assisted engineers save time by reading pre-fetched issues without context-switching to GitHub or re-fetching mid-task. Tech Leads and Project Managers benefit by knowing AI agents always have full issue context available. Engineering team leads managing backlogs in GitHub Issues see faster task resolution when AI agents can read comments and linked discussions without pausing.
A developer using AI coding assistants 3+ hours per week can expect to reclaim 1-2 hours weekly by eliminating context-fetch interruptions and copy-paste overhead. The savings scale with team size: a 5-person engineering team using Claude Code or Cursor daily could recover 5-10 hours per week across the group. Actual savings depend on how frequently your workflow requires switching between GitHub and AI agents.
ghfs integrates with Claude Code, Cursor, Windsurf, Cline, GitHub Copilot, and Aider. It generates rule files for each tool automatically, so your AI agent reads pre-fetched issues as local files without additional setup. If you use a different AI coding assistant, ghfs still makes issues available as files in your working tree, but you may need to manually point the agent to the `.ghfs/` directory.
ghfs runs on macOS (Apple Silicon, version 26 or later, with macFUSE 5.4.0), Linux, and Windows via WSL 2. Native Windows support is on the roadmap. Installation is a single curl command, and setup takes under 5 minutes: `ghfs init` to sign in to GitHub, then `ghfs` inside your repository to register it.
Initial setup is 5-10 minutes per developer: install, run `ghfs init`, and register repositories. Once running, the background daemon requires no ongoing maintenance. Team adoption friction is low if your agency already uses GitHub Issues and AI coding assistants; the main friction is ensuring all developers have macOS/Linux or WSL 2 available.
ghfs stops syncing new issues and the background daemon stops running. Existing `.ghfs/` directories remain on disk but will not update. Developers can delete the `.ghfs/` folder or continue reading stale issue files locally. No data is lost; cancellation is reversible by re-running `ghfs` in your repository.