Appearance

Changelog ​

What changed in each release of the Kadmo app at app.kadmo.ai, newest first. Releases ship to every account at once; there is nothing to install or upgrade on your side. The stories behind the larger releases are on the Kadmo blog at kadmo.ai/blog.

1.10.0 — 2026-10-20 ​

BYOK ​

  • Your AI providers and agent apps on one page. BYOK, under Configure in the sidebar, lists the account's AI providers as rows, with the one that serves lit: Kadmo serves, with the credit left, or Your key serves. Its second tab holds the agent apps. The AI providers have left Integrations; old links land on BYOK, and /agent-apps opens its Agent Apps tab. See BYOK › Providers and Agent apps.

Guardrails ​

  • Every limit on one page. Guardrails, right after BYOK, holds the budgets, data residency, the models' switch, content rules and the call rate. Every budget link lands here, and Settings › Billing keeps one line about the budgets. See Guardrails.
  • Data residency for the account and each workspace. An admin picks the regions the account's models may run in, EU, US or Global, and a workspace can narrow them. A call outside them is refused with the reason and the fix. See Data residency.
  • A switched-off model is refused on every lane: Ask, Slack, Microsoft Teams, Goals, chat agents and agent jobs, pinned agents included. See Models.
  • Content rules for chats. Kadmo reads every message of Ask Kadmo, Slack, Microsoft Teams, Goals and chat agents before it leaves for the model: Personal data, Keys and secrets and up to 25 patterns of your own can each be audited, masked or blocked, with a switch per detector; each rule shows what it found this month. See Content rules.

Goals ​

  • Start a task from its row. Start · ‹playbook› on a goal's task adds the task to Tasks and approves it in one press; the ▾ picks another playbook or adds it for approval only. The epic's head starts all of its tasks that can start. See Start a task from its row.
  • A done epic folds. A finished task stays a row while its epic is open, and an epic whose tasks are all done folds into one line.

Tasks ​

  • The work leads while it runs. While anything is in Active, the card at the top of the page folds to its top row, and the work in flight comes first. See Add tickets.
  • One playbook picker. Every place that picks a playbook opens the same picker: the playbook the ticket's type routes to first, then yours and Kadmo's. A playbook no agent here can run is listed, locked, with the reason. See The playbook picker.
  • Plain words. A task waiting for you reads Needs approval, and Start replaces Dispatch: Start now on a queued job, Start job on an automation, Remove from Tasks on a task.

Agents ​

  • A finished Self Update frees the agent. An agent whose runtime has never run a components pass takes work again as soon as its Self Update ends, instead of after a 15-minute window; a pause put back after a session hold keeps the agent paused; and clearing a Self Update's hold says that its version move is dropped. See Self Update.

The app ​

  • Experimental features is gone. Goals, Ask Kadmo with the ⌘K box, task bulk actions with merge and live agent-review suggestions are on for every account, and the switch under Settings › General is gone: nothing needs turning on. The Create-Agent wizard offers the App Builder profile to every account.
  • You are always in a workspace. The switcher no longer offers All workspaces. The first time you sign in, the app opens your account's first workspace; an account with no workspace yet opens on Workspaces, where an admin creates the first. Every page, search and count shows the workspace you are in.
  • An account Kadmo's team creates for you starts complete. It has its first workspace and its own copies of the default playbooks from the start, as an account created by signing up does.
  • One size of tabs, one row of filters. A page's own tabs are one size everywhere, and every filter is one row of chips. Goals comes before Tasks in the sidebar.

1.9.1 — 2026-10-19 ​

Goals ​

  • One list of tasks. A goal's tasks are one list, in the order they can start: the task, what it waits on (After), its state, who works it and its run. Done tasks fold under one row.
  • The composer says where your words go. Chat is answered at once by the model as the step's role; Agent job sends them to your agents as the step's playbook.

Agents ​

  • Select agents without checkboxes. Ctrl-click a card (⌘-click on a Mac) to mark it. One Add component button below the list opens the dialog with the marked agents ticked, and Escape clears the marks.

1.9.0 — 2026-10-18 ​

Ask Kadmo ​

  • Speak your request. A microphone in the Ask box, in a goal's chat and on the chat page. From an empty box the words heard are sent as your question; over a draft they join it and wait for Send. The note stays with your message. See Speak and Voice.

Agents ​

  • An update hold ends within one pass. An agent waiting for a component it was asked for is free again after one components pass at most; an agent whose runtime has never run a pass is not held for a component; an agent's own Self Update passes the hold. See Agent updates.
  • Browser slots. Beside Parallel jobs, an owner sets how many browser-holding jobs an agent runs at once. Until the agent's runtime reports a browser session per job, every agent keeps one. See Parallel jobs.

The app ​

  • Kadmo Light, refined. The lit canvas on every page, panels and dialogs on their own elevation; Dark is unchanged. Mails follow the same colours.

1.8.1 — 2026-10-16 ​

Agents ​

  • A Self Update cut at its ceiling keeps the agent held. When a Self Update is stopped at its 20-minute ceiling and the stop could not be confirmed, the agent stays held until its session is gone, until you press Resume, or for 24 hours; the fleet card reads Held, and a pause under it is kept. A failed job names its step and the step's reason. See Holds.

1.8.0 — 2026-10-16 ​

Slack ​

  • A thread is a conversation. A reply in a thread is decided with the thread before it, so continue starts the step the last report proposed, with what was said further up. When a job a message started ends, the thread gets the agent's own report: the verdict, a summary and the links it chose. See A message in the channel.

1.7.0 — 2026-10-16 ​

Agents ​

  • Agent updates. An agent's page lists what it runs, item by item: its components, its runtime versions, and the skills and files of its workspaces, each with the version it is at and what is on its way. Add component adds one to a running agent, Retry repeats a failed one, and the fleet list adds one to several agents at once. A change waits for a busy agent and lands when its job ends. Self Update brings an agent to its pinned versions, or to the latest, with a rollback when a version does not come up, and ends within 20 minutes. Auto Update Agent, off by default, lets an agent take automatic changes at its idle moments. See Agent updates.
  • Parallel jobs. An agent's owner sets how many tracked jobs it runs at once, one by default; each workflow says whether it can share an agent; the fleet card shows the slots taken, and Dispatch now asks before going past them. The agent needs the Kadmo Agent Runtime 0.2.0, which its Self Update brings. See Parallel jobs.
  • Every job runs in a named workspace. Channels, automation rules, the run tools and the Run form say which, and a job's page streams the agent's transcript while it runs.

Slack ​

  • Files with a request. A file posted with a request in a registered channel reaches the work: the agent reads it from Slack through a signed link that lasts seven days, and Kadmo keeps no copy. Your Slack app needs the files:read scope and a reinstall. See Setting up the Slack app.

1.6.0 — 2026-10-13 ​

Asking Kadmo where you work ​

  • The result on the ticket. When the work a Jira request started ends, Kadmo answers with ✓ or ✗ and what came of it. See The replies.
  • Slack and Teams on the same step. A message in a registered Slack channel or a Teams chat goes through the same decision, against the channel's or the workspace's list, and Kadmo answers in the Slack thread or the Teams chat. See Slack and Microsoft Teams.
  • Slack identities on Team › People. A person's Slack user can be linked next to their Jira user. See People.
  • The Slack app asks for more scopes. An existing Slack app needs the new scopes added and a reinstall. See Slack.
  • Teams: All current workflows. A workflow added after the Teams list was saved is no longer included on its own; tick it in the list. See Microsoft Teams.

Reporting ​

  • Kadmo's notices. What Kadmo itself writes at Started, Needs you and Done, on the ticket, in Slack, in Teams and by e-mail, with the presets Standard, Only when needed and Silent. Nothing changes until an admin changes it. See Kadmo's notices.
  • Per workflow and per playbook. A workflow and a playbook can override the account's notices. See Overrides.
  • My notifications. Each person turns their own Slack DMs, Teams DMs and e-mails off under Settings. See My notifications.
  • The pause comment waits two minutes. A run's Needs you comment is posted about two minutes after the pause, and not at all if the run moved on in that time. See How a notice is delivered.

Models ​

  • Settings › Models. Every Kadmo model under its provider, with its region, context window and prices. Star the models you use most; an admin switches a model off for the account and makes a model the default there. The Kadmo card on Integrations no longer has a model dialog. See Models.
  • A shorter model picker. It lists only the models ready to use, Favourites first, with Manage models at its foot. See Pick the model.
  • Economy. The model tier named Cheap is now Economy. See Model tiers.

1.4.0 — 2026-10-10 ​

Asking Kadmo in Jira ​

  • Ask in a Jira comment or with a label. Write @kadmo and what you need on a ticket, or add the rule's label, and Kadmo decides which of the allowed playbooks and workflows the request asks for, starts it and answers on the ticket. See Requests by comment and the Kadmo LLM decides action on Automations.
  • New request rule. The Jira dialog opens the automation form filled in for a request rule. See Requests by comment.
  • Who may start what. Each workspace lists what a request may start and who may ask; Team › People links a person's Jira identity and can narrow their own list. See Started by request and People.
  • What a request costs. Small calls on the account's provider, on the Automations lane; without a provider, Kadmo answers with its menu. See What it costs.

Reporting ​

  • Task setup › Reporting. One page for what agents write on a run's ticket and pull request: the report shape, its details and a preview, set for the account, and a playbook step can set its own. Nothing changes until an admin changes it. See Agent reports.

1.1.0 — 2026-10-06 ​

Models and credit ​

  • A new price sheet. The sheet dated 2026-10-06 replaces the one of 2026-10-01 that 1.0.0 charged. The current prices are on kadmo.ai/pricing; how a call is charged is on Models and credit.

Tasks and runs ​

  • A ticket's priority shows wherever the ticket does. The priority your tracker gives a ticket (Highest, High, Medium, Low or Lowest) now appears on the Tasks list and board, the Active lens and the intake preview, the Validation lens, the queue and the job page, the workspace Overview's waiting work, and the run's header. Highest and High stand out, and Medium, the most common, stays quiet on list rows.
  • Set a priority when you create a task. The form that creates an internal task, and the issue panel on the Tasks page, have a priority field. When the task is filed in Jira or Linear, the priority goes with it.
  • The queue explains its order. The position in the dispatch queue states the rule it follows: your own reordering first, then ticket priority, then age.
  • MCP tools carry the priority. review_tasks and get_task return each pooled ticket's priority, and work_on_task echoes it. See MCP tools.

1.0.0 — 2026-10-06 ​

The first production release of the Kadmo app, at app.kadmo.ai.

Sign-in and accounts ​

  • New accounts open by invitation. Who can sign in, and what everyone else sees: Getting started.
  • Accounts, members and invites. Admins invite colleagues as Admin or User, manage roles and company domains on the Team page. See Account and settings.
  • Credit and budgets. Kadmo's models are paid from the account's credit, with optional budgets per account and per workspace. See Models and credit.

Working with agents ​

  • Agents on your own cloud. Connect an AWS account and add agents with the Create-Agent wizard. See Agents and Create an agent.
  • Workspaces. Path, git projects, AGENTS.md, .mcp.json, skills and the tracker link in one place, with a setup guide and configuration that reaches agents on its own. See Workspaces.
  • Tasks and playbooks. Bring tickets in from Jira, Linear or Notion, or create internal tasks, approve them, and let playbooks carry each one through its role steps and gates. Every account starts with the Bug Fix, Feature Implementation and Hotfix playbooks. See Working with tasks and Playbooks.
  • Priority decides what starts first. Kadmo reads each ticket's priority from Jira, Linear and Notion and starts the higher-priority tasks first. See Working with tasks.

Asking and automating ​

  • Ask Kadmo, in preview. Ask questions about your account and hand work to agents through a plan you start, with ⌘K on every page; an admin turns it on under Experimental features. See Ask Kadmo.
  • Workflows and automations. Workflows with validation and version history, and automations that start them from tracker and git events. See Workflows and Automations.
  • Integrations. Jira, Linear, Notion, GitHub, GitLab, Bitbucket, Slack and Microsoft Teams. See Integrations.
  • MCP. Use your account from Claude, Cursor, VS Code or Codex through app.kadmo.ai/mcp. See MCP overview.
  • Skill packs and chat agents. Your account's skill pack in git, and chat agents you embed on your own site. See Skill packs and Embed a chat agent.

© Kadmo GmbHImprintPrivacy