Skip to main content
Display information about where adist stores project data, indexes, summaries, and configuration files.

​
Syntax

adist paths

​
Output Information

​
Storage Locations

​
Config File
path
Location of the main adist configuration file (typically in ~/.config/adist/)
​
Project Path
path
Filesystem path to the current project directory
​
Project ID
string
Unique identifier for the current project

​
Project Statistics

​
Indexed Files
number
Count of files in the project index
​
Has Overall Summary
boolean
Whether the project has an AI-generated summary

​
Physical Storage

​
Config Directory
path
Directory containing all adist configuration
​
Data Directory
path
Directory where project data is stored

​
Size Information

​
Overall Summary Size
size
Size of the project summary in kilobytes (if available)
​
Total Index Size
size
Combined size of all indexes in kilobytes

​
Example Output

adist paths

Storage Locations:
Config File: /home/user/.config/adist/config.json
Project Path: /home/user/projects/my-api
Project ID: 1234567890123
Indexed Files: 42
Has Overall Summary: Yes

Physical Storage:
Config Directory: /home/user/.config/adist
Data Directory: /home/user/.config/adist
Overall Summary Size: 2.45 KB
Total Index Size: 128.73 KB

​
Use Cases

​
Troubleshooting

Find configuration files when debugging issues: 
adist paths
# Locate config file to manually inspect

​
Backup

Identify what to backup: 
adist paths
# Backup the Config Directory shown
cp -r ~/.config/adist ~/backups/

​
Disk Space

Check storage usage: 
adist paths
# Review index and summary sizes
# Clear old projects if needed

​
Migration

Find data location for migration: 
adist paths
# Copy config directory to new machine

​
Configuration File Structure

The config file contains:
  • Project definitions and metadata
  • Current project selection
  • Indexes (both legacy and block-based)
  • Generated summaries
  • LLM provider settings

​
Data Persistence

All data is stored in: 
~/.config/adist/config.json
This includes:
  • Projects list
  • File indexes
  • Code block indexes
  • AI-generated summaries
  • Provider configuration

​
Privacy & Security

  • Config file contains project paths and code summaries
  • No source code is stored in the config
  • API keys should be in environment variables (not in config)
  • Summaries may contain sensitive information

Build docs developers (and LLMs) love

Get started for freeTalk to us