FAQ

Does cnfgr work offline?

Yes. cnfgr is local-first — edits apply instantly to your local state and work without a connection. When you’re back online, changes sync and converge with your other devices.

Does cnfgr sync my API keys or .env files?

No. Secrets are never synced. Values are scrubbed and replaced with placeholder references before anything leaves the device, and re-hydrated only on your own devices. See Secrets & privacy.

What happens if I edit the same thing on two devices?

Most concurrent edits merge automatically. When there’s a genuine conflict, cnfgr defers the write, writes the incoming version next to your file as a .cnfgr-conflict-* file, and offers a three-way merge to resolve it. See Conflicts & versioning.

How does cnfgr know two folders are the same project?

It resolves project identity from the git remote URL first, then a .cnfgr marker file, then a manual mapping — never the folder name. See Projects & identity.

Which tools are supported?

Claude Code, Codex CLI, Gemini CLI, GitHub Copilot, and Cursor — with varying fidelity. See the support matrix.

Can I roll back a change?

Yes. cnfgr keeps version snapshots so you can review history and roll back to an earlier version, which then syncs out like any other edit. See Conflicts & versioning.

Is telemetry collected?

Only if you opt in. Telemetry is off by default.

Does cnfgr sync hook scripts?

No. Synchronising executable hooks is a security risk and is intentionally out of scope.