Cloudron Forum

timconsidine

@robi thanks for that link
still working on my openclaw package, so that will be useful (incorporated if I can)

BrutalBirdie

Updated the app to version 13.351.

Update:

cloudron update --app $YOUR_APP_LOCATION --image brutalbirdie/foundryvtt.cloudron.app:0.1.1

msbt

apparently the successor of the tool has/will have one: https://controlr.app/

New repo: https://github.com/bitbound/ControlR
What happened: https://github.com/immense/Remotely/issues/985 --> https://github.com/bitbound/ControlR/discussions/84

timconsidine

@humptydumpty apologies for the rough ride you're experiencing - CCAI-P was spawned from CCAI and while I removed some things for the personal scenario, I think I mistakenly left in the auth timeout.

I have a total rework of CCAI and CCAI-P in production. It might be redundant in terms of Cloudron's announcement of 9.1. But they have a number of big items in that release so maybe I can get the re-worked versions out for a some some service lifetime until 9.1 is available.

Usually logout + connect clears it, but maybe mileage varies.

timconsidine

@luckow strange ... and apologies

line 1 and column1 is unusual
let me look into it.

do you have any more logs (sanitised if need be) ?

problems I hav e seen in CCAI-P are all due to the timeout (inherited from CCAI and due to be removed) on auth - usually solved by logging out (button above list on right of screen, then pressing the connect button which appears in the middle of the screen. I guess restarting does the same thing in effect.

timconsidine

v0.1.6 : ensured MCP servers work, resolved searx dependency

now pushed to git.cloudron.io/cloudron-agent0 and docker hub image tcmbp132021/cloudron-agent0:latest (aka v0.1.6)

girish

We initially tried to keep it separate. The reason to put them together was that when you make a new backup (which is a button on the site), nothing appears to happen after it finished. Open to other ideas.

timconsidine

v0.0.8 : **extended telegram bot functionality **
now pushed to git.cloudron.io/cloudron-agent0 and docker hub image tcmbp132021/cloudron-agent0:latest

/run : launch custom user scripts (no container rebuild) from your telegram app - open extensibility :
- invoice / document downloader (send it a link)
- task manager (add/remind/complete) ??
- <whatever you would like it to do>
/chat : chat with AgentZero from inside your telegram app
/learn : get AgentZero to memorise new info
/health : get AgentZero core system report

Bonus cool : some of this was designed/built by me & my TRAE dev assistant, but some was AgentZero itself !
Suggesting and writing changes "to itself" (well, to how the telegram bot could be better deployed inside AgentZero).
Self-healing, self-extending apps around the corner !

timconsidine

@robi you're right.

I have set the task to be run only once per week, it checks for an incoming email received with a subject like "your invoice is ready" from a specific email address (the supplier).

It only executes anything if there is a waiting email like that.

So limited email box polling and very constrained execution scope, and no AI credits used at this point (at this stage it's not parsing or processing the downloaded invoice - just a python script).

AI credits used in building the script, but none currently in execution.

The script is not in the package, it needs to be built by AgentZero specifically to the Cloudron's users needs. I'm still tweaking the script, but don't mind sharing it afterwards as a generic script if anyone wants it (upload to /app/data/instruments and then tel AgentZero to build a scheduled task invoking it).

Manual admin tasks like invoice download and processing are the bane of my life, so I was excited by what openclaw offered, but I think it can be done better in AgentZero.

Specifically about notifying the agent, I'm just building a telegram invoked task - go get this invoice. That might be relevant to your comment.

timconsidine

@robi well, there could be 101 answers to that, email being what it is, but the way I have done it is :

AgentZero is deployed on Cloudron, e.g. a0.domain.tld, so I have set up a mailbox a0bot@domain.tld. Created an extra Cloudron user xxx_bot and made it the owner of the mailbox (i.e. it has it's own password, I'm not sharing my main password with AgentZero)
I tell AgentZero the necessary IMAP details, username a0bot@domain.tld, password, mail server address used by your Cloudron, port 993
AgentZero builds a task (script) using the mailbox config which it is given to poll for emails received, processes them and (optionally) deletes them, using the body content and attachments in the script it is building
I forward emails to a0bot@domain.tld from other Cloudron email boxes or my primary email (ProtonMail). The email from my Proton has a forwarding rule (e.g. send Hetzner invoices to a0bot@domain.tld). It could be manual forward or auto-forward.

This could be much slicker, but at this stage (a) I'm experimenting, (b) I'm controlling what gets sent to AgentZero.

Depending how ambitious one wants to get, you can build a whole array of email inbox processing w/o forwarding, e.g. just give it my primary Proton mail creds. Maybe I will be brave on that later

Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.

Cloudron Forum

AppDev

Posts

Member List