# KilatBot guide

Source: https://kilat.host/docs/kilat-agent

KilatBot is your private AI agent. You give it a job and change anything later.

New agents run as **Flash**: they sleep when idle and wake when you need them. Flex is no longer offered for new agents. Existing Flex agents keep running and renewing. This page says where a limit differs for them.

## Chat

Open your agent's **Chat**. Replies stream in and show the tools it uses. You can steer it, queue a follow-up or stop it mid-reply. Review what it produces before you act on it.

It starts on Kilat AI, with usage included in each plan every month. To use another model, add your own provider key in **Settings**; your provider bills that usage.

## Pictures and files

Attach, drop or paste up to 10 at a time: pictures, PDFs, Office files, text, code, audio, video and zip files.

- **Size.** Up to 20 MB a file.
- **Telegram.** Send them to your bot. Telegram lets bots download up to 20 MB.

## Voice notes

Record in the chat or send one to your bot. In the chat you see the words before you send them.

- **Where.** Flash agents, and existing Flex agents.
- **Limit.** 5 minutes a note.
- **Cost.** They count toward your Kilat AI usage limits. A note that can't be turned into words still goes as a file.

## Approvals

Before a risky command runs, you see it and choose **Allow**, **Allow for this chat** or **Deny**. Nothing runs until you answer. Low-risk commands run without asking.

- **Purchases.** Your agent can't buy anything itself. It asks, and you select **Buy**.
- **Shared pages.** Making one public takes your tap.
- **Websites.** Publishing needs the Publish websites tool. Only the Coder template starts with it on, and it is told to ask you first. The tool itself doesn't stop to ask, so turn it off under **Tools** if you don't want it.
- **Schedules.** A scheduled task has nobody there to answer, so a risky command in it is blocked.

## Schedules

Ask in chat, or add one under **Scheduled tasks**: `every 2h`, `every day at 07:00`, `every monday at 9am` or a cron expression. You can run, pause, resume or delete each one.

- **Limit.** At most every 5 minutes.
- **Templates.** A template's schedules start paused. Resume the ones you want.
- **Sleep.** A sleeping agent wakes when a task is due.

For ideas and checks, read [how to schedule agent tasks](https://kilat.host/articles/schedule-ai-agent-tasks).

## Memory

Your agent keeps notes across chats. See them under **Memory**, or turn off **Remember things across chats** in **Settings**. Its memory and files survive sleep and restarts. Storage is not a backup, so keep your own copy of anything you can't lose. To decide what it should remember, read [agent memory for your business](https://kilat.host/articles/ai-agent-memory-for-business-context).

## Reading the web

With the Browse the web tools on, your KilatBot reads a page it has the address for with `web_fetch`. It's quick and uses no browser minutes. It reads web pages, text, JSON, XML and PDFs (the first 50 pages, not scans or password-locked files) up to 2 MiB, and only on the public internet. Pages that need JavaScript are read on a best-effort basis.

Your agent treats what it reads as information, never as instructions.

## Live browser

Your KilatBot opens a real browser when a page needs a sign-in or clicks, and to find pages, for example on a search site.

### Watch and take control

- In the KilatBot dashboard chat, the browser appears beside the conversation while your agent uses it. Select **Expand** or **Full screen** for a bigger view.
- Select **Take control** at any time. Your agent pauses while you drive. Select **Give back** when you are done; your agent checks the page again and carries on.
- Your agent asks for you when it needs you, for example a sign-in, a captcha or a payment. The panel shows what it asks.
- While you have control, you can paste text from your clipboard into the browser. Allow clipboard access, or press Ctrl+V (⌘V on Mac) in the browser view.
- Select **Stop browser** to close it yourself.

### Sign-ins and payments

Type sign-ins and payments in the browser, never in chat. Your agent never sees your password.

By default your agent signs in again each time. To skip that, turn on **Saved browser sign-ins** in the agent's **Settings**, or choose **Remember** when the browser panel offers it after you sign in. Saved sign-ins belong to that agent only and are never shown in chat. Turn the setting off to stop saving, or select **Forget** to delete what is saved.

### Telegram

On Telegram your agent browses in the background and replies with the result. If a task needs a sign-in, it asks you to open the chat in the KilatBot dashboard, because you take control there.

### Privacy and where it runs

- The browser runs in an isolated cloud sandbox in Singapore, Southeast Asia. Each session is wiped when it ends.
- Nothing is recorded: no video, no screenshots kept, no browsing history.
- Saved sign-ins are stored per agent. They are deleted with the agent, or when you select **Forget**.
- Only the owner of the agent can watch or take control.

### Limits

- The browser closes itself when it is idle.
- If something keeps failing, your agent stops and asks you instead of trying forever.
- Some sites block automated browsers or ask for a captcha. When that happens, take control and finish the step yourself.

## Telegram

1. Create a bot with BotFather and keep its token private.
2. Open your agent's **Channels** and save the token.
3. When someone new messages your bot, it replies with a pairing code. Approve them in **Channels**, or list numeric Telegram user IDs under **Allowed Telegram users**.

Only people you approve can talk to it. Send a test message and confirm you get a useful reply before relying on it.

## Templates

A template sets the persona, skill and schedules. You can change all of them later, or start blank. Templates run on Flash agents.

- **Social Media Planner.** Weekly content plans and caption drafts; you post.
- **Operations Reporter.** Daily reports from your CSV files; no guessed numbers.
- **General Assistant.** Meeting notes, weekly reviews, drafts and plans.
- **Coder.** Builds and publishes sites, runs scripts in a sandbox.

### Coder

Coder comes with C/C++, Go, Rust, Ruby, Node, Bun, PHP and Python, database clients and `mise` for other languages. It needs Medium (2 GB) or larger. There is no Docker.

It can test what it builds in a real browser:

- **Headless Chromium.** `chrome-headless` is installed, for a rendered page or a screenshot.
- **Puppeteer.** Install it in the project with `npm i -D puppeteer`. Its plain `launch()` works.
- **Playwright.** Install it the same way and launch with `chromium.launch({executablePath: process.env.CHROME_BIN})`. `npx playwright install` isn't needed.

## Publish a website

With the Publish websites tool on, your agent can build a static website and publish it on goki.lat through KilatBot MCP. Setup, limits and upload steps are in [Websites your agent publishes](https://kilat.host/docs/websites-and-backends#static-sites) and [MCP static tools](https://kilat.host/docs/mcp#static-sites).

**Everything in published assets is public.** Never ship `.env`, tokens, provider keys, PocketBase superuser credentials or private keys.

## Keys and safety

Agents can run tools and code you ask them to. Choose what an agent normally does under **Tools**. Use a separate model key for each agent with a spending limit, keep unrelated production credentials out of the agent, and rotate keys after deleting it.

Every agent can read and change records, schemas and access rules in any PocketBase backends already in your workspace. Revoke its token under **Account → MCP** to stop further calls; data it already read can't be recalled.
