Connect your services
Connect a service once, and the agent can read it and act in it.
The work you ask for lives in other tools too. Connect them once and every conversation can reach them.
- what is left on my Linear board?
- summarise the new Sentry errors since Friday
- draft a reply to the thread about pricing
/connect, also spelled /connections, opens one list of everything CodeAF can reach for you. At the top sit the model services; below them your accounts, grouped by kind: analytics, billing, developer tools and more, over a hundred in all. Type a few letters to filter it.
Try it in CodeAF
- Where
In a conversation in your repo.
- Type
What issues are open on my Linear board right now?- You see
The agent looks for a service that can answer, then asks
connect your Linear account?with1 connectand2 not now. Press 1, approve on Linear's page, and the answer follows in the same turn.
It asks while it works
You rarely need to open the list first. When a request needs an account you have not connected, CodeAF stops and asks, right in the conversation: connect your Linear account?, with the turn asked for something only that account can answer, and 1 connect or 2 not now. Press 1 and the service's sign-in opens; its tools arrive within the same turn, and the agent carries on with the question you asked. Press 2 and it tells you what it could not see and how to go on without it. A key service asks for the key in a masked box instead. When nobody is watching, as in a task or a routine, it never connects on its own: it says it needs you.
Two ways in
A row tagged sign in opens your browser: Google (Gmail and Calendar), Slack, and hosted tool servers such as Linear, Notion, Sentry, GitLab, Datadog, Supabase and Cloudflare. A row tagged key opens a box in place, paste your Mixpanel key, with a line saying where to find it. A key can also be a variable name like $MIXPANEL_KEY, read fresh each time it is used. Keys and tokens stay in your profile on this machine. To see or change everything at once, type /connect: it opens the whole list, filtered as you type.
What it may do
Every account carries two switches in /settings, on the Connections tab: read what is in the account, which is on, and act in it in your name, which asks first. Sending mail, creating calendar events and posting to Slack always ask, even when you run without approvals. Tasks inherit your connections but cannot add new ones, so nothing signs in while you are away.
Things to build
- Issue triage from your tracker: a Monday routine that reads the new Linear issues, groups duplicates, labels them and drafts the week's list. Schedules
- Errors to fixes: a watch on Sentry that opens a conversation for each new error class and proposes a patch.
- A morning brief: calendar, unread mail and yesterday's merged work in one short note on home.
- Release comms: after a tag, post the release notes to a Slack channel, with you confirming the post.
Go further
Watches: Say what you are waiting for; CodeAF looks on a timer and starts work only when the answer is yes.
Coming soon: describe the org you want and CodeAF builds it: teams, managers, budgets, standing orders.