July 2026

Adamko Builds A Branded Set Of Transactional Emails

Describe what your product does and he picks the transactional emails that suit it, then builds each one in your colors, your fonts and your logo.

He starts from our premade bases and restyles them rather than generating markup from nothing. That was a deliberate call. Email clients are genuinely hostile and the premades have already been through them; asking a language model to invent nested table markup that survives Outlook is a bet we did not want to place. The theming that follows is deterministic rather than model-driven, and one design family is chosen per team and then held, so your transactional emails and your campaign drafts do not drift apart.

The copy comes back in your website's language rather than in English, subject lines included. Czech site, Czech emails. The brand kit had been detecting the site language all along and nothing was consuming it. For a European company that was never really optional, and out of everything here it is the piece we are happiest to have got to. A translation that fails keeps the English original rather than handing you half a translated email.

Generation runs in the background, because it cannot do anything else: the whole chain takes minutes and a request is killed long before that. The first version showed three bouncing dots and no sign of whether the job was still alive. It always was, but nobody watching could have told you that, which is why there is now a progress bar and a rough countdown that stops short of claiming it has finished.

The Emails list shows the same thing happening. The emails you picked appear immediately as real rows with a Finalizing badge and an animated placeholder, rather than materialising one at a time. A row that is still being worked on cannot be opened, because editing it would race the job still writing to it.

A Brand Kit Read From Your Website

Give Adamko a URL and he reads the site for its colors, fonts and logo.

That was much harder than it sounds. An early attempt collected every color on the page and concluded that a company's palette was mostly the grey of a disabled control plus whatever blue the browser paints behind selected text. It was extremely confident about this. Interaction states are now weighted down rather than trusted at face value — though not removed outright, because deleting them cost dark-themed sites their actual accent color.

Several other things had to be taught. A site declaring a color by name matched nothing at all, so extraction fell through to guessing by frequency. A framework's own palette, compiled into the site's stylesheet, would outvote the brand — on one site two stock theme colors tied exactly, and which one won was decided by nothing more than the order they happened to be listed in. A single decorative gradient could beat a color used fourteen times.

Fonts had their own problem. A site builder ships its entire font catalogue whether or not the page uses any of it, and a stylesheet lists fallbacks besides, so reading the CSS tells you what a site would like to render in rather than what a visitor has actually seen. Ranking now prefers the families that are both declared and genuinely loaded.

Logos are often not images at all. Many sites draw their mark as inline vector artwork, so there is nothing to download; that artwork is now found through the link that points back at the homepage and turned into a proper standalone file. Looking for the word “logo” instead finds things like search-logo and close-logo.

Everything Adamko Creates Can Be Undone

Every template, campaign, brand kit, domain, API key and property he touches lands in an activity view, and anything he made can be reversed from that one place.

We wrote the undo before we wrote most of the generation, because nobody should hand an assistant write access to their account without a cheap way back out. It shipped nineteen days before the work it protects.

Each entry carries the prompt that caused it, and a bulk operation is one row with a count rather than five you have to piece together. What is safe to undo is decided on our side, per type: a campaign has to still be an untouched draft, a template untouched including its versions, a sending domain not yet verified — because verifying it means you adopted it — and an API key still present. When something cannot be undone you get the reason rather than a failure, and the log entry survives either way.

Adamko Reads Your Account, And Advises On What He Finds

A set of read-only tools closed the “I cannot see that” dead ends, and a set of advisory ones turn what he reads into an answer.

He can now look at your plan and quota, templates, API keys, webhooks with their last success and failure, team members and pending invitations, per-message delivery events, API request logs, a contact and its history, import history, and the real suppression list including whether one specific recipient is on it. API keys come back as metadata only; the key itself is never serialised.

On top of that: ask why a particular address did not get your email and you get one classified cause — suppressed, complained, hard bounced, blocked by the provider, delayed, rejected at send, still in flight, or delivered — with the evidence and what to do, rather than three tool calls you have to chain yourself. He will review a template for broken merge tags, a missing unsubscribe link, images with no alt text, fixed widths that break on phones, a body large enough for Gmail to clip it, and subject lines that will read as spam. He will compare recent campaigns, recommend a list or segment for a stated goal while explaining the reach-against-engagement tradeoff, and sketch a lifecycle or campaign plan that fits inside the sending quota you actually have left.

Rates come back as unknown rather than as a confident 0% when there is nothing to divide by, and he is explicitly forbidden from claiming he scheduled something, because no tool of his can.

Adamko Helps You Import A CSV

Drop a file on the chat and it goes straight to the import flow as an attachment — the model never receives it.

On the mapping step, unmapped columns offer a review that names what is actually wrong with your file: no email column, invalid addresses, duplicates inside the file, contacts you already have, no consent signal, statuses it does not recognise — quoting the real values it found. Asking him to map them opens a confirmation explaining which custom fields will be created and with what type, which existing ones get reused, and how your status column will be read. Every field he creates is recorded with an undo.

Secrets And Personal Data Are Stripped Before Any AI Request

Redaction moved to the wire, so it covers every AI feature in the product rather than each one separately.

Keys, bearer tokens, private keys and long secret-shaped strings are masked irreversibly, in system prompts, your messages, the assistant's history and tool results alike. Recipient details inside email HTML are replaced with stable placeholders that are put back in the response, so an “edit this HTML” round trip does not come back full of tokens.

Details in ordinary conversation are deliberately left alone — asking why delivery to a named address bounced cannot work if the address is removed on the way — and that transfer is covered in the data processing agreement. Two older editor AI endpoints that predate Adamko were brought under the same access model, throttle and spend cap at the same time.

Daily DNS Health Checks On Every Domain

Verified domains are re-checked once a day, and you are told when one stops resolving or stops pointing at us.

A domain that verified months ago and quietly broke since used to go unnoticed until a send failed. The check is strictly read-only and never writes a status back, so monitoring cannot disable a live domain. A control lookup runs first, because every failed lookup otherwise reads as “the record is gone” and one sick resolver would page every customer at once.

Broken records show in the app as well as arriving by email — on the dashboard, and as a badge on the domain, email and campaign lists saying which records are failing and for how long. A team with several broken domains gets one digest rather than one email per domain.