Team Setup Guide

Configure ContextDigger for individual or team workflows

📋 Contents

👤 Individual Setup (Solo Development)

Working on your own project? ContextDigger works out of the box with zero configuration.

1

Install ContextDigger

$ curl -sSL https://contextdigger.com/install.sh | bash
2

Initialize in Your Project

# Open Claude Code in your project directory, then:
$ /init-dig

This creates the .cdg/ directory with your project data.

3

Decide: Track or Ignore .cdg/?

✅ Option A: Track .cdg/ in Git (Recommended)

Persist your bookmarks, notes, and discoveries across machines.

$ git add .cdg/
$ git commit -m "Add ContextDigger data"
$ git push

Benefits: Your bookmarks, notes, and navigation history sync across devices.

⚠️ Option B: Keep .cdg/ Local Only

Add to .gitignore if you want ContextDigger data to stay local.

# Add to your .gitignore:
$ echo ".cdg/" >> .gitignore

Trade-off: Your ContextDigger data won't sync to other machines.

✓ Done!

Start using ContextDigger with /dig <area>, /mark-spot, and other commands.

👥 Team Setup (Collaborative Development)

Working with a team? ContextDigger automatically enables team awareness when you share the .cdg/ directory via Git.

🔑 How Team Collaboration Works

  • ✓ No setup required - Works automatically when .cdg/ is in git
  • ✓ Decentralized - No central server, uses git for sync
  • ✓ Auto-detection - Team members identified by git config
  • ✓ Privacy-friendly - Can opt out anytime
1

Repository Owner: Initialize

# In your project (via Claude Code):
$ /init-dig
# Commit the .cdg/ directory:
$ git add .cdg/
$ git commit -m "Initialize ContextDigger for team"
$ git push

The .cdg/ directory now exists in your repository.

2

Team Members: Clone & Start

# Clone the repository:
$ git clone <repo-url>
$ cd <project>
# Start using ContextDigger (via Claude Code):
$ /dig-dashboard

That's it! No additional setup required. ContextDigger will automatically:

  • Detect existing .cdg/ structure
  • Read team activity from other members
  • Broadcast your own activity when you navigate
3

Team Awareness: Automatic

Every time you navigate (/dig <area>), ContextDigger automatically:

  • Updates your activity file in .cdg/team/<your-email>.json
  • Records what area you're working on
  • Tracks your recent bookmarks and navigation
# Example: Alice navigates to backend-api
$ /dig backend-api
# This creates/updates:
.cdg/team/alice_at_company_com.json
4

See Team Activity

View what your teammates are working on:

# Via Claude Code:
$ /dig-team
# Or in dashboard:
$ /dig-dashboard

Example output: "Alice is working on backend-api | Bob is in auth-module | Carol recently marked payment-handler"

5

Share Activity via Git

Team activity is automatically shared through normal git workflow:

# Your normal workflow:
$ git add .
$ git commit -m "Implement authentication"
$ git push
# This also pushes your activity file:
.cdg/team/<your-email>.json
# Teammates pull and see your activity:
$ git pull

🔒 Privacy & Git Configuration

⚠️ Privacy Controls

By default, team activity is shared via git. You can easily opt out or customize privacy settings.

Option 1: Keep Team Activity Private

Don't want to share your activity? Gitignore the team directory:

# Edit .cdg/.gitignore
# Uncomment this line:
team/

Result: Your activity stays local. You can still see teammates' activity if they share theirs.

Option 2: Team Activity On (Default)

Default behavior - team activity is tracked and shared:

# .cdg/.gitignore (default state):
# team/ ← This line is commented = team activity tracked

Result: Your activity is shared with the team. Everyone sees who's working on what.

Option 3: Complete Privacy (Gitignore .cdg/)

Don't want to share anything? Gitignore the entire .cdg/ directory:

# Add to your project's .gitignore:
$ echo ".cdg/" >> .gitignore

Result: Everything stays local - bookmarks, notes, team activity, and all discoveries.

🔍 How User Identity Works

ContextDigger identifies team members using Git configuration:

# ContextDigger uses these git settings:
$ git config user.email
[email protected]
$ git config user.name
Alice Johnson

Activity file created: .cdg/team/alice_at_company_com.json

Note: Make sure your git config is set correctly for proper team identification.

💡 Best Practices

✅ For Individuals

  • ✓ Track .cdg/ in git to sync across machines
  • ✓ Use bookmarks liberally with /mark-spot
  • ✓ Review dashboard regularly with /dig-dashboard
  • ✓ Keep notes in areas for future reference

✅ For Teams

  • ✓ Commit .cdg/ regularly to keep team updated
  • ✓ Check /dig-team before starting work
  • ✓ Share bookmarks for important code locations
  • ✓ Use area notes for team documentation

✅ Git Workflow

  • ✓ Treat .cdg/ like any other project data
  • ✓ Include in your normal commit workflow
  • ✓ Pull before starting to see latest team activity
  • ✓ Resolve conflicts normally (merge or accept theirs)

⚠️ Privacy Considerations

  • ✓ Team activity is visible to all repo members
  • ✓ Use gitignore if you want privacy
  • ✓ Activity shows what areas you visit, not code details
  • ✓ You can opt out anytime by editing .cdg/.gitignore

📚 Common Workflows

Individual Developer

$ /init-dig # Initialize
$ git add .cdg/ && git commit # Track in git
$ /dig backend && /mark-spot # Work & bookmark

Team Member (First Time)

$ git clone <repo> # Clone repo
$ /dig-dashboard # See overview
$ /dig-team # Check team activity
$ /dig backend-api # Start working

Daily Team Workflow

$ git pull # Get latest (includes team activity)
$ /dig-team # See what teammates are doing
$ /dig my-area # Work on your feature
$ git commit && git push # Share your activity

🔧 Quick Reference

Setup Commands

/init-dig

Initialize ContextDigger

/dig-dashboard

View project overview

Team Commands

/dig-team

See team activity

/dig <area>

Navigate (broadcasts to team)

Need help? Visit the documentation or check out all commands.

Next Steps

🚀 Get Started

Install and run your first session

📖 Tutorial

Learn with interactive examples

⚡ Commands

Browse all 40+ commands