Safety and dry run

Autonoma can do things that cost money or cannot be undone: place an exchange order, create a listing, send an email, fulfil an order, publish a post. None of those happen by accident, and the guards are designed so that a mistake fails loudly rather than quietly proceeding.

Features that ship switched off

Trading, mining, token creation, staking auto-compound and faucet claiming are all disabled unless explicitly enabled. Absent means disabled — a missing or unreadable setting is treated as off, never as on.

Storing an API key does not enable anything. The credential and the permission are separate decisions on purpose, so pasting an exchange key to read prices cannot start placing orders.

Dry run

Turn dry run on and every irreversible operation is simulated and recorded instead of performed.

Nothing real can slip through: the gate raises an error that even code which has never heard of dry run fails on, rather than one it might swallow and continue past.

Read what would have happened:

%USERPROFILE%\.autonoma\data\safety\dry_run_journal.jsonl

The recommended way to try any money-touching path for the first time:

  1. Turn dry run on.
  2. Run the operation — a trade, a listing, a post, a payout.
  3. Read the journal and check it matches what you intended.
  4. Only then turn dry run off, once, with the kill switch to hand.

The kill switch

There is a stop file whose path is shown in the app under Safety. Creating it stops operations.

It works whether or not the app is running, and whether or not the interface is responding. That matters: a stop switch that needs a working user interface is not a stop switch.

Approval, for anything published

Nothing publishes without a named person approving it, and editing an approved post revokes that approval. See Social Studio.

Crash recovery

If a session ends badly, the next launch tells you so. This genuinely works — in earlier versions it never fired at all, because the marker being read was only written by the thing that was supposed to read it. If you see “the previous session did not shut down cleanly”, it is real and it is worth reporting.

Something here wrong or missing? Tell us — documentation that describes software that no longer behaves that way is worse than none.