Hey everyone starting this thread as an open space for anything Ollie-related: how a connector works, why we made a certain call (like running everything locally instead of in the cloud), what's still missing, or just general feedback after trying it out.
A few things people tend to ask, to save you a search:
How's this different from just using ChatGPT with plugins? Ollie connects directly to Gmail, Outlook, Slack, QuickBooks and many more via MCP and can actually take action (send an email, draft a reply, pull real numbers) - always showing you what it's about to do before it does it.
Where does my data go? Nowhere but your own machine. Ollie runs as a desktop app with a local database - no cloud sync of your inbox or financials.
What's next? More connectors, and continued work on making the memory smarter the longer you use it.
If you hit a bug, have a feature you wish existed, or just want to know how something under the hood works drop it here. I'm reading every reply.
@basil_yaqoob Ollie’s local-first approach really stands out, especially with QuickBooks and Stripe actions. I’ve upvoted it. How are you handling permission boundaries for actions like sending emails or booking meetings?
@spotch_founder Thanks, really appreciate that! QuickBooks and Stripe are read only today. Ollie can pull invoices, aged receivables, P&L, customer and charge data, but there are no write tools wired for either one, so there is nothing there for it to accidentally do. Stripe runs on a restricted key you generate yourself with read only permissions set in Stripe's own dashboard, so the boundary exists even before Ollie's own logic does.
Gmail, Outlook, and Slack are where actual writes happen, sending an email, drafting a reply, booking or updating a calendar event, posting a message. For every one of those, Ollie shows you the exact action and its arguments and waits for an explicit approval before anything executes. That gate is enforced at the tool level, not just prompted for in the model's instructions, so it cannot be talked around.
Nothing fires without you seeing it first, and the highest stakes surfaces, your books and your payments, cannot write at all yet.
How do you handle auth tokens and permissions, can I ensure Ollie reads only on certain accounts?
@amraniyasser Good question. OAuth tokens are stored encrypted in Ollie's own local database on your machine, never sent to any server we run, and refreshed automatically when they expire. On the read only point, QuickBooks and Stripe have no write tools built into Ollie at all today, so those connections are read only by construction, not by a setting you have to remember to toggle. Gmail, Outlook, and Slack do have write capability, and there is no blanket read only switch for those yet, but every single write action still requires your explicit approval before it runs, so in practice nothing writes without you seeing it first regardless of which account it touches.