Curiosity CLI
The official command-line tool for the Curiosity Workspace. Test connections, upload front-ends, ingest folders, sync git trackers, and export/import workspace definitions from any shell or CI pipeline.
What is curiosity-cli?
curiosity-cli is a dotnet global tool packaged as the NuGet package Curiosity.CLI. It exposes every operation you would otherwise script against the Workspace's HTTP / Graph API, with consistent --server / --token arguments and kebab-case command names.
Use it to:
- Promote a custom front-end bundle between environments.
- Iterate on a custom front-end locally while talking to a remote workspace.
- Ingest files (folders, PSTs) into a workspace, with or without Active Directory ACLs.
- Export and import custom code (endpoints, indexes, scheduled tasks) between workspaces — the foundation of GitOps-style workspace deployments.
- Wait for a workspace to become ready, then run smoke tests, inside a CI/CD pipeline.
Install
dotnet tool install Curiosity.CLI --global
Then confirm:
curiosity-cli --help
Full instructions, update path, and offline install on Installation.
Common arguments
Almost every command takes the same two arguments — a workspace URL and a Library Token:
curiosity-cli <command> \
--server https://my-workspace.example.com/ \
--token $CURIOSITY_TOKEN
Short forms -s and -t work everywhere. Tokens can also be stored encrypted on disk with store-token so you can pass --token auto afterwards.
See Common Options for the full list (timeouts, mTLS, ignore-certificate-errors, environment variables, logging).
Commands
Where to go next
- Building a custom UI? Start with Custom Front-End development workflow — it uses
serveandupload-front-endend-to-end. - Ingesting an existing share or PST archive? See
inspectfirst, thenupload-folderoringest-pst. - Moving custom code between dev, staging, and prod? See
export-workspace-definitionsandimport-workspace-definitions. - Need to wait for the workspace before running smoke tests in CI? See
wait-forand Workspace deployment operations.