[compare · ai assistants]
An assistant built around the people you work with.
[the seam in one line]
Oppulence centers on relationship context from authorized emails, meetings, and notes, with review before external sends and writes.
The goal is continuity: one assistant, one relationship memory, and one action history across Web, Desktop, and Voice. That shared experience is still being connected.
The seam
01 · the usual category
What a generic assistant is for.
A prompt, a model, a reply. Maybe a browser. The memory is the chat thread. External sends, if they exist, are easy to turn on and hard to trust.
02 · where oppulence sits
What the copilot is for here.
Desktop chat with MCP and builtin tools. Web agents and workflows for definitions you want in the cloud. Writes to mail, Slack, calendar, or CRM stay behind the same approval boundary.
Where the jobs split
Memory
01- The usual tool
- The conversation
- Oppulence
- Vault files, live notes, and the signed-in register
Tools
02- The usual tool
- Vendor plugins
- Oppulence
- MCP in ~/.rowboat/config/mcp.json, plus builtin mail and files
Background work
03- The usual tool
- Sometimes a scheduled prompt
- Oppulence
- Desktop or API target. API path uses Temporal.
Customer-facing send
04- The usual tool
- Often a toggle
- Oppulence
- A draft. Then a person.
Local option
05- The usual tool
- Rarely a real vault
- Oppulence
- BYOK and a folder you picked
Honest limits
- This is not the older visual agent-builder in the legacy rowboat app.
- Money-moving MCP scopes in the managed registry are not a production claim.
Questions people actually ask
Oppulence is organized around relationship context and follow-through. Source review, private notes, and approval are part of that experience; the model helps prepare the work.