The Sidekick CLI provides multiple levels of security controls:
- Telemetry management: Implementation
sidekick --no-telemetrySentry bug tracking and usage analysis data collection can be completely disabled. - key protection: All API keys are stored in the
~/.config/sidekick.jsonIt is recommended that you set the file permissions to 600. - local processing: Support for future integration of localized LLM solutions such as Ollama, where sensitive code may not be processed in the cloud.
- session isolationThe /clear command clears the current session history completely, and /compact compresses sensitive information.
For enterprise users, it is recommended to host your own MCP server to tightly control the flow of data, and to have a cost-budgeting feature (sidekick cost --set-budget) Prevent accidental overutilization of cloud APIs.
This answer comes from the articleSidekick CLI: An Open Source Claude Code Replacement ToolThe
May not be reproduced without permission:AI productivity tools " How do I protect my privacy and data security when using the Sidekick CLI?
