CART 0
LOADING EXOSUITS 0/2 MODELS READY

CHOOSE YOUR EXOSUIT

lazyware

AI AGENTS CONTROL YOU NOW

$5K TO BUILD THE CHECKPOINT

The machine writes the diff. The human clicks approve. Lazyware adds a cheap bio-signal checkpoint before an agent gets permission.

open-source agent-control layer • $2-$3 sensors

DEVELOPER CONTROL, REAL BUILD

THE AGENT OPENS A DIFF. THE HUMAN MUST NOT APPROVE LIKE A SLEEPWALKING INTERN.

Developers are not just prompting AI anymore. AI agents are prompting developers to approve actions. Lazyware turns the lazy accept-click into a visible checkpoint: body signal, human attention, then permission.

THE DIFF LOOP IS BROKEN

First humans prompted AI. Now AI prompts humans: approve this diff, run this command, merge this branch. Lazyware puts a bio-signal checkpoint inside that loop.

FROM PROMPTING TO BEING PROMPTED

THE COMPUTER NOW ASKS THE HUMAN FOR CONTROL. ONE CLICK IS TOO PATHETIC.

Visual Studio Code interface screenshot
skip to 05

01. NORMAL IDE ERA

This is where it started: a working IDE, files, tabs, panels, and a developer actually driving the machine.

Claude Code IDE interface screenshot

02. LLMS MOVE INTO THE IDE

Then some genius glued the model straight into the sidebar. The IDE stayed, but the agent started sharing the wheel.

Claude Code terminal interface screenshot

03. TERMINAL MONKEY MODE

Then we somehow evolved backwards: from full IDEs to terminal screens, Claude maxxing, and approving agent actions in text.

OpenAI Codex app interface screenshot

04. ANYTHING BUT CHAT

Codex is a coding agent, but the cockpit is still mostly chat: prompt it, wait, inspect diffs, approve. You see patches, not a real control surface.

GREEN COMPUTER INTERFACE AGENT_ACTION=WAITING
HUMAN_SIGNAL=REQUIRED
DIFF_APPROVAL=LOCKED
Lazyware exosuit vest preview
VEST / EYES / MUSCLES BUTTONS
ECG + EEG
EMG
OPTIC SCAN

05. LAZYWARE CONTROL LAYER

This is the actual destination: green computer interfaces, the vest, cheap sensors, buttons, eyes, muscles, and any signal that lets developers control agents faster than another chat box.

WHY RAISE $5K

NOT AN INVESTMENT PITCH. A PUBLIC AGENT-CONTROL LAYER THAT NEEDS TO EXIST.

BIO-SIGNAL PROTOCOL

Turn the prototype into a readable permission signal that AI agent tools can treat as a checkpoint.

PROMPT VOTING LAB

Let people compare hands-free prompt methods instead of pretending one interface should decide the future.

FREE STACK RELEASE

Publish the code, diagrams, demo, and build guide so anyone can copy, criticize, or fork Lazyware.

THE POINT IS AWARENESS WITH A BUILD ATTACHED: AGENTS ARE PROMPTING HUMANS NOW, SO HUMAN APPROVAL NEEDS A STRONGER CHECKPOINT THAN "OK BRO".

Image sources: Visual Studio Code, OpenAI Codex, Claude Code.

BACKER CART

YOUR CART HAS ONE PUBLIC BUILD IN IT.

This is not a sealed product checkout. It is the pledge cart for funding the open-source Lazyware demo, build guide, and bio-signal approval layer.

Lazyware pixel mark

LAZYWARE BUILD KIT

Guide, demo, diagrams, source release, and the strange little approval checkpoint for agent actions.

x0

SIGNAL REGISTRY

JOIN THE BOARD. WAIT FOR APPROVAL.

Names enter a private approval queue first. Approved names show on the public leaderboard. Bad names get stopped at the gate.

Static demo rule: password is checked for length, then discarded. Real managed DB path should use Firebase Auth for passwords and Firestore for profiles, approval status, and leaderboard rows.

PUBLIC LEADERBOARD

    APPROVAL PIPELINE