Help
Get started with resolvenengine
Straight answers about setup, permissions, account connections and the current release boundaries.
What does resolvenengine do?
It is a Chrome side-panel assistant that can use released integrations and interact with supported websites while you work.
Which browser is supported?
The current product is delivered as a Chrome extension. Chrome must be running for browser actions.
How are connectors different from browser actions?
Connectors use structured service operations. Browser actions work through a supported website interface when a direct operation is unavailable.
Why are Google sign-in and Gmail consent separate?
Google sign-in identifies your resolvenengine account. Gmail access is a separate authorization you can review and revoke.
What do operation permissions control?
They let you decide which actions may run and which should ask before execution. A denial is never bypassed.
Is AI usage included in the subscription?
No. Pro is $19 USD per month and requires your own supported AI API key. Provider charges are separate.
How do renewal and cancellation work?
The proposed plan renews monthly. Once billing launches, you will be able to cancel renewal and keep access through the paid period.
What syncs between installations?
Account-linked conversation text can persist. Raw uploaded image and PDF files are not all cloud-synced in the current release.
What happens when a connection expires?
Google or ClickUp can revoke or expire access. Reconnect the service and review its permissions again.
Are more integrations coming?
Several services are planned, but they will be listed as available only after implementation and release verification.
Connection troubleshooting
- 1. Confirm Chrome and the extension are up to date.
- 2. Reopen the service connection from the extension.
- 3. Review the account and requested permissions in the provider window.
- 4. If access expired, reconnect rather than sharing a token.
Need help?
Describe the visible error and the action you were attempting. Never send API keys, OAuth codes, email contents or access tokens.