Your coding tool handles code. Your KilatBot agents keep scheduled business work going while you are away. This guide connects Claude Code or Codex to KilatBot over MCP, then creates an agent, teaches it and gives it a schedule.
Why pair a coding tool with KilatBot?
A coding tool is good at the repository in front of you. A KilatBot agent is good at work that repeats: a weekly report, a daily summary, a drafted reply. Connecting the two means you can set up and check those agents from the tool you already have open.
The tool sets an agent up. It does not run the agent's work. The agent keeps its own memory and schedules, and you talk to it in chat on the web or on Telegram. See when you need an agent if you are not sure it fits.
How do you connect it?
You need a KilatBot account with a plan. Both tools connect to https://kilat.host/mcp and sign in with KilatBot.
Claude Code. Run this, then open /mcp and choose Authenticate:
claude mcp add --transport http kilat https://kilat.host/mcpCodex. Add the server URL to config.toml, then sign in:
[mcp_servers.kilat]
url = "https://kilat.host/mcp"codex mcp login kilatApprove the app on the KilatBot page that opens. It gets read access. Tick the box there only if it should also make changes. If you prefer a token, the client setup shows both tools with a token. Each tool also has its own guide: Claude Code and Codex.
Look first.
Start with questions that only read. They prove the connection works without changing anything:
- "List my KilatBot agents and tell me which are asleep."
- "Check my KilatBot plan: how many agents and credits do I have left?"
An empty list is a valid answer if you have no agents yet.
Create and teach an agent.
These steps change things, so the connection needs the box ticked for changes. Each one works only on your own workspace's agents.
create_agentmakes an agent, optionally from a template. It uses your plan's agent allowance, and a new agent costs nothing until it wakes.upload_agent_filegives it a file to work from. A file can be up to 10 MB, and an agent up to 200 MB in total.add_memory_noteadds a note of up to 2,000 characters. Use it to tell the agent when to read a file.update_agent_settingssets its persona and standing instructions.
A starting prompt:
Create a KilatBot agent called Toko Help and add a memory note with our opening hours. Show me what you changed.
Give it a schedule.
create_agent_schedule takes a name, a schedule such as every day 9am, and a prompt. The most often it can run is every 5 minutes. You can update or pause a schedule later.
A sleeping agent is not woken by a change. It gets the change the next time it wakes. wake_agent wakes it now, and that uses your plan's awake time. Read how to plan a scheduled task before you rely on one.
What can it not do?
- Pay for anything or delete an agent. Purchases are always yours to approve.
- Read logs, open a terminal or edit environment variables.
- Chat with an agent or hand it a task. Talk to your agent in its own chat.
Keep it safe.
Keep your tool's approval prompts on, and tell it to show you a change before it makes one. A token you create by hand lasts 30 days. To stop a connected tool, open Account → MCP and choose Disconnect. The MCP workflow guide has the working order and the tool reference lists every tool.
Start small.
Read next: How to create your own AI agent without code · How to schedule AI agent tasks throughout the day
Connect one tool, list your agents, then create one. Prices and the current way in are on the pricing page. If KilatBot fits that job: Get started.