An answer, or an action. You choose.
Understand the two modes, select useful page context, and know when a task counts.
Chat is for thinking and drafting.
Ask for an explanation, a summary, a rewrite, or a draft response. Chat returns text for you to review. It does not perform WebAct page actions.
WebAct browser Chat stays free and does not consume your monthly automation allowance. The connected provider’s limits and data controls continue to apply.
Task is for a result on the page.
Ask WebAct to extract data, enter values, or work through a bounded page workflow. Say what should change and how the result should be checked.
Review sensitive actions and any request for clarification. If the task reports uncertainty, inspect the page before trying again. Starting a new instruction is different from resolving a necessary clarification within the existing task.
Share the useful part.
Select a specific region when the rest of the page is irrelevant. If you use visible-page context, check the coverage: hidden rows, earlier messages, unloaded content, or another tab may not be included.
The selected connection processes shared context. Chat and automation in the extension are not local-only.
One automation, one task.
The Free plan includes 25 automation tasks per UTC calendar month. A task counts when its first action begins. Its agent steps, retries, recovery, and necessary clarifications retain the same task identity.
After the allowance is used, browser Chat stays free. Wait for the next month or choose a paid plan to continue automations without a WebAct task cap. Provider limits still apply.
Keep what worked.
Save a successful task in your library. Reusing it reacquires targets from the current page rather than relying on an old page snapshot.
Saved work is separated by verified account in the current browser profile. Local saved tasks and text histories are not a promise of cross-device cloud synchronization.