I am launching Relaticle here next Tuesday. It is an open-source CRM where AI agents can do real work on your data, and I want feedback on one design decision before launch day.
Relaticle has two trust levels. External agents (Claude Desktop, Cursor, any MCP client) authenticate over OAuth and write through 37 tools directly, like an API client. The in-app assistant is stricter: every write it wants to make becomes a proposal card, and a person approves or skips it record by record before anything lands.
The question I keep going back and forth on: is per-record approval the right granularity, or does it become noise once you trust the assistant? Would you want a "trust this kind of change" switch, or does that defeat the point?
If you run a CRM with any AI in it today, I would like to hear where you draw that line. The whole thing is AGPL and self-hostable, including the model via Ollama, so you can look at how it works rather than take my word for it.
Softorino 💻📲
Really like the approach here! Letting AI do the heavy lifting while keeping users in control of every change feels like the right balance. Have you considered adding customizable approval rules for low-risk updates?
Relaticle
@yelyzaveta_kibets Thanks, Lisa! A few people have asked about this today. I’m considering it, though deciding what counts as low risk is tricky. Which updates would you want to skip approval for?
Softorino 💻📲
@manukminasyan I would draw it at additive. Let it add a note or a field on its own, and require approval when it overwrites or deletes anything already there.
Dial
On the auto-approval question, I'd be wary of it even with policy rules. The whole pitch here is that the assistant's writes are legible to a human before they land, and policy-based auto-approval is basically a slow reintroduction of silent writes once someone gets tired of clicking approve. If anything I'd want auto-approval scoped to read-adjacent stuff like tagging or dedup, never to fields that touch pipeline value or contact ownership. That said, 37 tools over MCP with OAuth is a lot of surface area for a two-year solo project, curious how much of that is generated vs hand-written.
Relaticle
@galdayan @galdayan Fair concern. I’d be cautious with dedup too. One clarification: approval applies to in-app chat; MCP writes execute directly within granted permissions.
I wrote the code by hand before Opus. Since then, I’ve used it to help write code, reviewed every line, and made the architecture decisions myself.