How PeriCode works

  1. Choose context. Add notes, a folder or a selected passage.
  2. Use your provider. PeriCode sends the request through your selected connection and model.
  3. Control access. Vault limits and permissions govern file tools.
  4. Review the result. Follow sources and inspect revisions before applying them.

Saved conversations and plugin state stay in local storage. Cloud requests send prompts, attachments and tool results to your selected provider.

API keys and stored conversations are currently unencrypted. Provider apps and MCP integrations have their own data access.

Privacy and permissionsInspect the plugin source