KiloClaw is shutting down: how to save your agent and where to move it

What is happening, and when

KiloClaw was Kilo’s hosted OpenClaw. Kilo was acquired by Anaconda in July 2026, stopped taking new KiloClaw subscriptions in August, and has since removed KiloClaw’s product page and documentation; both now send you to Kilo’s homepage. The retirement date comes from Kilo’s email to subscribers, which an owner posted on Reddit: “KiloClaw is being retired on October 20, 2026. As a paying subscriber, you have 60 days to save anything you want to keep. We’ve already stopped all upcoming charges.” After that date, in Kilo’s words, the agent “will no longer be reachable via chat, cron jobs will cease to function, and its workspace will be deleted.” Kilo has not said why it is closing KiloClaw.

Your instance keeps running until then, so everything below is done while it still is.

Save your agent: the dashboard export

In the KiloClaw dashboard, open Settings and find Import & Export. The OpenClaw Export card downloads your workspace text: the agent’s profile, instructions and memory files, plus a list of the skills it had installed so you can reinstall them. The instance has to be running. If the card says export is not available yet, the instance needs updating to a version that has it.

That export is deliberately narrow. By Kilo’s own description it does not include credentials, channels, conversations, configuration or secrets, and it takes only Markdown files, so skill files, images and anything else the agent made are left out. One more file to watch: TOOLS.md carries instructions written for KiloClaw that will not apply on a new host.

Save more: ask your agent for a full backup

KiloClaw never offered SSH, but the agent itself can run commands, and that is how Kilo’s own help told owners to move: ask the agent to package its workspace and push it somewhere you control. OpenClaw’s own backup command goes further than the workspace, taking the configuration, scheduled jobs, credentials and past conversations. On the OpenClaw version KiloClaw runs, it skips the conversation in progress, so a plain archive of the agent’s files goes with it. Send your agent something like:

Make a full OpenClaw backup with "openclaw backup create --verify".
Then make a plain .tar.gz of ~/.openclaw and another of your working
directory. Upload all three to a private place I can download them
from (my Google Drive, or a new private GitHub repository), and tell
me the file names and where they are.

Kilo’s help suggested Google Drive through the agent’s Google tools, or a private GitHub repository through the gh tool; use whichever your agent can write to. The backup contains every key the agent holds, so it goes only to a private place, and you delete it from there once you have restored. If the agent cannot upload anywhere, the dashboard export above is what you can still take.

While the agent can still answer, ask it two more things and save the replies: a list of its scheduled jobs with what each does and when, and a list of every account and service it is connected to. Those are what you will set up again.

What does not move

• Chat connections. Telegram, Discord and Slack bots on KiloClaw were ones you created, so they are yours to keep. For Telegram, when the new agent is ready, send BotFather /revoke for your bot and give the new token to the new agent: the old copy loses its connection, and only the new one answers. Kilo Chat was KiloClaw’s own channel and ends with it.
• Google and other accounts. Connected accounts end with the service, and Google connections made on the web since June used Kilo’s own sign-in app. Connect each account again from the new home; Kilo’s own advice was to plan on reconnecting integrations rather than moving them.
• The model. Unless you brought your own key, KiloClaw supplied the AI model through Kilo’s. Your new home needs its own: a provider key, a subscription sign-in, or a host that includes model usage.
• The agent’s email address. A kiloclaw.ai address goes with the service.

Where to move it

KiloClaw ran ordinary OpenClaw (2026.7.1 in its last image), so a full backup restores into current OpenClaw, which moves the data to its own format on first start. If your instance was pinned to a release from before July 2026, OpenClaw’s update guide has older installs restored into 2026.9.5 first and updated from there. Moving OpenClaw to a new computer covers the restore step by step. If you only have the dashboard export, start a fresh OpenClaw, put the Markdown files into its workspace, and reinstall the skills on the list.

Where the new home should be depends on how much of the computer you want to run. A Mac you own or a VPS puts the updates, backups and security on you. A managed host takes those off your hands; managed OpenClaw hosting compared sets the field side by side with prices and terms. Two things worth checking, given why you are moving: that the host is a company you expect to still be there, and whether it documents taking in an existing agent from an OpenClaw backup. Hosted OpenClaw at Everpod is a private, always-on computer of your agent’s own, one customer per machine, at $29 a month with model usage included up to a cap, updates applied after testing and a backup every day.

Klaus and American Claw, two other managed OpenClaw hosts, have also closed; what their owners can still do is in the moving guide.