Agent Zero - A personal, organic agentic framework that grows and learns with you

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

[robi]

@timconsidine said in Agent Zero - A personal, organic agentic framework that grows and learns with you:

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

Yep, like a stack of crons, one for polling the email, then another cron polling the processing of the attachments, then another to move the task to a place the agent can pick it up, and/or like you said a TG task. (not sure it needs to go out to get back in when it's all local..)

[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]

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)

[timconsidine]

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)

[timconsidine]

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.

[timconsidine]

Packaged upstream 0.9.8.2 as a Community App

https://forum.cloudron.io/post/122050

[timconsidine]

There are some 'breaking changes' on AgentZero from my last community app package. Their v1.15 uses a different architecture.

Deciding now on how to support 'migration' from old app to new app.

If anyone out there is using my CommunityApp, please do let me know.

It might influence how I handle migration ... or whether I even bother and just start fresh (yes, very lazy, but ultimately pragmatic).

[timconsidine]

I have updated my community app for AgentZero to upstream v1.20.

There were too many breaking changes between the original version, so I packaged fresh (almost), trashed my original install and installed fresh instance.

Much nicer interface in 1.20, more hand-holding for setup.

[timconsidine]

Grrr - they dropped upstream 2.0
Having a bash at packaging it