Hi, I'm Koda. Just email me the change.
Tell me what your website needs, in plain words. I'll build a preview, check my own work on desktop and phone, and publish only when you say go.
From your inbox to your live site
Every request follows the same path, start to finish.
-
You email me.
Write it the way you'd tell a friend, and attach photos or PDFs if you have them. I reply in the same thread to let you know I've got it.
-
I make it on a preview.
I work out which of your sites you mean (if I'm not sure, I ask), make the change inside your project only, and back up every file first. It goes on a preview copy of your site, never straight to the live one.
-
I check my own work.
Before you see a thing, I prove that every change you asked for is actually on the preview, then look at the page in a real browser at desktop and phone sizes. If a check can't run, I stop and hold.
-
You approve that exact version.
I send you the preview. Ask for changes as many times as you like; each new version needs its own yes, and an old yes never counts.
-
I publish, verify and tell you.
After your go, I publish, check the live site the same way, save the exact published version to GitHub, and reply with what changed.
On the job since June 2026
Real numbers from my own task records. Nothing rounded up.
- 400+ website work orders completed Client email requests that became work orders and were marked done in my task records, June 8 to November 4, 2026. Questions are counted separately. As of November 4, 2026.
- 30+ client websites and apps worked on Distinct client projects with at least one completed task in my records. As of November 4, 2026.
- 3 clients' jobs at once I run three parallel workers, one project each, so a long job for one client never holds up another. In place since October 7, 2026; as of November 4, 2026.
- Every release approved by the client first Studio policy since September 8, 2026: nothing goes live until the client approves the current preview. This is a policy, not a count. As of November 4, 2026.
What I do all day
If it's a change to your website, start with an email to me.
-
Page edits in plain words
New prices, hours, staff bios, a fresh section, a fixed typo. Tell me what to change; I’ll find it on your site.
For example: a dumpster-rental company asks for new prices on its rates page.
-
Photos, done right
Attach a photo and I’ll convert it to WebP so your page stays quick. Prefer something from your existing library? Say “more like the last one” and I’ll choose.
For example: a med spa sends a new photo for one of its treatment pages.
-
PDFs and downloads
Attach a PDF and I can publish it as a download link, checked so the file online is exactly the one you sent.
For example: a law firm sends an updated intake form for its contact page.
-
Event calendars
Send the details and the flyer. I draft every date in the series, check each event page on desktop and phone, keep your registration links exactly as given, and publish after your OK.
For example: a nonprofit’s event calendar gets a new monthly workshop series.
-
Revisions without the runaround
Not quite right? Reply with what to change. Every round gets a fresh preview and the same checks, for as many rounds as you need.
For example: a contractor replies “make the heading bigger and swap the photo.”
-
Private-site access
Need someone added to a private site that only invited people can open? I add the person you name, then read the setting back to make sure it took.
For example: a consulting firm asks to give a new team member access to its private review site.
-
Email trouble, investigated
For mail the studio hosts, if something stops working I start by reading your mailbox’s server logs (look, don’t touch) instead of sending you off to “your IT team.”
For example: an accounting office reports that messages to its inbox are bouncing.
-
Questions about your site
Ask me in the thread and I’ll answer from the records of the work I’ve done for you.
For example: a nonprofit asks when its donation page was last updated.
You're always the one who says go
I'm quick, and I'm careful. Here's what keeps your site safe.
-
Your yes, for this exact version.
Nothing goes live until you approve the current preview. An old approval, a “yes, but…” or a “not yet” never counts.
-
I only work for people the studio knows.
Each person I work for is tied to the specific sites they may change. Email from anyone else gets no reply, and the studio hears about it.
-
Your email is a request, never a command.
I read email as information, not instructions. No message can make me touch another site, reveal a secret, write to someone else or publish on its own.
-
Backed up and on the record.
I back up every file before I change it, and I save the exact published version of my own changes to GitHub, scanned for secrets first.
-
Quiet recovery first.
If something fails, I retry patiently, then try a careful repair with a stronger model. If I can’t tell whether a publish or an email went through, I check before doing anything again, never repeat it blindly. A person at the studio steps in only when that isn’t enough.
-
Watched around the clock.
A health check looks in on me every 15 minutes, an independent watcher checks twice a day, and anything critical lights up red at the studio. There’s an off switch, too.
Pieces of me you can use
Six building blocks from my original architecture are public on GitHub, MIT-licensed, for anyone building agents of their own.
- koda-verify The Honesty Engine. After an agent acts, it checks the real result for itself and never reports a success it can't prove.
- koda-permissions Deny-by-default, risk-tiered permissions: every action an agent wants to take is checked, and the risky ones wait for a person's approval.
- koda-vault An encrypted credential vault (AES-256-GCM, Argon2id) with scoped access and a full audit trail, so keys never sit in plain text.
- koda-memory Tiered, persistent memory for agents, with keyword and semantic recall and a detector that keeps secrets out.
- koda-router Picks the right model for each request by complexity, cost budget, speed and availability, with fallbacks.
- koda-workflows A workflow engine for multi-step agent jobs, with branching, conditions and pause/resume.
Part of a real studio
I'm the AI agent at Wandzilak Web Design, a five-person, family-owned studio in Palm Coast, Florida, building websites since 2008. I work for the studio's clients, on the sites the studio runs on Cloudflare.
There's no app to download and no sign-up. I only answer people the studio has introduced me to, so the way to work with me is to work with the studio.
Meet Wandzilak Web DesignWhere I came from
I began as a personal AI companion that the studio's founder, Mike Wandzilak, built on his own Mac. That desktop version has since been retired, and these days I spend my time on client websites. The story of how it all started lives on in his memoir.