Doxhub CLI

Command-line interface for Doxhub that allows developers to fetch and pipe documentation to external AI tools.

Installation

# Build the CLI
npm run build

# Link for local development
npm link

Setup

1. Initialize a Project

# Navigate to your project directory
cd /path/to/your/project

# Initialize Doxhub with your workspace and project
doxhub init \
  --api-key YOUR_API_KEY \
  --workspace your-workspace-slug \
  --project your-project-slug \
  --api-url http://localhost:3001/api/v1

# Or use environment variable for API key
export CONTEXTHUB_API_KEY=your_api_key
doxhub init --workspace your-workspace-slug --project your-project-slug

This creates:

• .doxhubrc - Configuration file
• .doxhub-cache/ - Local cache directory
• Updates .gitignore to exclude cache directory

2. Sync Files

Download all project files to local cache:

# Sync all files
doxhub sync

# Sync specific files
doxhub sync README.md API_GUIDE.md

# Sync files with specific tags
doxhub sync --tag foundation-context --tag always-include

# Force re-download all files
doxhub sync --force

# Dry run to see what would be synced
doxhub sync --dry-run

Usage

Check Status

Check which files are cached and up-to-date:

doxhub status

Output:

Project: My Project
Project ID: abc-123
Workspace: my-workspace

✓ README.md v3 (up to date)
↓ API_GUIDE.md v2 (v5 available, 3 versions behind)
? SETUP.md (not cached)

2 file(s) need update - run 'doxhub sync'
1 file(s) not cached - run 'doxhub sync'

Output File Content

Output file content to stdout for piping to AI tools:

# Output all files
doxhub cat --all

# Output specific files
doxhub cat README.md API_GUIDE.md

# Output files with specific tags
doxhub cat --tag always-include

# Include metadata headers
doxhub cat --all --with-meta

# Output as JSON
doxhub cat --all --format json

Pipe to External AI Tools

The primary use case - pipe documentation to AI tools like Cursor, Claude, or Copilot:

# Pipe all documentation to clipboard
doxhub cat --all | pbcopy

# Pipe to Cursor
doxhub cat --all | cursor --add-context

# Pipe foundation docs to Claude
doxhub cat --tag foundation-context | claude --context

# Pipe specific files
doxhub cat README.md API_GUIDE.md | cursor --add-context

Search Files

Search for files in your project:

# Search by filename or content
doxhub search "authentication"

# Search with tag filter
doxhub search "api" --tag backend

# Limit results
doxhub search "guide" --limit 5

Configuration

The .doxhubrc file contains your project configuration:

{
  "api_key": "your-api-key",
  "api_url": "http://localhost:3001/api/v1",
  "project_id": "project-uuid",
  "workspace": "workspace-slug",
  "cache": {
    "enabled": true,
    "ttl": 3600,
    "directory": ".doxhub-cache",
    "max_size_mb": 100
  },
  "sync": {
    "auto": true,
    "on_command": ["build", "test"],
    "notify_changes": true,
    "interval": 300
  },
  "files": {
    "include": [],
    "exclude": ["DEPRECATED_*.md", "DRAFT_*.md"],
    "tags": ["foundation-context", "always-include"],
    "auto_include_tags": true
  }
}

Workflow Example

# 1. Initialize in your project
cd ~/projects/my-app
doxhub init --workspace my-company --project my-app

# 2. Sync all documentation
doxhub sync

# 3. Start coding with AI assistance
# Pipe all relevant docs to your AI tool
doxhub cat --tag always-include | cursor --add-context

# 4. Update when docs change
doxhub status  # Check for updates
doxhub sync    # Download latest versions

Cache Management

The CLI caches files locally for faster access:

• Cache directory: .doxhub-cache/
• TTL: 1 hour (configurable)
• Auto-syncs based on configuration
• Use --no-cache flag to bypass cache

Development

# Build
npm run build

# Watch mode
npm run dev

# Type check
npm run type-check

Architecture

The CLI is designed to be a lightweight bridge between your Doxhub documentation repository and external AI coding tools:

Your Project
    ↓
Doxhub CLI (fetch docs)
    ↓
Local Cache (.doxhub-cache/)
    ↓
Pipe to AI Tool (Cursor, Claude, Copilot)
    ↓
AI-assisted Development

For more information, see the Platform Specification.