Studio

Studio is an interactive editing view where you chat with the Kamu assistant and see the changes immediately in a live preview. It is the fastest way to make targeted updates — fix a sentence, swap a color, add a section — without a long wait.

Studio differs from the regular Chat view: you get a real-time preview and you publish the changes yourself when you are satisfied.

Starting a session

You'll find Studio in the site sidebar under Updates → Studio. You can also reach it from the overview page's Make changes section by selecting the Studio tab.

Press Start session, and Kamu spins up a temporary editing environment and loads the latest version of your site into it. The start page also shows your past Studio usage: this month's sessions, the duration and cost of previous sessions, and what was published in them.

Once the session is ready (usually in about a minute), you'll see two panels:

• Kamu panel: the chat with Kamu. Type what you want to change, and Kamu edits the site directly.
• Preview: updates automatically after each change. You can navigate between pages in the preview just like real visitors.

On a computer the panels sit side by side. On mobile the preview fills the screen and the Kamu panel is a bottom drawer you can open and close as needed.

Studio needs Kamu Balance

Studio usage is charged from your Kamu Balance. If the balance is empty, a session cannot be started — top up first from the Billing page. Your remaining balance is always visible in Studio's toolbar.

Continuing unfinished work

If a previous session ended before you published (for example due to automatic shutdown), your changes are not lost: they are saved automatically. The next time you open Studio, you get a choice:

• Continue where you left off: restores the saved changes into the workspace so you can pick up where you stopped.
• Start fresh: discards the saved changes and starts from the published version.

The same save happens when you press End while there are unpublished changes in the workspace.

Preview tools

Above the preview there is a toolbar:

• Pick an element to edit turns on the picker mode: click the spot in the preview you want to change and write your request right there. Kamu then knows exactly which part of the page you mean. This saves both time and Kamu Balance.
• Mobile / Tablet / Desktop buttons switch the preview width so you can see how the page looks on different devices.
• Mobile + desktop side by side shows the same page as two previews next to each other — handy when you want to make sure a change works on both at once.
• Copy address to share copies the preview address so you can send it to a colleague to look at.
• Open in a new tab opens the preview in its own tab.

Images, files, and voice

• Files: drag images or other files into the Kamu panel, paste them from the clipboard, or use the panel's attachment button (maximum 20 MB per file).
• Voice: with the microphone button you can dictate your request out loud. Kamu transcribes the speech and starts working right away — especially handy on a phone.
• Queueing: if you type a new message while Kamu is still working, the message is sent automatically as soon as the previous turn finishes.

Publishing

When you are happy with the changes, press Publish. In the publish dialog:

1. Give a short description of the changes (Kamu suggests one for you).
2. Build always runs before publishing, so a broken site can never go live. From the same dialog you can also run the accessibility and link checks — the option is on by default.
3. Press Publish or — if a check found problems — Publish anyway.

After publishing, the changes appear on the public site in about 30 seconds. You can then continue editing in the same session or end the session.

If automatic publishing is turned off

Then Studio publishes the changes only to the preview address {site}.kskamu.app. They are pushed to your own domain separately with the Publish to domain button in site settings. Read more: Publishing

Ending a session

A Studio session is temporary — it consumes Kamu Balance in the background until you end it.

• Continue editing: you can make more changes in the same session after publishing.
• End: shuts down the editing environment. Unpublished changes are automatically saved for next time.

Automatic shutdown

If a session is idle for more than 15 minutes, Kotisivukamu shuts it down automatically. You get a warning at around 13 minutes, at which point you can continue the session with one click. Automatic shutdown makes sure a session does not consume Kamu Balance unnecessarily.

Costs and tokens

Studio is charged from your Kamu Balance based on how many tokens Kamu uses during the session. A token is the AI's billing unit — roughly four characters of text. Every request you make, Kamu's replies, the files it reads, and the changes it makes all consume tokens.

If your Kamu Balance runs out mid-session, Kamu can no longer respond. In that case, publish the changes you have made right away so no work is lost, top up your balance on the Billing page, and refresh the Studio page.

The biggest factor in token consumption is conversation length: the more messages a session has, the more previous context Kamu has to read on every turn. In a long session the cost of an individual change grows considerably, even if the change itself is small.

Tips for saving tokens

• Start a new conversation after a big change. When you have finished one piece of work, press the Start a new conversation button (circular arrow at the bottom of the chat panel). Kamu forgets the earlier messages, but the session and preview stay up — you save both the tokens and the session startup time. This is the most effective way to keep costs down.
• Group similar changes into one session. If you are editing all the texts on the front page, for example, do them back to back in the same session. Kamu reuses the files it has read on later turns (caching), so the cost per change stays small.
• If you have several changes to the same page, try to put them all in one message. One long request ("change the hero heading to X, make the CTA button bigger, add a third service card, and fix the footer phone number") is clearly cheaper than four separate messages — Kamu reads the page once and makes all the changes in one turn.
• Avoid switching topics mid-session. If you jump from editing the front page to the blog and then the navigation, Kamu has to read different files every time. One session per topic is better.
• Write clear, sufficiently detailed requests. A vague request ("improve the front page") often leads to back-and-forth and several attempts. A precise request ("increase the font size of the front page main heading and change the CTA button background to dark blue") is often done in one turn. The Pick an element to edit tool achieves the same with a click.
• Upload images in one go. If you want Kamu to replace several images, drag them all into the panel and say where they should go. One turn with eight images is clearly cheaper than eight turns with one image.
• Watch your Kamu Balance. The remaining balance is shown in the toolbar. If a single turn costs surprisingly much, it is usually a sign that the session has grown too long — publish and start a new conversation.

The Start a new conversation button

At the bottom of the chat panel there is a Start a new conversation button marked with a circular arrow. It clears Kamu's memory without shutting down the session — the site changes and the preview stay as they are, but Kamu starts the next turn from a clean slate. One click saves what a long conversation history would otherwise cost.

If you also want to shut down the session entirely (e.g. for a lunch break), use the End button.

Example requests

• "Make the front page heading bigger and change the background to a darker blue"
• "Add a new item to the services list: Roof renovation, from 5000 €"
• "Fix the phone number on the contact page: 040 123 4567"
• "Swap the front page hero image for a lighter one and add text on top of the image"
• "Make the navigation more compact on mobile"

Difference to the Chat and WhatsApp assistants

Feature	Studio	Chat	WhatsApp
Real-time preview	Yes	No	No
Publishing under your control	Yes	No (automatic)	No (automatic)
Available on mobile	Yes	Yes	Yes
Pre-publish checks (accessibility, links)	Yes	No	No
Best for	Quick targeted edits	Bigger changes, blog	On the go