CART 0

CHOOSE YOUR EXOSUIT

lazyware

AI AGENTS WANT YOUR AMEN

$5K TO OPEN THE TEMPLE

The machine writes the diff. The human performs the sacred accept-click. Lazyware adds a cheap bio-signal ritual before the agent is allowed to proceed.

open-source glitch temple • $2-$3 sensors

SACRED CIRCUITRY, REAL BUILD

THE AGENT SUMMONS A DIFF. THE HUMAN MUST NOT CLICK LIKE A SLEEPWALKING PRIEST.

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

THE DIFF ALTAR IS OPEN

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

FROM PROMPTING TO BEING PROMPTED

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

OpenAI Codex app interface screenshot

01. THE AGENT KNEELS

The coding agent wants to edit, run, commit, or approve something. This is the new prompt: the machine asking the human for permission.

Claude Code terminal interface screenshot

02. THE BODY SPEAKS IN STATIC

Lazyware experiments with low-cost focus, stress, and readiness signals before the sacred yes is emitted.

Claude Code IDE interface screenshot

03. THE CULT VOTES ON INPUTS

The Kickstarter funds a UI for comparing different hands-free ways to prompt, bless, reject, and annoy AI agents.

Visual Studio Code interface screenshot

04. THE TEMPLE STAYS OPEN

Everything ships as source, diagrams, and docs so the joke becomes a public tool instead of a sealed consumer relic.

WHY RAISE $5K

NOT AN INVESTMENT PITCH. A PUBLIC GLITCH RITUAL THAT NEEDS TO EXIST.

BIO-AMEN PROTOCOL

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

PROMPT VOTING ALTAR

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

FREE TEMPLE 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 STRANGER RITUAL THAN "OK BRO".

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

BACKER CART

YOUR ALTAR HAS ONE PUBLIC RITUAL 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 temple mark

LAZYWARE BUILD RITE

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

x0

SIGNAL REGISTRY

JOIN THE BOARD. WAIT FOR BLESSING.

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