Safety and privacy

Claudioo is designed so you can hand it a project and let it work freely without worrying about damage. Here's the short version of what that means in practice.

What Claudioo can reach

• Your project workspace — full read and write access to your linked GitHub repo's files. Changes stay in the session; nothing is pushed.
• Base Odoo source — read-only access to all installed Odoo versions (community and enterprise) for reference.
• Your live Odoo instances — only via SSH using a key you generated and authorized yourself. See Connect to Odoo instances.
• muchdoo data — only with the API key you configured. Claudioo sees what you can see.
• Slack — only the channels and DMs your Slack account has access to. Read-only.

What Claudioo can't do

• Push code to your repository. Claudioo can commit locally inside the session but it can't push. You review and push yourself.
• Post on Slack. No posting, editing, deleting, or DMs — the OAuth scopes are read-only and you can verify this on Slack's consent screen.
• Reach files outside your workspace. System files, other projects, and personal directories are off-limits.
• Run system-level commands. No sudo, no installing system packages, no modifying system configuration.
• Connect to arbitrary servers. Only servers you've authorized your SSH key on are reachable.

Where your data goes

• Conversations are stored in much.'s own database so you can come back to them and share them with teammates.
• Each consultant uses their own credentials — your SSH key, your muchdoo API key, your Slack token. Claudioo doesn't have a shared service account for these.
• Sharing a conversation makes the full transcript visible to anyone at much. with the link. See Share a conversation for what that includes.

Learn more

• Connect to Odoo instances — How SSH access works
• Share a conversation — What's in a shared transcript
• FAQ — Common questions about access and limits