How do integrations work in codus?
An integration is a connection between codus and a service you already use, such as Vercel, Stripe, or Google. You set them up in one place: open the gear (⚙), click See all settings →, then click Integrations. Each service is a card with a Connect button. Some cards sign you in through your browser, and some ask you to paste an access token, with step-by-step help printed right on the card. Once a service is connected, your agents can work with it on your behalf, and they never see your login. The page opens with the line "Connect codus to the tools you already use."
Where integrations live
- Click the gear (⚙) in codus, then See all settings →.
- In the settings page, click Integrations in the list on the left.
- Use the Search integrations… box at the top to filter the cards by name.
The cards are grouped by category, for example Source control, Hosting + deployment, Finance + accounting, Advertising, Analytics + tracking, AI, and more.
The two ways a card connects
Every live card works one of two ways, and the card tells you which:
- Sign in through your browser. You click Connect (for example Connect GitHub or Connect with Google), your normal browser opens, you approve access, and you come back to codus. GitHub, Google, and Xero work this way.
- Paste an access token. The card walks you through creating a token on that service's website, gives you a box to paste it into, and you click Connect. Vercel, Cloudflare, Stripe, Supabase, and the AI providers work this way.
Either way, a connected card shows a green Connected label, usually with your account name next to it (for example "Connected as @yourname"). To remove a connection, click Disconnect on the card and confirm.
Live cards versus "Coming soon"
Below the live cards is a group headed Coming soon, shown greyed out with the note "Not connectable yet — tell us which one you want first." Those cards have no Connect button. As of this writing the Coming soon group holds GitLab, Netlify, Cloudflare Pages, Bitbucket, Slack, Discord, Linear, Jira, Asana, ClickUp, Notion, Sentry, Figma, and Zapier. If a card you want is greyed out, it is not ready yet, and no amount of clicking will connect it.
What connecting gives you
Once a service is connected, any agent in any of your projects can use it when you ask. You can say things like "list my Vercel deployments", "what did my Stripe revenue look like last week", or "pull my Google Ads spend", and the agent works through your connection. The point of connecting is that the agent gets to act on your real account without you pasting keys into a chat.
Where your credentials are kept
Your tokens and keys stay on your Mac. codus encrypts each one with the macOS Keychain and saves it in the app's own folder on this machine (~/Library/Application Support/codus/). A credential is only ever sent to the service it belongs to. It is not uploaded to the codus cloud, it does not sync to your other Macs, and it never enters an agent's chat, a terminal, or an environment variable. Because the connection lives on this machine, each Mac you use connects separately.
How do I know it worked?
The card shows a green Connected label, and for most services it adds a detail it read back from your account, such as your username, your organisation name, or how many projects or domains it can see. That read-back is your proof the credential is valid, not only saved.
Common problems
- The card I want is greyed out. It is in the Coming soon group and cannot be connected yet.
- My token was rejected. Follow the steps on the card exactly. Several services need a token with specific permissions (scopes), and a token missing one will fail. Re-create it with the scope the card asks for and paste it again.
- I connected on my other Mac, but not this one. Connections are per machine and do not sync. Connect again here.
- I disconnected by mistake. Click Connect again. For a browser sign-in you approve once more; for a token you paste a fresh one.