Skip to content

Getting started ​

This page takes you from your first sign-in to the first piece of work an agent does for you: signing in to the app at app.kadmo.ai, the workspace your account starts with, your first agent, and handing that agent a task through Ask Kadmo. Each step links to the page that covers it in full.

Sign in ​

Open app.kadmo.ai. Kadmo sends you to its sign-in screen, where you sign in with your work email address or with Google (use the same work address if your company runs on Google Workspace). After sign-in you land on your account's workspace, or on the page you were opening when you were asked to sign in.

New accounts open by invitation for now. While Kadmo rolls out, signing in works for:

  • people who already have a Kadmo account, and
  • people an account admin has invited (see Account and settings).

Anyone else sees Kadmo is invite-only for now, with Sign in again and a link to write to info@kadmo.ai. Nothing is created for an address that is turned away. To try Kadmo before sign-up opens, join the waitlist at kadmo.ai/trial.

When sign-in is refused ​

ScreenWhy you see itWhat to do
Kadmo is invite-only for nowThe address has no account and no inviteAsk your team's admin to invite this exact address, then Sign in again; or write to info@kadmo.ai
Your team is already on KadmoYour company already has an account, and it only lets invited people joinAsk an admin of that account to invite you, then Sign in again
Use your work emailA new account needs a company address; public providers (Gmail, Outlook and the like) and temporary inboxes can't start oneTry again with your work email. If you already have an account, use the address you signed up with
Verify your email firstYour address isn't verified yetOpen the verification email, click the link, then Sign in again. Check spam if nothing arrived
Email sign-up is temporarily unavailableSign-up with a password could not create the accountContinue with Google with the same work address
Login FailedAnything else went wrong during sign-inTry Again

An invitation is waiting for you when you sign in with the invited address. You join the account with the role the admin picked (Admin or User). A person belongs to one account at a time, so an invite from a second account cannot be used while you are a member of another.

Your account and its first workspace ​

Your account holds everything you and your colleagues share: workspaces, agents, playbooks, integrations, the credit and the settings. Admins manage members on the Team page and the rest on Settings; Account and settings covers both.

A new account starts with:

WhatDetails
A workspaceDev Workspace, deployed to ~/workspace on each agent assigned to it
Three playbooksBug Fix, Feature Implementation and Hotfix, as editable copies of Kadmo's defaults
The Kadmo providerKadmo's models, used through the account's credit (see Models and credit)

Open Settings at the bottom of the sidebar and then Workspaces to see the workspace. Its card shows Setup n of 5 until it is ready. Setup has three steps, Assign agents, Connect code and the intake answer, and the workspace page walks you through each with one button. To get ready for the first run, open the workspace's Edit page and:

  1. On Code & files, add the git project agents should clone (Add project, then the repo URL). For a private repository, connect GitHub, GitLab or Bitbucket under Integrations first.
  2. Optionally, on Settings, under Work intake, link the Jira project, Linear team or Notion data source whose tickets should route here. Without a link, tasks you create in the workspace are internal Kadmo tasks.

Workspaces explains every part of the page.

Your first agent ​

Agents are virtual machines, hosted by Kadmo or in your own cloud account. Kadmo provisions them, keeps their configuration in step with your workspaces, and dispatches work to them. In this release an agent in your cloud runs on AWS, in an agent subnet peered with Kadmo's network; Agents says what works where.

  1. Connect a cloud account under Integrations: AWS, or ask for a hosted agent (see Agents).
  2. Open Agent Fleet in the sidebar and press Create Agent. The wizard asks for the machine, the agent app, the workspaces and the roles.
  3. When the agent comes online, it appears on the workspace's Agents tab. If you did not pick the workspace in the wizard, press Assign there. The workspace configuration reaches the agent at once.

Create an agent walks through the wizard, and Agents covers the fleet once it runs.

Your first piece of work ​

The quickest way to give an agent work is Ask Kadmo: you describe the work and Kadmo answers with a plan. Nothing happens until you press Start.

In this release Ask Kadmo is in preview. An account admin turns it on under Settings › General › Experimental features, and the setting applies to everyone in the account. Then:

  1. Choose the workspace in the switcher at the top of the sidebar, and press + New chat, or press ⌘K (Ctrl+K on Windows and Linux) on any page.
  2. Write the work, for example Fix the failing checkout test, or Create this feature followed by the ticket's link. Type @ to attach a repo, ticket, agent, playbook or workflow as context.
  3. Kadmo answers with a plan card: the repo and ticket, the playbook and the agent, the steps, an estimate in tokens and minutes, and what Start creates. Change it with Ask for edits or Edit.
  4. Press Start (in the ⌘K box, press Open in chat first: Start is on the thread). The run begins, and the thread shows the step the agent is on, the gate it passed and any question it has for you, up to the link to the pull request.

Ask Kadmo covers the box, plans, answers and sharing.

Without Ask Kadmo, + New chat opens What are we building?: write the change, bug or question, pick the Role, and press Start. That message starts a job on the workspace, and a free agent picks it up. To bring in many tickets at once, use the Tasks page (see Working with tasks).

Next steps ​

  • Workspaces: instructions, .mcp.json, skills and tracker routing.
  • Integrations: connect Jira, Linear, Notion and your git host.
  • Workflows and playbooks: what agents run, and how to change it.
  • Models and credit: the models, the credit and budgets.
  • MCP: use your account from Claude, Cursor, VS Code or Codex.