johnlindquist / johnlindquist/mdflow
Feature Request: Support Recursive Directory Traversal for Global Agents (`~/.mdflow/`)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 604
- Forks
- 43
- PR merge metrics
- No merged PRs in 30d
Description
Description
Currently, mdflow scans project-scoped flows (flows/) recursively (recursive: true), but user-scoped global agents (~/.mdflow/) are resolved non-recursively (recursive: false in src/flow-discovery.ts). This prevents users from organizing personal/global agents into logical domain subfolders (e.g., ~/.mdflow/engineering/, ~/.mdflow/utils/).
Proposed Change
Modify the global filesystem source configuration in src/flow-discovery.ts to enable recursive traversal:
{
root: join(homeDir, ".mdflow"),
recursive: true, // Changed from false
scope: "global",
origin: "global-personal",
source: "~/.mdflow",
provenanceLabel: "GLOBAL",
}
Benefits
- Allows local organization of complex personal rosters without cluttering the root directory.
- Aligns the behavior of global flow discovery with project flow discovery.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Open src/flow-discovery.ts and compare the project-scoped filesystem source with the global ~/.mdflow source. Enable recursive traversal for the global source, then verify that flows in subdirectories such as ~/.mdflow/engineering/ and ~/.mdflow/utils/ are discovered while preserving the global scope and provenance settings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 88/100