After KiloClaw: what you can still recover and where to move your agent
KiloClaw's end date, 20 October 2026, has passed. Where your agent's files may still be, what to revoke, how to rebuild it, and where to move it.
Kilo told KiloClaw subscribers that the service would end on 20 October 2026: the agent would stop answering in chat, its scheduled jobs would stop, and its workspace would be deleted. If you need anything from the instance itself, ask Kilo’s support now; only Kilo could get it back. If you saved nothing in time, look in three places: a private GitHub repository (Kilo’s setup guide had the agent push its workspace there every hour), the Google Drive the agent wrote to, and your chat history with the bot, which Telegram lets you export. Revoke every key the agent held and remove Kilo’s access to your Google account. Then set up OpenClaw on a new home and rebuild from what you found.
What Kilo said about 20 October
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. The end date comes from Kilo’s email to subscribers, which an owner posted on Reddit: “KiloClaw is being retired on October 20, 2026.” 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 published nothing about the retirement since, and has promised to keep nothing. The dashboard’s export is no way back either: it only worked while the instance was running. If there is something you need from the instance itself, write to Kilo’s support at support@kilo.ai straight away; only Kilo could restore anything.
Where your agent may still be
- A private GitHub repository. Kilo’s setup guide had owners send the agent: “Use your GitHub access to back up your workspace. Make it a GitHub repo and push it as a private repo. Add me as a member so I can see it. Then set up a cron job to pull, rebase, and push any changes at least once an hour.” If you did, that repository holds what the agent pushed as its workspace, as of its last push, most likely including who it was, what it knew about you, and its memory and notes. The same guide recommended a separate GitHub account for the agent, so look there too.
- The agent’s Google Drive. Kilo’s help also suggested asking the agent to “Tar compress your workspace and push the file to Google Drive”. If the agent had a Google account of its own, sign in to it and look, or download all of it with Google Takeout.
- Your chat history. Your Telegram bot was your own, so the whole conversation with it, both sides, is still in Telegram. In Telegram Desktop, open the chat, then the ⋯ menu, and choose Export chat history, as HTML or JSON. Discord’s data package holds only the messages you sent, and Slack’s Free and Pro plans export public channels only, so for those, what is still on screen is what there is. Kilo Chat, KiloClaw’s own channel, went with the instance.
- Anything you downloaded. The dashboard export (your workspace’s Markdown files and a list of the skills it had installed), or a backup the agent made for you.
Revoke what it held
Every key you gave KiloClaw was last on a machine you can no longer reach, so revoke each at its source and make a new one for the new home: a model provider key with the provider, a GitHub token in GitHub’s settings, and each chat bot’s token. For Telegram, send BotFather /revoke for your bot now; it gives you a new code at once, for the new agent when it is ready; for Discord and Slack, reset the bot token in their developer settings.
Then check your Google account, whether or not you pressed Disconnect in KiloClaw: on its linked apps page, choose Access to your Google Account, select Kilo’s entry, then See details and Remove access. If you set the agent up with a Google account of its own, its access lives in that account, so remove it there too, and undo any forwarding, delegation or calendar sharing you gave it from your own account.
Rebuilding it
KiloClaw ran ordinary OpenClaw (2026.7.1 in its last image), so what you recovered goes into any current OpenClaw. A full OpenClaw backup restores whole, and OpenClaw moves the data to its own format on first start; moving OpenClaw to a new computer covers the restore step by step, and OpenClaw’s update guide has a backup from before July 2026 restored into 2026.9.5 first and updated from there. With the workspace files alone, from GitHub or the dashboard export, start a fresh OpenClaw, put the Markdown files into its workspace, and reinstall the skills.
With nothing but the chat history, the agent starts fresh, but the history is most of what it knew about you. OpenClaw keeps what it knows in files in its workspace, so attach the export and ask the new agent to write down what it should remember.
Set up again in any case: your chat connections (with the new bot tokens), your Google and other accounts, a model (unless you brought your own key, KiloClaw supplied it through Kilo’s), and your scheduled jobs. A kiloclaw.ai email address went with the service.
Where to move it
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. 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.
Bringing your agent to Everpod
On Everpod’s OpenClaw pod, your agent moves itself in from one .zip you attach in its chat: the file you asked it to pack before the move, or the Markdown files and skills you saved (from the dashboard export or the GitHub copy) put into one .zip. On your pod’s page in Everpod, tap Open the OpenClaw control panel. In the chat, tap + beside the message box, choose File and pick the .zip, then send:
I've moved you here from KiloClaw. The attached file is what I saved of you there: your workspace, and your skills and a list of your scheduled jobs if it has them. Move back in: put your identity, personality, what you know about me and your memory where they belong on this computer, install your skills, and set your scheduled jobs up again. Keep this computer's own setup and files as they are. When you're done, tell me what came across and anything you couldn't bring.CopiedA few minutes later your agent is back with what the file held, and lists what it brought. Then connect Telegram: tap Telegram on your pod’s page and paste the new code BotFather gave you. When your agent answers you there, send it “From now on, send your scheduled messages to me here.”
Klaus and American Claw, two other managed OpenClaw hosts, have also closed; what their owners can still do is in the moving guide.