Frequently Asked Questions
Everything you need to know about ContextDigger
🚀 Getting Started
What is ContextDigger?
ContextDigger is a codebase navigation tool that works through Claude Code. It automatically discovers logical areas in your code, tracks your exploration history, and helps you maintain context across coding sessions. Think of it as a GPS for your codebase.
Do I need Claude Code to use ContextDigger?
Yes, Claude Code is required. ContextDigger currently works exclusively through Claude Code chat sessions.
All commands (like /init-dig, /dig, etc.)
are used within Claude Code.
Future versions will support Cursor and other AI coding tools.
How do I install ContextDigger?
Two steps:
Step 1: Install Python package
$ pip3 install --user git+https://github.com/ialameh/contextdigger.git Step 2: Install Claude Code skills
$ curl -o - "https://raw.githubusercontent.com/ialameh/contextdigger/main/install-skills.sh" | bash See Getting Started for detailed instructions.
What languages does ContextDigger support?
ContextDigger is language-agnostic! It works with any programming language including JavaScript/TypeScript, Python, Go, Rust, Java, C++, Ruby, PHP, and more. It discovers code areas based on file structure and common patterns rather than language-specific analysis.
How long does setup take?
Installation takes about 2 minutes. Running /init-dig for the first time
takes 10-30 seconds depending on codebase size. You'll be productive immediately after that!
✅ Do I need to approve commands every time?
No! ContextDigger v1.0.0 runs without approval prompts. Commands execute instantly with zero interruption.
How it works:
ContextDigger uses a CLI-based architecture. When you run /dig-dashboard, it calls a simple bash command that Claude Code auto-approves. All the Python logic runs behind the scenes through your installed package.
What you'll experience:
- Instant execution - No "Do you want to proceed?" prompts
- Smooth workflow - Type command, get results immediately
- Just like native tools - Same experience as running git, npm, or any CLI tool
- Still secure - Commands run from your installed package, not arbitrary code
Technical Note: This is the recommended architecture for Claude Code skills - implement logic in a proper CLI package, keep skill files simple. It's faster, cleaner, and provides a better user experience.
💡 Usage & Features
What's the difference between /dig and /dig-search?
/dig <area-name> - Navigate to a specific discovered area (like "backend-api" or "frontend")
/dig-search <query> - Search across all areas, files, notes, and history
Use /dig when you know where you want to go, /dig-search when you're looking for something.
How do snapshots work?
Snapshots save your complete work context including:
- Current code area you're in
- Your bookmarks
- Navigation history
- Notes you've taken
Use /dig-snapshot name to save and /dig-load name to restore.
Perfect for handling interruptions or switching between features!
Can I use ContextDigger on multiple projects?
Absolutely! Each project gets its own .cdg/ directory.
You can run /init-dig in as many projects as you want.
Your snapshots, bookmarks, and history are project-specific.
Does it work with monorepos?
Yes! ContextDigger is excellent for monorepos. It automatically discovers different services, packages, and modules as separate areas. You can navigate between them seamlessly and understand cross-service dependencies.
How accurate is the dependency analysis?
ContextDigger uses static analysis to map imports/requires and file relationships. It's very accurate for understanding which files depend on each other. For dynamic dependencies (like runtime plugin loading), it shows you file-level relationships which are usually sufficient for planning changes.
👥 Team & Collaboration
Can my whole team use ContextDigger?
Yes! Every team member should install it. The .cdg/ directory
can be committed to git (it's just metadata), so everyone shares the same discovered areas.
Individual history, bookmarks, and snapshots are stored locally, but team notes and wiki are shared.
How does the team wiki work?
When you use /dig-note "your note", it's saved in
.cdg/notes/. Running /dig-wiki
generates a searchable wiki from all team notes. Commit the notes directory to share knowledge with your team!
Can I see what my teammates are working on?
Yes, use /dig-team to see real-time team presence (who's in which code area).
Use /dig-activity to see recent team activity.
Use /dig-who <area> to find the expert for a specific area.
🔧 Technical
Does ContextDigger modify my code?
No, never. ContextDigger only reads your code and creates a .cdg/
directory for metadata. It never modifies your source files.
What's stored in .cdg/?
- areas.json - Discovered code areas
- notes/ - Team notes and wiki content
- config.json - Project settings
- local/ - Your personal history, bookmarks, snapshots (gitignored)
Should I commit .cdg/ to git?
Yes, except for local/. The default .gitignore includes .cdg/local/
but commits the rest. This shares discovered areas and team notes while keeping personal history private.
Does it work with large codebases?
Yes! ContextDigger has been tested on codebases with 500k+ lines of code. Initial scan might take 30-60 seconds for very large projects, but after that, all operations are instant. It's actually MORE valuable for large codebases where manual navigation is painful.
Are there any dependencies?
Zero dependencies! ContextDigger is pure Python with no external dependencies. It only requires Python 3.11+ and Claude Code.
Is my code data sent anywhere?
No. ContextDigger runs entirely locally. Your code never leaves your machine. All analysis is done locally. The only network activity is when Claude Code itself operates (which is controlled by Anthropic, not ContextDigger).
💰 Pricing & Support
How much does ContextDigger cost?
It's free and open source! ContextDigger is released under the MIT license. You can use it for personal projects, commercial work, or anything else without paying.
Where do I get support?
GitHub Issues: Report bugs or request features
Documentation: Complete documentation and guides
Tutorial: Step-by-step walkthrough
Can I contribute to ContextDigger?
Absolutely! Contributions are welcome. See the Contributing Guide for how to get started. We accept bug fixes, new features, documentation improvements, and more.
🔮 Future Plans
Will it support Cursor / VS Code / other tools?
Yes! Support for Cursor and other AI coding tools is planned.
The architecture separates the Python backend from the interface, so adding new tool support is straightforward. Cursor support is the top priority after initial release stabilizes.
Will there be a GUI/web interface?
It's being considered! A web dashboard for visualizing code areas, dependencies, and analytics could be valuable. If you'd like this feature, upvote it on GitHub Issues.
What features are coming next?
Short-term roadmap:
- Cursor support
- One-command installation (simplified setup)
- PyPI package (easier installation)
- AI-powered code area suggestions
- Visual dependency graphs
Still Have Questions?
Check our documentation or ask on GitHub