FAQ
Frequently asked questions
Short answers to the questions people ask first.
Is Client OS a hosted service?
No. It is a codebase you clone and run on your own accounts. There is no sign-up, no hosted instance and no paid plan.
Can I clone it?
If you have access to the catesworks organization on GitHub. The source repository is private; the docs site and the clientos-context skill are public.
Can I download the CLI or the desktop app?
Not yet. The release workflow can build both, but no release so far has published binaries, and the CLI is not on npm. Build them from the workspace.
Is the desktop app finished?
No. apps/desktop is a Tauri 2 shell with a placeholder frontend and a bundled sidecar: a starting point for a desktop client.
Do I have to keep the CRM?
No. clientos is a worked example of the patterns. Keep it as a reference or remove its routes, pages, commands and schema and build your own domain.
Does it use Postgres row-level security?
No. Org-scoping is checked in the application layer: every clientos route checks that the record belongs to one of the caller’s organizations.
What does the clientos-context skill do?
It takes free-form notes about a Client and routes each fact into the right one of the eight Context files, instead of appending one blob. It is on npm as @client-os/skill-clientos-context.
Where are the docs?
On the documentation site linked in the header: getting started, architecture, deployment, usage examples and the skills catalog.
Still stuck? Contact us.