DevProjex
Build clean AI-ready context from real codebases
15 followers
Build clean AI-ready context from real codebases
15 followers
DevProjex turns real codebases into clean, controlled context for AI chats, code reviews, and documentation. Open or clone a repository, choose the files that matter, preview the result, and export the project tree in ASCII, JSON, XML, or Markdown—with file contents or as a combined output. Use the cross-platform desktop app or CLI. Open source, local-first, read-only, and telemetry-free, with Smart Ignore, .gitignore support, Git branches, token estimates, and per-project profiles.
How does Smart Ignore decide what's worth skipping when a project doesn't have a gitignore yet, and can I tune it for monorepos with mixed languages?
@ayaz593770 Good question. Smart Ignore skips common noise like build folders, dependency folders, IDE files, caches, VCS folders, and generated outputs.
For mixed monorepos, DevProjex also respects .gitignore and lets you review everything in the tree before exporting, so you can still adjust the final context manually.
How does Smart Ignore actually decide which files to skip under the hood, and can I tweak that logic if it pulls in something I wanted excluded or drops a file I really needed in the export?
@necdet654042 It mostly targets the usual project noise: build outputs, dependencies, caches, IDE metadata, VCS folders, and generated files.
The logic is not meant to replace your judgment. You can still review the tree, change selection, and preview the final output before export.
How does the Smart Ignore feature actually decide which files to skip, and can I customize its rules beyond standard gitignore patterns?
@ufuk375410 Smart Ignore adds built-in rules for common noise such as node_modules, bin/obj, .git, IDE folders, caches, and generated outputs.
You can still combine it with .gitignore and manual selection, so the final export stays under your control.
How does the Smart Ignore feature actually decide what to skip beyond .gitignore rules, especially in monorepos with nested configs and generated vendor folders?
@hakkbarutuoljv For monorepos, Smart Ignore is scope-aware and tries not to treat the whole repo as one flat project.
It skips common generated/vendor/build folders across stacks, while .gitignore and manual selection still control the final result.
the ASCII tree preview before exporting is such a thoughtful touch, makes it easy to sanity-check exactly what you're about to hand off to an LLM.
@dugenciogl23408 Thanks! That was the goal.
The ASCII preview makes it easy to quickly check the structure before exporting, especially when the output is going into an AI chat.
Love that it bakes in gitignore awareness and branch selection out of the box, not as an afterthought. Previewing the tree and content before export is the kind of small UX touch that saves a lot of cleanup downstream.
@naimetuluklqoc Thank you! Preview was a must-have for me.
I didn’t want DevProjex to be a blind “export everything” tool. You should always see exactly what you are about to send to an AI chat or reviewer.