LoopOS

LoopOS is the agent that replaces the back office across five short-term rentals in Japan, Taiwan, Philippines, and Bali. It triages tickets, retrieves the right context from a four-layer Company Brain, drafts the dispatch, and routes it to the right vendor at the right cost cap.

Built initially at AWS Builder Loft “Build YC’s Next Unicorn — Agent Hack Day” (top 6 finalist), it became the ongoing system I use to actually run my STR operations.

The architecture: a multiplayer MCP-native AI Chat App on Reboot. Every team member’s AI client — Claude Desktop, ChatGPT, Goose, any MCP client — plugs into the same durable backend and shares state. Tickets are first-class entities. Skills are an executable, version-controlled JSON map; agents run against it. Not search. Not RAG.

It answers two of the 2026 YC Requests for Startups:

• Alströmer · “Sell the service, not the software.” STR ops back-office spend dwarfs software spend. Replace the back office with an agent; take the margin.
• Blomfield · “Tribal knowledge in heads, email, Slack, tickets.” Build a living, executable map. Four layers, one JSON, the agent runs against it.