Roles & solo mode
Working roles solo, ops, product and dev change how Loomaly answers. The role is guessed from your assistant and you can change it.
Loomaly has a working role on your account: solo, ops, product or dev. It is separate from project membership (owner / admin / member). The working role only changes how tools phrase say and which next step they suggest — for example whether to offer send_to_dev.
The four roles
| Role | Best for | Typical next step after todo |
|---|---|---|
| solo | You build and ship alone | Apply fixPrompt in this repo, open a PR, then check (target: fix) |
| dev | Developers in a coding assistant | Same as solo: follow fixPrompt, open a PR, check (target: fix) |
| ops | Marketers / SEO ops in chat | send_to_dev for paste-ready task text, then check (target: fix) after the PR |
| product | One focus page, one change a week | Prefer focus / set_goals; ops can still send_to_dev |
The top todo item already carries fixPrompt. Call problem only when you need more detail.
How the default is chosen
On first use, Loomaly looks at the OAuth client that connected:
- Cursor, Codex, Claude Code (and similar coding clients) →
dev - Everything else (Claude web, ChatGPT, unknown) →
ops
That default is saved on your account. You can change it anytime.
Change your role
In chat:
statuswithsetRole: "solo"(orops/product/dev)set_goalswithmemberRole: "solo"(same values)
Or in the account UI when available (account.setMemberRole).
Sites and who pays
- One site is one project. Your plan's site limit counts projects you own. Invited projects do not count against your limit.
- Scans and data-budget spend come from the project owner's plan.
- Emails (scan complete, weekly report) go to the project owner.
Invite teammates and manage ownership under /account for that site. Deleting a project frees a site slot; it does not refund pages or data budget already used.