Riftri

Troubleshooting

Start in the repository with your destination:

View .md / Copy .md

riftri doctor --destination ../app-auth
riftri status

Read the reported blocker before retrying; Riftri stops rather than silently making a full copy.

Command not found

Follow the installer's printed PATH instructions, then run riftri --version. On Linux, a runtime error can mean the wrong glibc/musl binary; rerun the installer.

Unsupported storage or checkout

Check filesystem compatibility. Custom filters, submodules, or checkout hooks also block creation; do not disable a needed hook — use ordinary Git outside interception. Missing LFS objects: Git LFS. Partial checkout: sparse directories.

Git is not using Riftri

riftri shell status

You need both repository enablement and an activated shell or process in the same terminal or tool. Embedded Git libraries and absolute Git paths bypass the hook.

An operation was interrupted

Follow the diagnostic's recovery command. With the default state location:

riftri repair

Keep any custom repository or state-directory arguments. Repair preserves changed or ambiguous paths. Never delete internal state directories to clear an error.

Removal or cleanup is blocked

Commit or back up local changes first; --force discards them. If gc reports a base claimed by an interrupted operation, repair that operation first.

Still stuck? Open an issue with your OS, riftri --version, and the diagnostic output (review it for private paths first).

Edit on GitHub