Skip to main content

​
Proposals

With proposal permission and the necessary reads, an assistant can submit a typed change. It remains pending until you review and approve it inside Geldee. The agent cannot approve its own proposal. A stale or expired proposal must be reviewed again through a fresh request.

​
Direct editing

Only enable direct editing for the areas you want an assistant to change. Each area is separate: transaction editing does not grant asset, debt, budget or other editing. The agent must:
  1. Obtain the exact records and confirm the user’s requested change.
  2. Call preview_change with a fresh UUID request ID and the typed change.
  3. Inspect the returned before-and-after result.
  4. Call apply_change with the identical request ID and change, plus the returned previewVersion.
  5. Inspect the receipt and reread the affected records and canonical totals.
A preview expires after ten minutes and binds the request, records and authorization. Changed inputs, stale records or changed permissions reject the edit. Direct editing does not require a separate approval click for each change once that edit area is explicitly authorized.

​
Retry and undo

Retry a confirmed request with exactly the same arguments and request ID. Do not generate a new ID because a response was lost: that could describe a second operation. Undo is available only when the receipt says it is supported and current record and permission guards still pass. An agent can undo only its own supported direct edits. Do not promise undo for every creation or import.

​
Limits

No tool moves money, pays a bill, trades, connects a bank or refreshes bank data. Editing a saved record is different from operating the real account. See the transaction-correction workflow and tool reference.