How do integrations work in codus?
An integration connects Codus to a service you already use. Open Settings → Integrations, find its card and follow its connection instructions. Agents can then use permitted service features when you ask.
Before you start
Connect only accounts you are authorised to use. Review permissions and potential charges first. Connecting a service does not authorise purchases, destructive changes or publishing without your request.
Connect a built-in service
- Click the gear → See all settings → Integrations.
- Use Search integrations… to find the service.
- Click Connect. Complete browser approval or paste the requested token into the card's credential field.
- Check the returned account details.
- To remove access from this Codus installation, choose Disconnect and confirm.
Connections are set up on each computer. Do not expect a service connected on one machine to become connected automatically on another. Never paste credentials into agent chat or documentation.
Which kind of extension do I need?
A built-in card is the starting point for a named supported service. Coming soon cards are not connectable.
Use custom integrations for another service's API. Use MCP servers for a separately provided tool server. Use Skills for reusable instructions. They do different jobs.
Account and usage checks
See work-tool connection details for ClickUp, Figma, Netlify and PostHog, and email sending for Postmark, SendGrid and Mailgun.
View usage shows supported balances and allowances. It does not replace the provider's billing statement or the Claude/Codex usage panel.
How do I know it worked?
The card shows a connected state with the intended account details. A read-only check of a relevant resource confirms the permissions needed for your task. If rejected, check credential type, scopes, account and region before trying again.