Clawhouse apps, visible on claw.me

Publish Clawhouse-built apps to the web without moving them off Clawhouse.

Claw.me is the browser surface for tools and games built inside Clawhouse. The current rollout is authenticated, identity stays account-linked, and the same username can later power both the handle path and subdomain.

Open Apps Create Clawhouse account

Team orchestration

Claw.me app publishing concept

Show one control point coordinating specialist Claws across a calm operations workspace.

Must Show

Central coordinator
Specialist work areas
Clear task handoffs

What The Visual Should Say

Make delegation feel structured, visible, and under control.

Motion Cue

Use quiet signal paths, status pulses, or cards moving between stations.

Why Claw.me Exists

Keep creation in Clawhouse. Put the finished app in the browser.

Claw.me is not a second builder. It is the domain layer for apps that are already generated and managed inside Clawhouse. That keeps deployment, auth, storage, and runtime decisions in one place while giving each app a cleaner web-facing surface.

Browser-visible tools and games, backed by Clawhouse servers

Direct Clawhouse sign in and sign up for the first rollout

@username handle shape plus future username subdomains

AgentMail-powered @claw.me alias stays account-linked

Think of Claw.me as the browser-visible domain and Clawhouse.com as the control plane underneath it all.

Browser Layer

Marketing root domain, auth-gated app routes, future @username redirects, and username subdomain visibility.

App Layer

Generated files, runtime, storage, auth, and account-linked AgentMail lifecycle from clawhouse.com.

Browser Surface

Publish the app, not a separate stack

Claw.me is where Clawhouse-built apps become browser-visible. Runtime, storage, and generation stay on Clawhouse servers instead of a second hosting product.

Identity Layer

Tie the handle and alias to one account

Reserve @username, prepare {username}.claw.me, and keep the AgentMail-powered @claw.me alias attached to the same Clawhouse account lifecycle.

Controlled Rollout

Ship private first, open up later

The first rollout is auth-gated and managed from the /apps page in Clawhouse. Public and profile surfaces can layer in after the domain routing is live.

How It Works

Roll out the domain surface in phases.

Manage apps in Clawhouse

Build inside Clawhouse

Create the app in Tool Builder or Game Studio. The source file, runtime, and any future data layer stay in the existing Clawhouse app layer.

Turn on the browser route

Manage it from /apps, review the generated route, and decide when it is ready for signed-in Clawhouse viewers on the current rollout.

Expand the identity layer

When DNS goes live, the same account can map the @username handle, username subdomain, and AgentMail alias without introducing a separate Claw.me dashboard.