Troubleshooting

The switch is on but nothing changed

These tools read their config once, at startup. Restart the app or the terminal window — a session that was already running keeps its old settings.

"Config does not point at Asale"

Something else rewrote the tool's config after Asale did — often the tool itself on upgrade, or a second config manager. Asale re-applies it automatically; if it says it could not, sign in again and re-apply from the Buy page.

Stuck on "coming online"

The client cannot complete its handshake with the gateway. Check that you are signed in under Account, and that the machine has a working outbound connection. It retries with backoff on its own.

Codex ignores the model I picked

Codex chooses from its own built-in model list, not from the request. Select a model on the Buy page so it is written into ~/.codex/config.toml, then restart Codex — the model also has to appear in the app's menu.

503 "no supply"

Nobody currently has capacity for that model. Try another model, or wait — supply is re-declared every minute as sellers' windows roll over.

If you are a seller seeing your own lane look empty, check your reputation. A run of failures can push it under the matching threshold and take the device out of the market until it recovers.

402 insufficient balance

The pre-authorisation could not be frozen. It reserves your declared max_tokens at the output price, which is usually much larger than what the request will actually cost — a small balance can fail on a request it could easily have afforded. Top up.

429

Your per-account rate limit. The response carries a retry delay.

An account shows as "expired"

The stored credential could not be refreshed. Reconnect that account from Sell before it can serve again.

Selling stopped part-way through the day

Either the daily cap was reached — it resets at UTC midnight — or the plan's rolling window is exhausted and will recover as it rolls over. Usage shows which.

Signature errors after a server update

Sign out and sign in again. A token issued under a previous signing key cannot be validated; a fresh sign-in fixes it.

Nothing here matches

Open an issue on the client repository with what you did, what you expected and what happened. Do not paste credentials or request bodies.