[compare · ai assistants]
Chat without tools is a drafting window.
[the seam in one line]
A generic desktop copilot can write a paragraph. Oppulence can see the vault, the ledger, and the mailbox — and it still will not send until you approve.
We are not a ChatGPT skin. The assistant is useful because it has tools and a place to put the result. Autonomy without a gate is just spam with better copy.
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
No. The useful part is the register, the approval gate, and the local vault. The model is a means.
