Ask Fóir

Two ways in, one conversation

Open the command bar and choose Ask Fóir for a quick question, or use the panel on the right for longer work, which stays open as you move between screens. Both share one conversation. The assistant knows which workspace, project and page you are on, and sees the record open in the editor, unsaved changes included.

Your own permissions

Each turn runs on a token minted from your live console session, carrying your effective permissions in that workspace and project and never more. The assistant is offered only the tools those permissions allow, from the same catalogue an agent connected over MCP receives. Its writes are attributed to the assistant acting for you.

How edits are staged

With a record open in the editor, a change goes into the form as an unsaved edit. Nothing reaches the server until you save, and you can discard it. Writes to other records land as drafts on models with publishing enabled, and publishing is a separate action.

Anything that is neither a read nor a safely repeatable write shows an Approve or Deny card first. Publishing, unpublishing, reverting, deleting, revoking a key and updating a record you do not have open are approved one at a time. Creates and schema changes can share one approval.

Actions on a field

Ask Fóir also appears on individual fields in the editor, with six actions: generate, rewrite, expand, shorten, change the tone and fix.

AI credits

The assistant spends AI credits from the workspace balance, and how many you have depends on your plan. When the balance runs out, the assistant pauses and offers a top-up or an upgrade, and the rest of the console keeps working. A project can be given its own cap on the Usage page. foir chat is the same assistant in the terminal, on the same permissions and meter.