Approve or reject

A proposal sits at pending until you answer it. This is the only step that can release an order, and it always carries the owner's own token, never something the model can produce.

From the desk#

The proposal arrives as a card in the conversation, after the steps Olai took to reach it. The action is the biggest type on the card, BUY ETHUSDT for $15.00 or HOLD, with the order type under it. Then How sure it is as a meter, Data it says it used (each merchant, what it cost, and its settlement hash linked to BscScan, under the plain note that the model writes this list and the receipt is the record), and What could go wrong, the risks the model named.

Below those sits the rulebook's own verdict: "The rulebook allows this" or "The rulebook refuses this", the biggest order the rules allow right now, and each reason lined up with the rule id that produced it.

Approve sends it; the button reads "Sending" while the call is in flight. Reject opens a one-line reason field, placeholder "One line: why not?", and a Record the rejection button. Both buttons disable the instant either is clicked, so a second click cannot send a second order. When Olai proposes holding there are no buttons and the card says "Olai recommends holding. Nothing to approve."

What follows lands under the heading "What happened next", in the same plain sentences the rest of the conversation uses:

You approved the buy of ETHUSDT
Olai sent the order to Binance
Binance filled 0.0059 ETHUSDT for $14.75

In a dry run the last two lines become "Dry run: the order was not sent". A fill that carries an average price reads "Binance filled 0.0059 ETHUSDT at $2,500.01" instead. This is packages/web/src/components/conversation/proposal.tsx, with the sentences from packages/web/src/lib/describe.ts.

From the command line#

The same two actions as plain HTTP calls, useful for scripting or for checking the desk against the API directly:

curl -X POST http://localhost:4000/api/sessions/ol-3f0c.../approve \
  -H "Authorization: Bearer $OLAI_OWNER_TOKEN"

curl -X POST http://localhost:4000/api/sessions/ol-3f0c.../reject \
  -H "Authorization: Bearer $OLAI_OWNER_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"reason":"I want to see the weekly close first."}'

The reason is optional, up to 500 characters. Left out, it records "The owner gave no reason."

What approval actually does#

Read from SessionRunner.approve in packages/agent/src/session/session.ts, in order:

1. Already done? If the session is executed, or the runner has already reached the exchange for it, the existing record comes straight back. Approving twice sends one order.
2. Still pending? Anything else that is not pending is a 409 saying what state it is in.
3. The rulebook runs again, against an account snapshot taken now, not the one from when the proposal was made. The day's loss, the open positions and the kill switch can all have moved while you were thinking. A refusal here writes a rule.refused line and the session becomes refused. This is the check that stops an approval clicked twenty minutes late from trading against a state that no longer exists.
4. The approval is recorded as an approval line by the owner.
5. The session is marked as ordered before the exchange is called. If the send throws, we do not know whether Binance got it, and a second attempt could buy twice. One order per session, even a failed one, is the safe reading.
6. The order goes out, with the session id as the client order id, so a line in Binance's own records can be matched to a line in Olai's.
7. The result is recorded: order.filled on a fill, order.failed when Binance comes back REJECTED or CANCELED, or when the call threw.

In a dry run, steps 6 and 7 do not happen. The session goes to executed and an order.sent line marked dryRun: true says plainly that nothing was sent to Binance.

What rejection does#

The session becomes rejected and a rejection line goes in the ledger with your reason. Nothing is sent. A rejected session cannot be approved afterwards: a second call gets a 409.

The ledger lines you should see#

For an approved order that filled, in this order:

approval    by owner   Owner approved SELL BNBUSDT
order.sent  by agent   Sent SELL BNBUSDT for 15 USD
order.filled by binance FILLED: 0.0231 BNBUSDT for 15.00 USD

For an approval the rulebook stopped:

rule.refused by rulebook The rulebook refused this order at approval time: <reasons>

Errors you can get#