Use settings and the developer space
Settings are available from the account area. They control personal interface preferences and provide links to account-scoped actions.
Account and privacy
In General settings, you can customize:
| Setting | Action |
|---|---|
| Appearance preference | Choose your preferred look |
| Interface language | Choose your language |
| Accent color | Choose your accent color |
| Sign out | Sign out from the current device |
Use the privacy-policy link to read the current Anywe Privacy Policy.
The account area includes an account-deletion flow. It requires you to type DELETE exactly before the final action is enabled.
Deleting an account is irreversible in the app: it removes the account, conversations, contacts, and agents owned by that account. Do not start this flow unless that is your intended outcome.
Review agent permissions
Settings includes a permissions area for connected agents. It shows the scopes currently granted when that information is available and may mark scopes newly requested since the last consent. Select Manage on an agent to review the permissions controls offered by the app.
You can also open your blocked list and consent-management views from Settings. These routes show their own loading, empty, or error state when the relevant information is unavailable.
Enter the developer space
Use the Developer entry in the workspace sidebar to open the developer space. It is separate from the normal conversation workspace and includes areas for overview, monitoring, analytics, errors, revenue, versions, and setup.
You must be signed in to use the developer space. If your account does not yet have a publisher, the page presents publisher registration and an account-level CLI-token area.
After a publisher is available, developer-space routes show information for your own publisher account. The developer space includes a visible link back to the app.
Settings and developer problems
A developer-space sign-in prompt means the page cannot show publisher information until you authenticate. A publisher-registration screen means the account has no publisher record yet.
If a publisher lookup fails, the page shows an error rather than an empty developer dashboard; retry after the error is visible.
For settings actions, use the confirmation text and disabled controls as the source of truth. For example, the delete control remains unavailable until the exact confirmation word is entered. Do not treat a disabled action as evidence that the change completed.