Troubleshooting

“Not configured”

This is not an error. Autonoma ships with no credentials, so any provider you have not set up reports itself as unconfigured rather than guessing or silently doing nothing.

Open Settings → API keys, find the provider, add your key. See API keys.

A key I saved does not seem to be used

Check the settings screen: it marks whether each value is coming from what you typed or from your environment. What you typed takes precedence, so if a field shows as arriving from the environment, nothing was stored for it.

If you keep a .env file, it still works — it is the fallback, not the winner.

A post will not publish

Work through these in order:

  1. Is it approved? Nothing publishes without an explicit approval recorded against a named person. A draft stays a draft.
  2. Was it edited after approval? Editing revokes approval, deliberately. Approve it again.
  3. Does its account still exist? A post addressed to a disconnected account refuses rather than failing quietly at send time. Reconnect it, or point the post at another account.
  4. Is the account paused? Paused accounts are not offered in the composer and do not publish.

A platform is missing from the list

Platforms with no working publish path are listed with the reason rather than hidden. TikTok, Threads and YouTube currently store credentials but cannot publish.

If what you need is not there, a custom webhook account will reach anything that accepts a POST — Slack, Teams, Zapier, Make, n8n, or your own endpoint.

Accented characters render as boxes

Autonoma needs a real TrueType font to draw accented text. If it cannot find one it says so rather than rendering empty boxes. Installing a standard font set resolves it.

“The previous session did not shut down cleanly”

Exactly what it says, and it is trustworthy — crash reporting genuinely works now, where in earlier versions it never fired at all. The logs are under %USERPROFILE%\.autonoma\logs\. Please send them.

Nothing is happening and no error appears

Check whether dry run is on. It simulates irreversible operations and journals them instead of performing them, which is correct behaviour that can look like nothing happening. The journal is at %USERPROFILE%\.autonoma\data\safety\dry_run_journal.jsonl.

Also check the stop file described under safety — if it exists, operations are intentionally halted.

Updates are not installing

If the status says no update source is configured, none has been set; that is honest rather than broken.

If it says the signature does not match, the download was altered or corrupted and was correctly discarded. Try again; if it persists, tell us, because that is worth investigating.

Still stuck

Get in touch with what you did, what happened, and what you expected. A log from %USERPROFILE%\.autonoma\logs\ turns a long exchange into a short one.

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