The Share buttonfor the tools you build.
Luo runs the internal tools — and agents — you build in Claude Code: hosting, sign-in, permissions, integrations, schedules. Sharing them with your team is a link.
Internal tools are easy now. Sharing them isn't.
Claude Code will build you a supplier tracker from a paragraph of description. Then someone asks to use it, and the real work starts: picking a host, wiring OAuth, inventing a permissions model, standing up a deploy pipeline — for a tool with four users. The building is the easy part now; the productionizing is a whole second discipline. That's where most internal tools die — not because they weren't good, but because they were single-player.
What ship it actually does.
The stack you'd otherwise glue together — hosting, an auth provider, a database, an OAuth app per integration, a cron service — is one MCP server.
- hosting
- Your tool at a URL. TLS, zero config, no dashboard safari.
- accounts
- Your team signs in. You never write auth again.
- permissions
- Roles and sharing like a doc, not an IAM console.
- integrations
- Gmail, Slack, Airtable, Notion — scoped, consented connections. Not your .env file.
- agents
- Not just tools — deploy the agents you build too. Schedules, triggers, background work; alive while your laptop sleeps.
- iterate
- Change the spec in your terminal; the running tool updates. No redeploy ritual.
Not a snapshot. A running thing.
A deploy is a snapshot — you push a build and walk away. A Luo workspace stays alive. Agents keep working inside it: filing the quotes, chasing the inbox, posting the summaries to Slack. The agents you prototype in Claude Code ship the same way the tools do — spec one, and it runs in the workspace with the same connections and permissions. And your teammates don't view what you built — they work in it, next to the agents. The thing you prompted into existence in a window only you could see becomes something your whole team lives in.
How it works
claude mcp add luo
Or point Codex at the MCP server. One config line either way.
Build like you already do
Your terminal, your agent, your specs. Luo is not another place to build — it is where the result runs.
Say "ship it"
Luo creates the workspace: a URL, accounts for your team, scoped connections to the tools it needs — and any agents you specced start running.
Send the link
That is the rollout.
Frequently asked questions
Does Luo replace my dev workflow?
No. You build where you already build — Claude Code, your editor, your terminal. Luo is where the result runs: hosting, sign-in, permissions, integrations, and the agents that keep it working.
Claude Code only?
Anything that speaks MCP. Claude Code and Codex are first in line.
Can I run agents on it, not just tools?
Yes — agents are first-class. Spec one in your terminal and it runs in your workspace: on a schedule, on a trigger, or in the background, with the same scoped connections and permissions as your tools. Your team sees what it did and can steer it in plain language.
My team does not use a terminal.
They do not need one. They get a link, sign in, and use the tool. And Luo builds tools without a terminal too — that is the rest of this site.
What does the runtime actually include?
Hosting at a URL, sign-in and role-based permissions for your team, scoped OAuth connections to tools like Gmail, Slack, Airtable, and Notion, and agents for scheduled and background work. The stack you would otherwise glue together, as one runtime.
When can I use it?
Early access is rolling out from the waitlist, in order. Get in line.