Configuration

GDT works out of the box with minimal setup. This guide covers the options available when you want to customize behavior.

Data Locations

GDT stores everything locally in ~/.gdt/:

~/.gdt/
├── config.json          # Your preferences
├── privacy.json         # Privacy settings
├── sessions/            # Conversation history
├── task-context/        # Task decomposition data
└── usage/               # API usage tracking

Task data is managed by TaskWarrior and stored separately in ~/.task/.

Environment Variables

Required

Variable	Description
ANTHROPIC_API_KEY	Your Anthropic API key (starts with sk-ant-)

Optional

Variable	Description	Default
GDT_MODEL	Claude model to use	claude-sonnet-4-20250514
GDT_MAX_TOKENS	Maximum response length	4096
GDT_DATA_DIR	Data storage location	~/.gdt

Privacy Settings

GDT gives you full control over conversation history.

View current settings:

> /privacy

📋 Privacy Settings

Conversation history: Enabled
Data location: ~/.gdt/sessions/

Commands:
/privacy disable history  Stop saving conversations
/privacy enable history   Resume saving conversations
/privacy clear history    Delete all history
/privacy clear all        Delete all GDT data

Disable conversation history:

> /privacy disable history

When disabled, each GDT session starts fresh with no memory of previous conversations. This trades convenience for privacy.

API Usage Monitoring

GDT tracks your API usage to help manage costs. Usage logs are stored in ~/.gdt/usage/ as daily JSON files.

Set usage limits in ~/.gdt/config.json:

{
  "api": {
    "dailyLimit": 100000,
    "alertThresholds": [0.8, 0.9, 0.95]
  }
}

When you hit a threshold, GDT warns you:

⚠️ API Usage Alert: 80% of daily limit used

Complete Configuration Example

{
  "api": {
    "model": "claude-sonnet-4-20250514",
    "maxTokens": 4096,
    "dailyLimit": 100000,
    "alertThresholds": [0.8, 0.9, 0.95]
  },
  "session": {
    "maxHistoryMessages": 50,
    "autoSave": true
  },
  "decomposition": {
    "maxRetries": 2,
    "cacheTTL": 1800
  }
}

TaskWarrior Integration

GDT automatically adds these custom attributes to TaskWarrior:

Attribute	Purpose
gdt.complexity	Complexity score (1-10)
gdt.has_risks	Whether task has identified risks
gdt.decomposed	Whether task has been broken down
gdt.context_file	Path to detailed analysis file

These are stored in ~/.taskrc and let GDT track metadata across sessions.

Debug Mode

When troubleshooting, enable detailed logging:

DEBUG=gdt:* getdone

For specific modules:

DEBUG=gdt:llm getdone          # AI interactions
DEBUG=gdt:taskwarrior getdone  # Task operations
DEBUG=gdt:session getdone      # Session management

Next Steps

• Conversation — Learn effective conversation techniques
• Commands Reference — All available commands