Tenki is now Luxor Agent Cloud
New name, same tools, and all of Luxor making them better.
Guzman Pintos
Product at Luxor Agent Cloud
3 min read

Same Sandbox, Runners, and AI Code Reviewer. Same team. Starting today, Tenki is now Luxor Agent Cloud.
Why Luxor
Tenki's agentic cloud platform was always built at Luxor by Luxor's team. Everything still runs in full Linux VMs on servers Luxor owns. Now it carries the Luxor name.
Luxor is also putting more behind the platform: more hardware, a dedicated sales team, and the full 110-person Luxor team.
What doesn't change
Everything you run keeps working. Your workflows, sandboxes and reviews run exactly as they did yesterday.
Your account, workspace, data and billing. You don't need a new account. The dashboard moved to app.luxor.ai, and the move signs everyone out once. Sign in again with the same login.
Old links still work. Every page that was on tenki.cloud redirects to luxor.ai, so bookmarks and docs links land in the right place.
Your GitHub Apps stay installed. They're now called Luxor Runner and Luxor Code Review. You don't need to reinstall them.
The integrations you use keep working, from Cursor Origin and Scale AI's AgentEnv to TinyFish, Hotdata, Omnara, Naïve and Anchor Browser. Each one is being updated to the new name.
What changes
The name. The product is Luxor Agent Cloud. It's part of Luxor AI, one of Luxor's two divisions alongside Luxor Mining. Inside the platform you'll see "Luxor."
The address. luxor.ai for the site, app.luxor.ai for the dashboard, luxor.ai/docs for the docs and api.luxor.ai for the API.
The names in your setup. The old ones keep working while you switch:
- CLI:
tenki→luxor - Packages:
@tenkicloud/*→@luxorai/*on npm,tenki→luxor-aion PyPI, andgo.luxor.ai/sandboxfor Go - API keys:
tk_→lx_ - Environment variables:
TENKI_*→LUXORAI_* - Runner labels:
tenki-standard-*→luxor-ubuntu-*, andtenki-macos-*→luxor-macos-* - Code Reviewer mention:
@tenki-reviewer→@luxor-reviewer - Sandbox images:
tenki/<image>:stable→luxor/<image>:stable
What you need to do
Nothing today. Your tk_ keys, tenki-* runner labels, the tenki command and @tenki-reviewer all keep working.
Switch to the new names when you have a moment. The migration checklist walks through it in nine steps. Start with the SDKs and the CLI: lx_ keys need sandbox SDK 1.4.2 or later and CLI 2.10 or later.
Runner labels. tenki-* labels keep working alongside the new luxor-* ones, so you can switch one workflow at a time.
API keys. Create an lx_ key, replace the old one in your shell, CI and secret managers, check it with a request, then revoke the old key.
Two things only get updates under the new name. Images under tenki/ stay on the last build published there, and the old Go module path stays at 1.4.4. Move to luxor/<image>:stable and go.luxor.ai/sandbox to keep getting new releases.
Old names stop working on January 1, 2027. Switch before then.
Get started
The migration checklist lists every change and what to replace it with. If you have a question, write to hello@luxor.ai or reply to the email we sent you.
Thanks for building with us.



