Tracking And Sharing

Capture your local config and sync it safely.

Pick what to track

Start with the files you actually care about. LCT routes them automatically:

• Home dotfiles such as ~/.zshrc land in dotfiles.
• Config directories under ~/.config (for example alacritty, nvim) land in configs.
• Everything else is treated as other.

Add paths and let LCT categorize them:

lct file add ~/.zshrc  
lct file add ~/.config/alacritty  
lct file add ~/work/custom.conf  

To keep the list tidy, remove entries that no longer exist:

lct file list  
lct file remove ~/.config/alacritty  

Gather into your remote

Save a snapshot to your remote repository after reviewing the plan:

lct gather          # copies tracked files, warns about secrets  
lct gather --force  # overwrite existing copies in the remote  

After a gather you can push the prepared remote (~/.local/share/lct/remote) to Git to share or back it up.

Bootstrap a new machine

Recreate your setup on another machine using the same config repository:

lct init                  # writes ~/.config/lct/config.yaml  
lct bootstrap             # restores tracked files and configs  
lct reload                # refresh aliases + env vars in your shell  

If a local config folder already exists and you want to replace it, pass --force to lct bootstrap.

Keep things clean

Remove unused copies from the remote or cache when they accumulate:

lct prune            # clean tracked config + plugin files  
lct prune --plugins  # focus on plugins only  

This helps avoid stale files being reapplied on future bootstraps.