Ask and Act
The two chat modes, the approval card every change goes through, the undo that survives it, and how conversation sharing works.
The mode control sits in the composer, and it decides one thing: whether Chat is allowed to propose a change at all. It never changes the price of a message.
Ask mode
Ask is read-only, enforced at the tool layer rather than by prompt wording: in Ask mode the write tools are simply not available to the assistant. The composer states the contract in one line: reads only, and it cannot change anything or spend credits beyond the message itself.
Ask answers questions like "who is cited instead of us", "which pages does that answer read", "what moved this week" and "where did the credits go", from your own tracked data.
Act mode
Act adds the ability to propose changes. Proposing is not doing: every change arrives as an approval card that shows exactly what will happen before it runs, and shows the price when the action has one.
- A card that saves something into your account, a keyword, a prompt, a task, says what will be saved.
- A card that changes your live site, one page's SEO title and meta description, shows the exact before and the exact after.
- A card that runs a priced action, a fresh check or an article draft, quotes that action's own rate first.
Nothing is applied until you approve the card. Declining is free, and the conversation carries on.
The undo
An applied page fix keeps its undo. RankX AI records the values that were there before it wrote, so a revert restores them exactly, not a regenerated approximation. The undo is read from the run's own ledger, so it survives a page reload and does not depend on the conversation still being open. Every write, applied or reverted, lands in an audit log with who approved it.
Proposals expire
An unapproved proposal does not wait forever. If you come back to a stale card, ask again: the assistant re-reads the live state and proposes against what is true now, not what was true when the card was made. A proposal made against a page that has since changed is the thing this rule exists to prevent.
Sharing a conversation
A conversation is yours. You can share one with a teammate in two roles:
| Role | May |
|---|---|
| Collaborator | Read, send messages, and approve or decline proposals |
| Viewer | Read only |
Sharing a conversation never widens project access: someone who cannot see the website behind a conversation does not gain it by being handed the conversation.
Last updated
Chat
The assistant behind the Browse/Chat toggle. Ask reads your data and answers in plain English; Act proposes changes that run after you approve them.
What it can and cannot do
The complete capability statement, in three bands, including the permanent limits. Chat's abilities follow what each tool is enforced to do, never marketing.