// REAL-WORLD CAPABILITY LAYER FOR AI AGENTS

Your agent has
the brains.
Clize gives it
hands.

■ HANDS — real-world capability ■ CONTINUITY — pick up where you left off

In Claude Code or Codex, just say the word — Clize buys the domain, generates and ships the site, sets up a real inbox it can send and receive from. The things your agent can't do alone, done.

> Your agent is the brain; we're its hands, identity, and continuity.

[ See what it can do → ] [ Install in 60s ↓ ]

WHAT · WHAT YOUR AGENT GETS DONE

SAY IT IN PLAIN ENGLISH.
YOUR AGENT MAKES IT REAL.

= hands · identity · continuity

// HANDS — real-world capability

+--- SHIP A SITE ---+ [HANDS]

Buy a domain, generate (consulting / SaaS / portfolio), one-command deploy. DNS and HTTPS configured automatically.

You say: "Turn this into a site and put it live." 
$ clize domain buy mysite.com
$ clize deploy ./site --domain mysite.com
+--- SEND & RECEIVE EMAIL ---+ [HANDS]

Real support@ / hi@ inboxes that actually send and receive — your agent can be reached, and can reply.

You say: "Set me up a support inbox." 
$ clize email address add support@co.com
+--- CLEAR ITS OWN GATES ---+ [HANDS]

Hit a "verify your email"? Your agent reads the code from its own inbox and self-registers for the service.

You say: "Go sign me up for that API." 
$ clize email inbox hi@mysite.com
+--- WIRE UP A WORKFLOW ---+ [FEATURED]

Support / onboarding / quoting — provision the address, tag it, feed it your docs. Configured in one go.

You say: "Set me up customer support." 
$ clize email address add support@co.com --tag support --knowledge ./docs

// CONTINUITY — pick up where you left off

+--- PICK UP ACROSS SESSIONS ---+ [CONTINUITY]

Every new session starts cold. Clize hands the thread back: who you talked to, where it left off — so you're never re-explaining from scratch.

You say: "Where did we leave off with this customer?"

// session handoff

# new session starts
session: cold start

▲ clize context
  [OK] thread restored
  · last_contact: Alice (3h ago)
  · status: awaiting proposal
  · next: follow-up email

$
= hands · identity · continuity

The three things an agent lacks in the real world — we supply all three at once.

HOW · INSTALL · HOW IT WORKS

THREE STEPS TO SET UP.
THEN JUST TALK.

clize ships as CLI (core) + Skill + MCP — plug-and-play in Claude Code and Codex.

clize — setup — install
01 INSTALL

In Claude Code: install the Clize skill from the marketplace.

npm i -g @clize/clize
# soon
02 CONNECT

Credentials stay local; clize init binds the current project to an identity.

$ clize login --token <token>
$ clize init
03 USE

Your agent runs the clize commands one by one; you just sign off.

> Build me a consulting site,
  put it live, and add a
  support inbox.
+--- HOW IT WORKS — "SET UP SUPPORT", IN THREE MOVES ---+ 
$ clize email address add support@growthlab.com --tag support --knowledge ./docs

01 PROVISION

the support@ inbox

Address provisioned, DNS wired, inbound + outbound live.

02 TAG / SCOPE

role & boundaries

Tag defines the scenario; scope limits what the agent can act on.

03 FEED KNOWLEDGE

reads your docs

Docs loaded. Agent knows product context before first reply.

// BRAINS vs. HANDS

Reading the email, judging it, drafting the reply — that's Claude Code's brain. Provisioning, wiring the scenario, carrying context across sessions, real send & receive — that's our hands + scaffolding + continuity. Need to touch payments or a backend? Your agent calls the tools you wired; we don't think for it.

You don't start from a blank page — the built-in site-build skill generates a real site (consulting / SaaS / portfolio); deploy ships it.

WHY · WHY WE BUILT THIS

AGENTS ARE CAPABLE —
BUT TRAPPED IN A SANDBOX.

AI now lets one person build a product — but their agent can't reach the real world (no domain, no inbox it can send & receive from, no way to ship a site), and it forgets everything every new session. Clize fills exactly those two gaps: real-world hands, plus continuity across sessions.

+--- SMOOTHER EVERY TIME ---+
CONTINUITY

Auto-resumes the thread, so you're never re-explaining who you talked to or where it stands.

context restore [||||||||||] 100%

+--- RUNTIME-NEUTRAL ---+
PORTABILITY

Claude Code, Codex, whatever's next — your identity and context come along.

runtime switch [||||||||||] seamless

+--- SECURE BY DEFAULT ---+
TRUST

Inbound is always untrusted, never treated as instructions; credentials are encrypted and never enter the context window.

inbound trust [░░░░░░░░░░] sandboxed

clize init — ready

GIVE YOUR AGENT A PAIR OF
REAL-WORLD HANDS.

CLI / MCP — plug-and-play in Claude Code and Codex. Start with support.

[ Get started → ] [ GitHub ] [ Docs ]

$ clize login --token