Connected services
Gmail, Drive, Calendar and ClickUp operations, according to the connected account and granted scopes.
Browse integrationsProduct
One assistant for your browser and connected apps
Move from a request to visible action without constantly switching tabs, copying details, or retracing context.
Start from a conversation
Describe one supported task and keep its context in view.
Match a released capability
The current selector uses task-matching rules, not a universal semantic planner.
Watch the action
Review connector activity or browser interaction as it runs.
Control permissions
Write operations can stay set to ask before execution.
Stay in Chrome
Browser actions run while Chrome is open; this is not an always-on cloud agent.
Illustrative product preview
resolvenengine
ClickUp · Search workspace tasksUsing the workspace's real status names4 tasks are in progress
Review the matching tasks and open any item in ClickUp.
Ask a follow-up…
What is available now
Browser assistance
Supported tasks performed through website interfaces, with page state and layout as practical constraints.
See practical tasksConversation continuity
Account-linked conversation text can persist. Raw uploaded files are not all synced across devices.
Ready to work in your own Chrome?
Install resolvenengine from the Chrome Web Store. Sign-in, subscription and billing happen inside the extension.
Prompts that map to a released capability
The assistant is deliberately not a universal planner. A request is matched against released operations, so the useful prompts are specific ones. These are the shapes that work today, written the way people actually type them.
Work in the tab you are on
- “Fill this form with the details from the attached CSV row 4.”
- “Go back to the previous page and tell me whether the price changed.”
- “Take a full page screenshot of this article and give me the key numbers.”
Browser work stays in the active tab. A new tab is opened only when a task genuinely needs a second page, and the “Work in a new tab” setting is respected.
Research without a tab storm
- “Research the top five AI news items of 2026 and cite your sources.”
- “List five software companies in Budapest with a link for each.”
Open web research runs in the background through a server side search path and returns a cited answer. Pages are opened only when interaction or visual inspection is required.
Connected work
- “Summarize my unread emails from this week.”
- “Summarize the last 20 messages in my Slack project channel.”
- “Show my top queries for the last 28 complete days.”
A connector is used when the request clearly points at your own data. A bare service name is not enough on its own, and ambiguous requests are clarified instead of guessed.
Allow, Ask and Deny, per operation
Every connector operation carries its own policy. Reads can be set to Allow so a summary needs no interruption, while anything that writes can stay on Ask, which produces an approval ticket naming the exact target before it runs. Deny removes the operation from the toolset entirely, so the model cannot select it even if the conversation drifts in that direction.
| Policy | Typical use | What happens at run time |
|---|---|---|
| Allow | Search, read, list, report | Runs immediately and reports what it read |
| Ask | Send, create, commit, comment | Pauses with an approval ticket naming the target and payload |
| Deny | Anything you never want attempted | The operation is not offered to the model at all |
Cost model: your own AI key
Pro is 19 USD per month and includes every released connector. Model usage is not resold: you add your own supported AI API key and the provider bills that usage directly to you, at the prices published on their pricing page. Two practical consequences: you can pick a stronger model for a hard research task without a plan upgrade, and a stopped task stops spending, because the run ends where you stop it.
Limits worth knowing before you start
- Browser actions run while Chrome is open. This is a side panel assistant, not an always on cloud agent.
- Search Console data commonly lags by 2 to 3 days, and every answer built on it states that delay.
- GA4 standard reports can stay incomplete for roughly 24 to 48 hours, so same day comparisons are not reliable.
- Connector visibility follows the connected account. An empty result can mean missing access rather than missing data, and it is reported that way.
- Page based tasks depend on the live layout. When a page changes shape mid task, the run reports the failure instead of inventing a result.