About DevProjex
DevProjex is a cross-platform code-to-prompt tool for Windows, Linux, and macOS: a desktop app that turns any folder or Git repository into clean, AI-ready context — project structure, file contents, or both. Whatever you call it — a codebase context generator, a repo packer, or a code-to-prompt converter — the job is the same: prepare real code for ChatGPT, Claude, Gemini, DeepSeek, Qwen, Kimi, Copilot, or any other AI assistant or AI agent such as Claude Code and Cursor, locally on your machine.
It solves an everyday developer problem: a real project does not fit into a chat window. Copying files one by one does not scale, and pasting everything blows past the token limit — often with API keys, passwords, and personal data inside. DevProjex packs your entire repository — or a single module — into one AI-friendly document, shows the estimated token count in advance, and — with one switch — masks detected secrets before the text ever leaves your machine.
If you have been packing codebases with command-line tools and wished for a visual way to do the same job — this is it: a file tree with checkboxes, search and name filters, and a live preview that updates while you select. Scrollbar markers show search matches and every redaction finding at a glance, so you always see exactly what you are sending.
Smart Ignore removes dependencies, caches, and build artifacts automatically — based on real project evidence, so monorepos are filtered correctly and source folders are never hidden by name alone. Git filtering goes further than .gitignore: include only Git-tracked files, or narrow the selection to staged files, all current changes, or a diff between two refs — ideal for sending an AI only what you are working on right now. Root folders, file types, exclusions, and single files toggle independently.
Hide Secrets masks detected API keys, tokens, passwords, and connection strings right in the output, using Gitleaks-based rules. The file and its surrounding code stay in place — one secret never costs you the whole file, a false positive can be overridden per match right in the preview, and any other value can be hidden by hand for the session or permanently for the project, without storing the original. Optional private-data masking hides emails, IP and MAC addresses, phone numbers, and user paths. In CI, the findings check can fail a pipeline before a leak — secret values are never printed.
Code compression saves tokens where it matters: declarations, signatures, fields, and class structure stay intact while method bodies are emptied — pure source code gets about three times smaller. Comment and blank-line stripping covers 20 syntax-aware language packs: C, C++, C#, Go, Java, JavaScript, Kotlin, PHP, Python, Ruby, Rust, Scala, TypeScript, and more. Every transformation applies to the output only: your files never change.
One engine, four ways to work. The GUI gives you the visual tree and preview. The keyboard-first terminal workspace (TUI) brings the same workflow to SSH sessions and servers, with a searchable action palette. The CLI automates scripts and CI: analyze, search, or export straight from a GitHub URL, pipe a file list in from git diff, and use shell completion for bash, zsh, fish, and PowerShell. The built-in Model Context Protocol (MCP) server gives AI agents such as Claude Code, Codex, Cursor, and VS Code read-only access to your project: the agent searches the code and immediately sees which function each match belongs to, reads a single function by name or several files in one request, and receives large results in parts. The server never leaves the folders you allow, opens remote repositories by URL only when you permit it, and its secret masking is always on and cannot be disabled.
Work with your agent, not around it. Connect an agent in one step — from the MCP menu in the app, or with the mcp connect command in the terminal workspace — and choose a mode: Live context or Standard. In Live context mode, the agent follows the checkboxes in the DevProjex file tree: the checked files and folders become its working area, and when you change the checkboxes, the agent sees the new selection on its very next request — no restart, no copy-paste. The window's filters — file types, exclusions, and Git scope — set the boundary: whatever they hide stays out of the agent's reach, while any other project file can still be opened by name when the agent needs it. In Standard mode, the agent works with the whole project, independent of the window. Turn on View → Agent activity, and files the agent received are marked with ✦ right in the tree, while a tooltip shows how many times it received them; in the terminal workspace they are marked with the letter A. Related files show what a file depends on and what depends on it.
The agent journal (MCP → Journal…) keeps the history of every session right on your computer: the client and its version, the mode, the number of calls, response size, estimated tokens, delivered files, the number of masked values, and the duration — plus, for every call, its parameters, result, and notices. Export any session as a Markdown or JSON report — for an audit, for your team, or simply to see exactly what the agent received. Your code, detected secrets, and search query text never enter the journal.
Everything is built for large codebases: fast scanning, search and filters, metrics for files, lines, characters, and estimated tokens — plus a token budget that fits the largest files into a model's context window and reports what was included, while experimental ranking orders files by importance or by closeness to the files you pick, so the budget goes to what matters first. Copy results to the clipboard or export them as ASCII, Markdown, JSON, or XML — or save the selected files as a clean project copy, a folder or ZIP archive, for code review, teaching, or handing a module to a teammate. …
