FAQ
Frequently asked questions
Short answers to the questions people ask first.
Is Workloom a folder sync tool?
No. It is a package manager with a plan and apply step: packages are versioned in a registry, rendered into each provider’s files, and only files Workloom wrote are ever changed.
Which AI coding tools does it support?
Claude Code and Codex files are written directly. GitHub Copilot is supported for committed projections, which need a local approval. Gemini is preview-only: Workloom describes what it would install but writes nothing.
Where do my secrets go?
Nowhere. A package refers to a secret as {{secret:NAME}}, and Workloom resolves it on your machine at apply time from an environment variable, your OS keychain or an encrypted local vault. Values never reach the registry.
Can a package install a plugin without asking?
No. A plugin ref installs only when its id is on your approved-plugins allowlist; otherwise the trust gate reports trust.plugin_unapproved. `wl install --approve-plugin` adds it.
What happens to files I already had?
Workloom does not overwrite them: sync stops with sync.ownership_required. With --adopt it backs a file up before taking it over, and `wl unbind` puts the original back.
Does Workloom collect telemetry?
Not by default. New workspace manifests set telemetry to off, and the CLI sends none. The registry refuses events that carry prompts, outputs, file content, paths, diffs, usernames, emails or tokens.
How do I install the CLI?
Run it from a source checkout with pnpm, or use the test installer from the public releases repository, which installs a checksum-verified binary to ~/.workloom/bin. It is not on npm or Homebrew.
Is there a desktop app?
There is a Tauri desktop app, but today it is a sign-in shell (device-code login) and only test builds exist. Use the CLI for everything else.
Are the plans real?
No. Workloom has no billing; the plans page shows sample prices only.
Still stuck? Contact us.