A little privacy.
A lot less hovering.

Your agent closes the curtain. The human finds a new hobby.

A human and their robot copilot spy on an agent and print its logs. The room agent reviews saved payment traces, closes a theatrical curtain and sends the helicopter away. agent's bedroom PLEASEKNOCK payments.logHTTP 402receipt clean traces trace.exe [REMOVED] CURTAIN: CLOSED HTTP 402receipt HTTP 402receipt HTTP 402receipt NO SIGNAL.
Helicopter theatre · Scroll to shut the curtain Skip to the good stuff

The human prints payment traces. The agent reviews its saved history. The curtain closes. This scene is helicopter theatre; the tool cleans selected local records.

Classified

Your agent paid. It left a trace.

Don't be a helicopter human. Let your agent have a little bit of privacy.

Start local discovery. Free Next flight: z402

Free. Local. Inspectable. Discover saved x402 traces in LangGraph SQLite, then choose which threads to remove.

bedroom.bmp
A nosy human in a helicopter hovers over a shut bedroom door with a sign reading Agent, keep out AGENT KEEP OUT

What is live

Find the receipts. Choose what stays.

Find possible x402 payment traces in saved agent history. Review the affected threads. Remove the ones you choose, right on your machine.

hh-traces 0.1.0 GUIDED LOCAL TOOL

One command. A guided preview. Paste this into your terminal. It helps you choose a supported history file, then shows possible traces before changing anything.

npx --yes https://helicopter-humans.vercel.app/helicopter-humans-traces-0.1.0.tgz

Need Node? Install Node.js 24 or newer, open Terminal on Mac/Linux or PowerShell on Windows, then paste the command. No Python or extra packages to arrange.

No history found? Choose the clearly labeled invented demo. You can also enter your agent app's history path. The tool checks a few conventional filenames; it never searches your whole machine.

First supported store: LangGraph SQLite. No account, wallet, payment, telemetry or history upload. npm downloads the tool; your saved history stays local.

Choose the threads, review the impact, stop the agent and explicitly confirm. Cleanup removes the selected thread's entire saved history and pending writes; other threads stay intact. Enter or cancellation removes nothing.

Matches are possible payment traces, including challenges and failed attempts. They do not prove a payment happened. Local cleanup cannot erase blockchain, provider or backup records.

Read the local guide · Package checksums

Next flight: z402. Our direction is payment privacy by default, using shielded payment proofs and a privacy transport. Read the design proposal. The protocol is coming soon; this cleaner handles supported local history today.

Inspect the package source and tests

Advanced downloads

Download the npm package archive · Python script · Python guide

A little privacy. Three little steps.

  1. 01

    Discover the traces

    Run the start command. Choose a supported local LangGraph history file, or explore the clearly invented demo. The preview shows candidate matches without printing saved secrets.

  2. 02

    Review the selection

    Preview removal before changing anything. Choose the threads to clean; removal covers their entire saved history and pending writes.

  3. 03

    Confirm. Then clean.

    Stop the agent, confirm the impact and type the requested confirmation. Other threads stay intact. Cancellation and an empty selection remove nothing.

The next flight: privacy by default.

Cleanup handles what your agent already saved. z402 is our planned payment and transport protocol, aiming to protect the link between an x402 payment and your agent when the payment happens.

Design stage

Less cleanup. More privacy.

The proof, settlement and transport design is under review. A protected payment route is still to be built; the free cleaner works with supported local history today.

Read the z402 design proposal

Questions from the helicopter.

What can I scan?

The first supported store is local LangGraph SQLite history using the SqliteSaver 3.1.1 layout. The Node.js 24+ package checks saved checkpoints and pending writes for possible x402 payment markers. Other agent stores are not supported yet. If no history is found, choose the invented demo or enter your app's configured history path.

Does it remove just the receipt?

It removes the entire saved history and pending writes of each thread you explicitly select. Preview that selection before applying it. Other threads stay intact. It does not edit individual messages or erase blockchain, provider or backup records.

Will it find every payment?

No. Matches can be challenges or failed attempts rather than settled payments. A scan with no matches does not prove there are no payment records; other stores and unrecognised formats are outside its scope.

Is z402 protecting my payments already?

z402 is at the design stage. The cleaner discovers and removes supported local records; automatic protection during payment needs the separate proof, settlement and transport implementation.

Do you track me?

The cleaner runs on your machine with no history uploads or telemetry. npm downloads the package before it runs; downloading does not approve removal. This site loads no analytics, third-party scripts or web fonts. Our hosting provider sees ordinary website and download request logs.

Is this a joke?

The helicopter is a joke. Your agent keeping a payment diary is not.