Plugins

Choose a plugin to install

Use Settings → Available plugins to see which plugins this instance may install and what each one adds.

What the catalogue contains

The catalogue is Chetty's curated registry, and only plugins covered by the installation licence appear in it: you cannot install from an arbitrary address or a local folder.

Chetty fetches the catalogue from the licensing server over HTTPS with the installation licence, revalidates it on each refresh and caches it locally for offline use. Anything outside the licence is hidden, and installing or updating it is refused. Each download is verified against the catalogue's checksum and size before it is installed.

The catalogue is separate from the Chetty package, so what is available and in which version can change without a new core release.

Version requirements

A plugin may require a minimum core version (requiresCore) or an exact shared API version (requiresSharedApi). When the running core is too old, or does not offer the version the plugin names, installation is refused; upgrade Chetty first.

An automatic update holds a plugin back while it needs a newer core than the release being installed, and advances it on a later run once the core is new enough. A plugin's own details and the catalogue card show its current version and core requirement.

What installing asks you to approve

A plugin that declares mutating capabilities asks for your acknowledgement before it can work. The request can cover access to prompts, tools, events, workflows or users.

Until you confirm, the plugin is not enabled and an update is not applied. Chetty keeps what you acknowledged and asks again when an update requests additional capabilities. Read the request rather than approving it by habit: a plugin runs as part of Chetty, not in a sandbox.

Chat and account integrations

Plugin	Adds	Important limit	Guide
`discord`, `telegram`, `whatsapp`	Chat-platform bots.	Each needs its own credentials and sender policy; platform permissions still apply.	Channels
`msteams`	Teams bot and delegated Microsoft 365 tools.	Requires Entra and Azure Bot setup; tools follow the linked account's Microsoft permissions.	Microsoft Teams
`onedrive`	Two-way sync with a Project or folder, including folder selection, pausing, manual sync, and conflict resolution.	Requires a linked Microsoft identity; remote deletions go to mirror trash.
`skills`	Reusable instructions and a skill manager.	Instance skills require operator authority; personal skills stay within their account.	Skills
`chatbot`	Visitor chatbots for third-party websites.	Each chatbot is a non-interactive account bound to exactly one managed Project.

Scheduling and media integrations

Plugin	Adds	Important limit	Guide
`browser`	Private browser sessions and page inspection, plus page capture for Sites.	Each account has its own browser; web traffic passes through the network proxy. Site capture uses a separate browser session limited to one public HTTPS origin.
`cronjob`	Scheduled prompts, one-shot wake-ups, and the Automation page.	Personal jobs run with the owner's permissions and are capped; advanced shell guards require privileged scope.	Scheduling
`image-gen`, `image-edit`	Generate a PNG or edit a project PNG/JPEG or public image URL; source replacement requires an explicit output path and overwrite option.	Require a configured image provider; calls can take up to two minutes.
`voice-bot`	Outbound calls through a configured service endpoint and secret.	Uses full international phone numbers; calls cannot be undone, so never guess a number or retry an uncertain call.
`twilio`	Outbound telephone calls through Twilio. Publishes the `phoneCalls` control for other plugins.	A regional key works only in its region. Each started minute is billed at the price you set; the per-call answering-machine detection fee is not included.

Project and developer integrations

Plugin	Adds	Important limit	Guide
`editor`, `github`, `lsp`	Project editing, the GitHub connection and Project repository mapping, and language-server tools.	Project access applies; the editor's separate System view is for administrators, and each account connects its own GitHub identity.	Code Tools
`sites`	Managed Project previews and proxy publications.	Requires the Sandbox plugin. New sites forward to an application already running in a Project; public visibility needs confirmation. Existing file Sites retain their addresses and recovery files but serve maintenance until republished from a running Project service. File publication and rollback are no longer available.

Business integrations

Plugin	Adds	Important limit	Guide
`raynet`	Raynet CRM tools for searching, reading, creating, updating, and acting on records, plus a CRM page and a skill.	Works under a company login unless a person switches on their own credentials. The access mode caps what a turn may change, and raw API requests are off by default.
`meeting-confirm`	Confirms tagged Raynet meetings by phone and sends exception notices to the salesperson in Teams.	Uses the `raynetMeetings` control from Raynet; the consumer must report unavailable when Raynet is absent.

Session and productivity integrations

Plugin	Adds	Important limit	Guide
`todo`	A per-conversation task list with live progress.	Installed from the registry, not bundled.	Sub-agents & Workflows
`brainstorming`	A skill that makes the agent clarify and get a design approved before creative work.	Limits are not documented yet.
`stats`	Model usage statistics for tokens, spend, and cache use.	The daily trend covers at most the latest 90 days.

Plugin guides list the tools, configuration fields, permissions and limits of each integration. Start from a task guide for Channels, Projects and environments, Scheduling, Skills, MCP, Memory or Sub-agents and workflows.

For installing, updating and removing a plugin, see Install and update plugins. For its settings afterwards, see Configure a plugin.