Studio

Studio is an editing view where you chat with Kamu and see the changes immediately in a preview. It is for quick targeted edits, such as fixing a text, changing a colour or adding a new section, without a long wait. You can also make small text changes yourself, directly in the preview.

Studio differs from the Chat view in that you see every change in the preview right away and publish the changes yourself when you're happy with them.

Opening Studio

You'll find Studio in the site sidebar under Updates → Studio. You can also get there from the overview's Make changes section: select the Studio tab and press Open Studio.

Studio opens straight into the latest version of your site, and there is nothing to start separately. If the site is being built at the moment, Studio opens once the build is done.

The view has two parts:

• Kamu panel: your conversation with Kamu. Write what you want to change, and Kamu makes the changes to the site. The New conversation button at the top of the panel starts the conversation over.
• Preview: updates after every change. You can navigate the preview from page to page just like real visitors.

On a desktop the two are side by side. On mobile the preview fills the screen, and the conversation opens from the Kamu button in the bottom right corner.

The top bar shows the site's name and address, the version you are editing, your Kamusaldo and the model Kamu uses. The arrow in the top left corner takes you back to the dashboard. The question mark in the top right corner opens a short guide to using Studio.

Studio needs Kamusaldo

Studio usage is charged from your Kamusaldo. If the balance is empty, Studio cannot be opened. Top up first on the Billing page. You can see the remaining balance and what the session has cost so far in Studio's top bar.

Unfinished work from the previous Studio

Studio has been renewed. If you left changes unpublished in the previous Studio, they are not lost. The first time you open the site in the new Studio, the unfinished changes are included as unpublished work, and a notice at the top says You continued from the unfinished changes in the previous editor. They go on the site when you publish. It's worth checking the changes in the preview before publishing. If you don't want to publish them, you can discard them, see Discarding a draft.

Preview tools

Above the preview there's a toolbar:

• Edit / View switches the mode. In View mode the preview works as it does in a visitor's browser. In Edit mode you can click a text in the preview and type the new text in its place without Kamu. Enter starts a new line. The change goes onto the page when you click elsewhere or press Ctrl+Enter (Cmd+Enter on a Mac). Esc restores the original text. If a text cannot be changed directly, Studio tells you, and you can ask Kamu to make the change.
• The 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. These buttons are shown on desktop only.
• In the address field you can type a page address, for example /contact. The house icon takes you back to the front page.
• Pick what to edit turns on pointer 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 Kamusaldo. Esc ends pointer mode.
• Discard, Save and Publish, see below.

Files, speech and the queue

• Files: drag images or other files into the Kamu panel, paste an image from the clipboard, or use the panel's attach button. A single file can be at most 10 MB and the attachments of one message at most 25 MB in total. Attachments are saved to the version you are editing. Kamu reads the contents of an image or PDF only if you switch on the eye icon on the attachment. Reading uses tokens, so switch it on only when Kamu needs to see the contents.
• Speech: with the microphone button you can dictate your request. The speech is turned into text in the input field, and you send it yourself. Handy especially on a phone.
• Queue: while Kamu is still working, the Send button reads Queue. A queued message is sent automatically once the previous request is done. You can edit a queued message with the pencil button or remove it with the cross.
• Stop interrupts Kamu in the middle of a request. If a request is stopped or fails, the queue waits and you see Queue paused. Resume sends the queued messages, Clear removes them.

Saving and publishing

Changes made in Studio don't show on your site until you publish them.

• Save: Kamu usually saves its own changes when the requested change is done. Text changes you made yourself are saved with the Save button. The number on the button tells how many files are unsaved. Saving takes one click, and Studio writes a short description of the change into the version's history. Save is not available while Kamu is working.
• Discard: throws away unsaved changes. Changes already saved are kept. To discard the whole draft, use the version menu, see Discarding a draft.
• Publish: takes the version's saved changes to the site. Unsaved changes have to be saved first. The site is usually updated in about 30 seconds. The publish is recorded in the site's history under the version's name.

If the site was changed elsewhere at the same time, for example through the chat or the Texts page, and the changes could not be merged automatically, Studio shows an error and lists the affected files. Ask Kamu to reconcile the changes and publish again.

You don't need to stop or close Studio separately. Unpublished changes are kept in the version, and you can continue from them later.

If automatic publishing is off

In that case Studio publishes changes only to the preview address {site}.kskamu.app. They're taken to your own domain separately with the Publish button on the overview page. Read more: Publishing

Versions

The Version picker in the top bar shows which version of the site you are editing. A new version gets its name from your first request to Kamu, for example Summer menu and opening hours. Until then it has a dated name in the site's language, such as Muutokset 10.11. If you make the changes yourself without writing to Kamu, the name comes from the first save. Publish always takes the selected version to the site.

Next to the picker is a three-dot menu:

• New version makes a new version from the selected one, for example when you want to try a bigger change separately. You can type a name or leave it empty. Each version has its own conversation with Kamu.
• Rename changes the version's name. A name you give yourself stays.
• Discard draft and start over, see below.

Discarding a draft

The Discard button only throws away unsaved changes. To give up the whole draft, saved changes included, choose Discard draft and start over in the version menu. Studio first tells you how many saved changes in the draft are not published yet. When you confirm, you get a new version that starts from what is on the site now, and the conversation with Kamu starts over. The option is not available while Kamu is working.

A discarded draft is not lost. It is listed in the version picker under Discarded drafts. When you open it, you can bring it back with Restore draft and continue where you left off. A discarded draft can't be edited before it is restored.

Costs and tokens

Studio is charged from your Kamusaldo according to how many tokens Kamu uses. Opening Studio and using the preview cost nothing. A token is the AI billing unit, roughly four characters of Finnish text. Every request you make, Kamu's response, the files it reads and the changes it makes all consume tokens. Turning dictation into text is charged too.

If your Kamusaldo runs out mid-way, Kamu cannot continue until you top up. The changes already made are kept, and you can save and publish them. Once you have topped up on the Billing page, reload the Studio page and continue where you left off.

Token usage is driven most by conversation length: the more messages there are in a conversation, the more of the earlier context Kamu has to read on every turn. In a long conversation the price of a single change grows considerably, even if the change itself is small.

Tips for saving tokens

• Start a new conversation after a big change. Press New conversation at the top of the Kamu panel. Your site changes are kept, unsaved ones too. If Kamu is still working or there are messages in the queue, Studio asks first, because a new conversation stops Kamu and clears the queue.
• Group similar changes into one conversation. If you're editing all the texts on the front page, for example, do them one after another in the same conversation. Kamu reuses files it has already read on later turns (caching), so the cost per change stays low.
• 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 phone number in the footer") is clearly cheaper than four separate messages. Kamu reads the page once and makes all the changes in a single turn.
• Avoid switching topics mid-conversation. If you jump from editing the front page to the blog and then to the navigation, Kamu has to read different files each time. Better one conversation per topic.
• Write clear, sufficiently detailed requests. A vague request ("improve the front page") often leads to back-and-forth and several attempts. A precise request ("make the front page's main heading font larger and change the CTA button's background to dark blue") is often done in one turn. The Pick what to edit tool achieves the same by clicking.
• Fix small texts yourself. A single word or number can be changed directly in the preview in Edit mode, without Kamu.
• Upload images in one go. If you want Kamu to replace several images, drag them all into the panel and say where they should appear. One turn with eight images is clearly cheaper than eight turns with one image each.
• Keep an eye on your Kamusaldo. The top bar shows the remaining balance and the session's cost. If a single turn costs surprisingly much, it's usually a sign that the conversation has grown too long. Then it's worth publishing and starting a new conversation.

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
How a change starts	Kamu makes the change at once, you publish	You approve the change description, Kamu updates the site	Kamu updates the site based on the conversation
Available on mobile	Yes	Yes	Yes
Charged for	Tokens used	The site update only	The site update only
Best for	Quick targeted edits, design	Bigger changes	On the go