Appearance
You run the shop, the salon or the newsroom. Your developer built the site on kitloom. This page is what you can now ask instead of opening the admin: each case is a real request, the tools the agent calls, what is left for you to check, and what the same work takes by hand.
The agent is Claude, ChatGPT, Cursor or any other MCP client, connected to the site as a user you approved, with the role you gave it.
"Give 20% off everything in Winter until Monday night with the code WINTER20, and put a banner for it on the home page."
products_list — the Winter productscoupon_save — percent, 20, those products, expires Tuesdayads_create , ad_zones_update — the banner into the home page's zoneLeft to you: the coupon applies once it is published — the agent leaves it a draft unless you said otherwise; a look at the banner on the home page.
By hand: the coupon screen, each product picked from a list, the banner uploaded, the zone found and filled — a dozen screens and clicks.
"Our number is now 204-555-0187. Change it everywhere on the site."
search_replace_dry_run — every page, post and field that has the old number, with each change before and aftersearch_replace_run — exactly the change it countedtheme_customize — the footer line, if the theme keeps it thereLeft to you: a look at the count before anything changes; each record keeps the version it had.
By hand: searching the admin page by page, then the footer, the widgets and the forms' texts — and the one page nobody remembered.
"Which addresses gave 404 this week? Send each to its new page."
not_found_list — the 404 log, with how often each was hitresolve_url — what lives at the likely new addressredirect_from_404 — one 301 rule for each matchLeft to you: the addresses it could not match, listed for you.
By hand: reading the log, opening each address, guessing where it went, writing a rule for each.
"How did last week go? What is waiting on us, and is anything broken?"
sales_report , top_products — revenue, orders and the best sellers against the week beforeorders_list — the orders on hold or waiting for paymenthealth_report — the site's checks and any failed background jobsLeft to you: reading the answer. Nothing is changed.
By hand: three reports in the admin and the Site Health screen, put side by side.
"We close at 2 pm on December 24. Cancel the bookings after that and tell the clients why."
bookings_close — no free times from 14:00bookings_list — the bookings already made in that timebookings_decide — each cancelled with the reason; the client is emailedLeft to you: who you would rather call than email.
By hand: blocking the time, finding each booking, cancelling it, writing to each client.
"Write SEO descriptions for the products that have none, in our tone."
products_list — the catalogueseo_get — which products have no descriptionseo_update — a description for each, under 160 charactersLeft to you: a look over the list; each change is a revision you can bring back.
By hand: opening each product, writing, saving — one by one.
"Mrs. Jensen called: two Hearth Blend 1 kg and a grinder, delivery to her saved address. Send her the invoice."
customers_list — finds herorder_create — at today's catalogue prices, waiting for payment; nothing is chargedinvoices_create — the invoice, sent with the orderLeft to you: taking the payment. Refunds stay in the admin.
By hand: the new order screen, the customer found, each line added, shipping chosen, the order saved, the invoice made.
Every request above runs through the same code as the admin, with the rights of the user who approved the agent. It cannot do what that user may not do, it deletes nothing for good — records go to the trash, products start as drafts, bookings end declined — and the settings that decide who gets in and what leaves the site are locked, whatever a comment or a form message tells it. The activity log shows every change under the agent's name, and revoking it stops it at once. How it is kept safe →