hermes-data-sync

Initialize a git repository in ~/.hermes, add a .gitignore excluding caches and *.db-wal/*.db-shm files, then push to a private GitHub repo using a fine-grained PAT with Contents read/write permission embedded in the remote URL.

Always run git pull origin main before pushing to avoid non-fast-forward rejections. Commit with git add -A and push after pulling, using --rebase if conflicts appear between devices.

A 401 error means the GITHUB_TOKEN in ~/.hermes/.env is a placeholder or invalid. Generate a fine-grained PAT with Contents read/write access scoped to your backup repository and use it directly in the remote URL.

No. These are SQLite Write-Ahead Logging files that change on every write and cause constant diffs and conflicts. Exclude them in .gitignore with *.db-wal and *.db-shm patterns.

Hermes memory has a hard 2200-character limit across all entries. When importing external memory exports, distill each fact to under 200 characters, check the usage field after each memory call, and prioritize operational facts.

Yes, but Termux git handles symlinks differently, so use git add -A instead of -u to track all files. Large state.db files can slow pushes, so prune old sessions before backing up.