Cloudron Forum

House-keeping :

• Cloudron have announced they will introduce support "in-platform" for custom app deployments
• consequently CCAI (the open hosted-as-a-service version) can no longer be installed from CCAI. (It can be installed manually if really needed but I don't really see why anyone would want to).
• CCAI-P (the personal edition which stores auth creds locally in app) can no longer be installed from CCAI : if you want CCAI-P, use the new https://customappgateway.appx.uk distribution point
• CCAI-P has been cleaned of legacy auth timeouts (inherited from original CCAI) so runtime gremlins should not occur. There is still a manual logout and connect option, in case the user wants to do so manually. Otherwise it should remain 'ready to go' without timeouts.

Improvements :

• both CCAI and CCAI-P still focus on new installations, and there is no support for updating an existing custom app. I am working on introducing support for updates.

The Future :

• with Cloudron's announcement that their v9.1 release will include some support for in-platform deployment of custom apps, "the writing is clearly on the wall" and CCAI / CCAI-P / CustomAppGateway will die and git repos / docker images will be removed at some point.
• I doubt anyone is more pleased than me !
• however we do not know the timescales for Cloudron 9.1 (other big stuff in it too), so I will continue to make available CCAI / CCAI-P until some point after Cloudron 9.1 is stable.

I'm calling this a v1.0.0 package
I may add/tweak something later, but I'm now using this as a production tool.

Currently I like it more than openclaw (clawdebot, moltbot).
But returning to work on my package of openclaw, and will reconsider which is better when openclaw package is complete.

I really like Agent Zero support for Telegram, and a relatively easy addition of new skills and tasks using the /run xxx structure.

My testing and live usage has mostly been with my selfhosted Ollama instance which is configured with ollama cloud models (so large models run on ollama servers). Seems low cost and large power).
If you test with other providers and issues found, let me know.

It's a big image (3.9Gb), so make sure you have disk space. But it installs quite quickly.
Make you set memory for your installation quite high - I have 4Gb and maybe will bump a little higher for production use.

v0.1.12 : fixed searx issue, now using Brave Search API key

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

@miednr I build all my apps using local device docker, push to a cloudron private registry and use cloudron install --image xxx.
I feel guilty in some way for not using Cloudron Builder, but local gets the job done fine, so good that you got your build out and deployed.

Nice, but I know nothing (yet) about Ansible

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

@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.

@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.

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)

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 !

@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.

@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

v0.0.6 : added telegram support
v0.0.7 : fixed telegram support
pushed to git.cloudron.io/cloudron-agent0 and docker hub image tcmbp132021/cloudron-agent0:latest

clawdbot / moltbot / openclaw is an amazing piece of work, but in comparison to Agent Zero, it feels hacky. But their idea of a telegram integration to fire off a task is so cool, it is sweet and glacial

So I baked it in to AgentZero.
Get yourself a telegram bot and set it up with AgentZero - work inside and with AgentZero to build your task/skill - invoke it hands-off via a Telegram command.

I'm not much into Discord, Slack, WhatsApp, Signal, but if there's a demand for them as interfaces to AgentZero, I can look at adding them in.

v0.0.5 pushed / image updated (:latest / v0.0.5)
tested scripting ... built by AgentZero itself.

Gave it a supplier's nasty website who doesn't email out invoices, requiring manual login to collect invoices and download. Well, not manual any more.

AgentZero built a custom python script to check every Monday morning if a "ready to collect" email has been received, and if so, logs in, handling the OTP issued, downloads the invoice.

I know, it's not rocket science .... except that AgentZero built the custom script based on a brief.

For sure, it needed a while to test and refine different approaches, because of the supplier's nasty strange website. But who cares, it wasn't about the speed of development, it's about the fact that I hardly had to lift a finger.

v0.0.4 pushed
some updated instructions on using selfhosted ollama In AgentZero

(n.b. I mostly deploy ollama cloud models so the processing is offloaded : not fully selfhosted but a step towards more data privacy)

Update git repo to v0.0.3 and pushed new image to docker hub tcmbp132021/cloudron-agent0:v0.0.3 (also :latest)

More work to do but preferring Agent Zero to openclaw - persevering with both.

@jdaviescoates I used to make it a point of principle to submit and pay at 23:55. But I'm getting more accommodating - I'll settle for 13:00 nowadays.

Tried to use Agent Zero to do my tax return !
TBH, this version's PDF capabilities were not good.
So I am making a new version with enhanced PDF query functions.
Standby ...

@marcusquinn

Interesting : now I see that many of his creations are listed as plugins/extensions within moltbot/openclaw

"Ship beats perfect"

Ha ! Don't I know it (from packaging moltbot).
Far be it from me to challenge this, but I think he should revise his approach.
"Shipped and properly working, not incomplete, beats perfect" might be better.

@marcusquinn started packaging it ....