Sync

txi sync walks the directories configured under paths.transcripts and paths.summaries and reconciles the SQLite index with the filesystem. It is the primary command for keeping the index up to date.

txi sync

How it works

For each candidate file, txi computes a content hash and compares it against the stored hash:

• New files are parsed and inserted as conversations (or notes attached to a conversation).
• Modified files are re-parsed and updated in place.
• Renamed files are detected via hash and updated without losing the existing row.
• Deleted files cause their rows to be removed (unless --keep-orphans is set).

The output is a summary report:

new conversations:       3
updated conversations:   1
renamed conversations:   0
deleted conversations:   0
unchanged conversations: 142
new notes:               2
updated notes:           0
deleted notes:           0
elapsed:                 0.84s

Options

txi sync \
  --only path/to/specific.txt \
  --strict \
  --keep-orphans \
  --dry-run

• --only PATH — restrict sync to specific files. May be passed multiple times. Useful for re-indexing a single file after fixing a parser.
• --strict — abort on the first malformed source instead of warning and continuing.
• --keep-orphans — don't delete rows whose source files have disappeared.
• --dry-run — preview what would change without modifying the index. Sync runs against a temporary copy of the database, which is discarded afterward, so the report is identical to a real run.
• --config PATH — override the default config file location.

Stats

After syncing, check the corpus shape:

txi stats

conversations:       146
  with notes:        38
  kind=meeting       144
  kind=slack_thread  2
turns:               18,402
notes:               41
people:              12
date range:          2023-04-12 → 2026-05-08