Hi there,
So openclawd is a security nightmare as it turns out and the bigest problem is letting loose an LLM on the web with all your credentials.
But I can’t shake the feeling, that something similar COULD work inside your Nextcloud instance. With the ai-backend mcp server even the arcjitecture is there, but we would need something, that would create an agentic loop.
So our AI assistant would be actually proactive!
Like in the morning writing you a brief about your day, with your calendar events and with your incoming e-mails. Proactivly reminding you of your tasks from the tasks and Deck. Organizing you e-mails perhaps? Warn you about overlapping events in your calendar and so on!
Like clawdbot but only in your Nextcloud, so it wouldn’t browser the internet.
Idk maybe I’m missing something, but my ADHD head always forgets everything even when it put in my tasks to do list or in Deck. I imagin it would be very helpfull for me if somebody was writing me from time to time, not to forget my todo, which is my Deck for months.
What do you guys think? How hard would this be to do?
Ps: Look before you guys eat me alive for this, yes I’m aware, that you still have to trust very much everybody on your instance, and the incoming e-mails, could be an attack vector. But for home use, if the agent doesn’t has web acces, I don’t think there could be a huge issue.
Honestly, I would not want something like this hard-wired in my NC instance. Giving access, yeah, that might be doable. Creating an agent (or more) to fulfill jobs? Yeah, also thinkable.
An agent is no generic “I do everything as you please” piece of software. Each agent has a clear job at hand and will try to do it. Honestly, I do not see the required infrastructure in the NC AI assistant at the moment (although I might be wrong here).
You could use an ExApp to add that missing infrastructure, I guess. But then you are writing just a wrapper for an agentic framework for usage inside NC. As this would be running inside the NC, you would have to manually duplicate all authorization stuff to prevent unintended access.
Why not providing an adjacent service (think Collabora) that can be triggered on request and need dedicated authentication?
Regarding AD(H)D: you know, keep to a rather strict schedule. Every day you should go though your daily tasks. Check them, priorized them. Verify with your plan of the day. Try to stick with it. An agent will not be able to help you if you do not look at it or tell him that you are distracted. I feel with you.
Personally, I think the NC tools are not well suited because a few elementary features are missing but this is a different topic. Look for what helps you the most.
Righ now, since I’m not really a coder, I’m thinking to somehow “wake up” the assistant we already have, with the flow app. If I could create a flow, whiwch writes to the Nextcloud assistant, using the assistant chat app, than I’m actually almost there!
It would be possible to develop something like this by configuring a workflow, for example in Windmill, to retrieve the information, parse it through the LLM, and send you the message. It would not be very hard to do even with limited coding experience.