gifgrepSearch + local sheets
READYNative-first · Android
OpenClaw
in your pocket.
A living AI companion with a local mobile Gateway, useful skills, voice, and the freedom to choose local or cloud intelligence.
Google Play launch in preparation · Follow the public release train
01Native-firstAndroid owns the primary runtime
02Official GatewayFresh upstream release at setup
03Modular installsVerified packs with receipts
04Human approvedReview before wallet signing
The product, not a mockup
Touch the control surface.
Switch the preview to see how Plawie exposes intelligence, capability, health, and payment boundaries instead of hiding them.
PlawieOPENROUTER · NATIVE HUB
Give me a focused start to the day.
I can check your calendar, weather, and task inbox.
PROPOSED TOOL PLAN3 read-only steps ready
AGENT CAPABILITIESSkills that explain themselves.
12 READYstocksMarket snapshots
READYblogwatcherOptional native pack
DOWNLOADDependency receipt savedVerified · no repeat download
NATIVE MOBILE GATEWAY Healthy
OWNERAndroid
ENDPOINT127.0.0.1
PATHNative
LIVE ACTIVITY · PREVIEW
- ✓ gateway health confirmed
- → paired Android node
- ✓ capability snapshot ready
- ↻ waiting for your message
PRoot remains an explicit rollback option—not the primary runtime.
BASE
PLAWIE WALLET · DEMO$38.42USDC available
SOLExternal wallet
USDCBase · internal
HUMAN APPROVAL REQUIREDModel credit top-up · $5.00
Nothing signs or sends automatically.
LIVE PRODUCT PREVIEWFour surfaces.
One operating rhythm.
One operating rhythm.
Use the controls here or tap the navigation inside the phone. Each state is a faithful, non-connected illustration of the Android experience.
Interactive product illustration. It is not connected to your device, account, or wallet.
Local control · connected intelligence
A mobile nervous system
you can actually inspect.
The app keeps runtime ownership and model transport separate. That makes local control possible without pretending every model lives on your phone.
Chat, setup, permissions, status, and approvals.
LOCAL
Lifecycle, pairing, health, and tool routing.
ALLOWLISTED
Visible readiness, configuration, and dependencies.
Native first means native first. PRoot is preserved only as an explicit user-demand rollback path—not the default architecture.
How setup worksOne companion · real capabilities
Less “AI magic.”
More useful machinery.
VOICE
Talk like it lives there.
Voice input, model-aware replies, on-device speech options, and a visual companion that makes interaction feel present.
SKILLS
Readiness you can see.
Know whether a skill is ready, needs configuration, or requires an optional native pack before you ask the agent to use it.
- gifgrep
- canvas
- stocks
- camera
- voice
- files
- memory
MODEL CHOICE
Local when it fits. Cloud when you choose.
Keep the Gateway and tools consistent while selecting the intelligence path that matches your device, task, privacy needs, and budget.
HUMAN APPROVALYour agent can propose.
Your agent can propose.
You authorize.
Wallet actions expose the amount, network, recipient, reason, and expiry before device-authenticated signing.
NO SILENT SPEND
OBSERVABILITY
See the heartbeat.
Gateway state, logs, setup progress, dependency receipts, and repair paths live in the app—not in a hidden server dashboard.
gateway.health node.paired skills.ready
Fresh install · built to resume
A lean APK.
A transparent setup.
Plawie keeps the fast-moving Gateway and optional runtimes modular. Setup verifies each component, shows progress, and records receipts so successful work is not downloaded twice.
Inspect public releases- STEP 01Official GatewayVERIFIED
Download the current upstream OpenClaw release with visible progress.
- STEP 02Native runtime checkHEALTHY
Pair Android, validate health, and keep rollback isolated.
- STEP 03Optional mobile runtimesRECEIPTED
Resolve only what the skill needs through the approved install channel.
- STEP 04Ready to talkCOMPLETE
Resume successful work instead of downloading it all again.
Powers · configured by you
Power should come
with a control surface.
Choose how Plawie thinks, how you meet it, what it can use, and exactly where consequential actions stop for you.
BYOKBring your own intelligence.
Connect a supported cloud provider with your own API key, or keep selected work private with an on-device model.
WALLET FUNDEDPay from your own wallet.
Use the secured Base wallet with Venice prepaid or BlockRun per request. Every spend still requires visible details and device authentication.
TWO INTERFACESCompanion or classic dashboard.
Talk through the animated companion chat, or open the OpenClaw Web Dashboard for the traditional browser control surface.
AGENCYGo hands-off—or stay in the loop.
Open available Gateway tools, paired Android commands, and configured app or service skills—or lock them down one by one. Unconfigured proactive model heartbeats stay off.
The pocket agent is waking up
Be there when
Plawie lands.
Google Play and Product Hunt launch preparation is underway. Follow the public release train today; the store button arrives only when the listing is real.
Straight answers
Before you install.
Is Plawie native or PRoot?
Native-first. Android owns the primary mobile Gateway lifecycle and device bridges. PRoot is preserved only as an explicit user-demand rollback path.
Does everything stay on my phone?
No blanket claim like that would be honest. The Gateway and app controls run locally, and local models can stay on-device. If you select a cloud provider, the data needed for that request is sent to that provider under its terms.
Why does first setup download components?
OpenClaw moves quickly. Plawie downloads the current official Gateway during fresh setup instead of bundling a stale copy, then resolves optional mobile runtimes through the install channel. Successful components leave receipts so setup can resume without wasting data.
Can I use a local model?
Yes, on supported Android hardware and for models that fit the device. You can also select supported cloud providers for larger or different workloads.
Will every desktop OpenClaw skill run on Android?
No. Mobile-compatible skills can run through native tools or verified Android dependency packs. The Skills page shows readiness, required configuration, and genuine platform blockers instead of pretending all desktop binaries are available.
Can Plawie spend from my wallet by itself?
No. Wallet actions are designed to stop at a visible approval containing the amount, network, recipient, reason, and expiry, followed by device authentication before signing.
When is the Google Play release?
The Play listing is being prepared alongside final release and policy acceptance. Until a real store URL exists, GitHub Releases remains the public sideload channel. The Play build will use Play-approved delivery for executable modules.