docs / 10

Connections and tasks from outside

Connections

connect opens a catalog of about fifty services the crew can use while it works: web search, a browser, GitHub, Notion, Linear, Slack, databases and more. Press Connect on a card. Some run on this computer, some need no account, some ask for a key, some open the service's sign-in page.

The Chef tells each step which connections it may use (at most three on low flame), so a connection nobody needs costs almost nothing.
Anything a cook reads through a connection becomes part of its prompt and is sent to the AI provider in use.
Each connection is a program running with your permissions, and some can change things (create issues, write to a database). There is no approval step for tool calls, so connect only what you trust.
Manage on a connected card lets you switch it off, disconnect it, or keep it for certain cooks only (Who may use it).
Not in the catalog? Add a custom MCP server at the bottom: a name and the command that starts it. Its settings (tokens) are stored encrypted.

Google. The Google card lets the cooks search your Drive, read Docs and Sheets, search and read Gmail and list Calendar events. It is read-only and you choose which parts. It needs your own free Google sign-in keys (about ten minutes, once); the dialog walks you through it. This has been tested against a stand-in for Google, not yet with a real account.

The connections dialog: search, categories, and Connect.

Starting tasks from outside

Under connect -> Start tasks from outside:

Your own webhook. Kadhai makes an address and a token (shown once). A program on this computer posts {"text": "what to do"} with the token to start a task.
GitHub issues. An open issue that carries your label (default kadhai) becomes a task, once.
Linear issues. The same with a Linear label.
Telegram bot. A message to your bot from a chat you allowed becomes a task, and the report is sent back.

Nothing on the internet can call Kadhai: these services are checked once a minute from your computer. A task that arrives this way is treated as untrusted text: it queues like any other, and its commands still wait for your OK.

This page comes from the user guide in the repository. Something unclear or wrong? Tell us.