Tools, connectors & plugins
What Celeris can do is the set of tools it can reach. It starts with built-in tools and grows with whatever you connect or install. Every tool, whatever its source, runs under the same approval rules.
Built-in tools
Every install can run a command in a working folder, read and search files, list folders, resolve a loose reference like "the invoices folder", and put a result on your clipboard.
Common software tasks are packaged on top of these as whole-task tools: raise a pull request, review one, fix its failing checks, upgrade dependencies, start local servers. One tool per job means one decision and one approval, rather than a chain of steps that each have to go right.
Connectors
A connector brings a service you already use, such as a calendar, mail, documents, chat or an issue tracker, into Celeris as tools. Add one from Settings → Tools → Connectors.
Connectors that need an account sign you in through the provider's own consent page in your browser. The token is stored in your operating system's keychain and never shown in the app. Disconnect from the same page, or revoke access at the provider.
A few providers, Google Workspace among them, register no app for Celeris automatically. For Google Drive, Gmail and Calendar, create a desktop OAuth client in your own Google Cloud project and paste its client ID and secret into the connector's page before you connect.
Every operation a connector adds is checked like any other tool, so reading your calendar runs without asking while sending mail asks first.
MCP servers
Celeris speaks the Model Context Protocol. Add a server under Settings → Tools → Connectors → Add MCP server and its tools appear alongside the rest.
Plugins
A plugin bundles skills (written procedures for a kind of work), the connectors those skills need, and the reference notes they read. You install, update and remove it as one unit.
Plugins come with the desktop app downloaded from the Celeris website. The Mac App Store version does not include them.
Open Settings → Plugins → Add plugin and paste the plugin's git URL. Its card shows whether it is ready:
- Ready: everything it needs is connected.
- Degraded: it works, but an optional connector is missing. The card says which skills are affected and how to fix it.
- Blocked: a required connector is not connected yet. The card says what to connect.
Press Check to re-run this after connecting something. Update fetches the latest version and only replaces the old one once the new one verifies.
A plugin adds instructions, never permissions. It cannot grant itself a tool or skip an approval, and a connector it names is offered to you to connect, never switched on for you.
To write one, make a folder with a plugin.json that names its skills,
connectors and files, and write the skills as Markdown. There is nothing to
compile. Sharing a plugin is sharing its repository.
Tools you make yourself
Two routes, neither of which needs you to write a connector.
A user tool wraps a shell command you already type, so deploy-staging or
tail-prod-logs becomes something Celeris can call. It declares what it
touches, and how far Celeris trusts it is capped because you wrote it, not
because it says it is safe.
A skill is a reusable way to do a job. Open Settings → Tools → Skills, describe a repeated task in a sentence or two, and let Celeris try it. Each attempt that misses patches one step. When the plan survives a run unchanged, it becomes a tool Celeris can call like any other. Every step asks for approval wherever that tool would ask in your own conversation. Like plugins, skills are not in the Mac App Store version.
Which tool Celeris picks
Celeris keeps a local record of which tools ran on each task and whether you kept the result. It uses that to prefer the tools that have worked on similar tasks before. Denying a call keeps Celeris off that tool for the rest of the session, and rejecting a wrong result teaches it more than fixing it by hand.
To keep a tool out of reach entirely, disable the connector, or a single operation, in Settings → Tools.