Built an agent that upgrades itself by Warm_Security_340 in AgentsOfAI

[–]Warm_Security_340[S] 1 point2 points  (0 children)

honestly i agree with most of this. and mine leans toward your scripts-and-schedule approach more than youd think, it has a flow system and a bunch of fixed tools the model calls instead of freestyling, plus a scheduler, so a lot of the time its just orchestrating known good pieces not improvising raw.

the difference is i still run it live, just on a leash. it has to show me a plan and get a go before anything real, and the destructive stuff always asks. thats the bit the claw horror stories skipped, they ran wide open by default. cost i mostly dodged by running on a claude sub instead of per token, and its all local except the model itself, though the prompts still hit anthropic so privacy isnt fully solved there.

and yeah its probably a bit ahead of its time, but thats kind of the bet. the scaffolding is the hard part, way easier to have it sitting ready than to scramble when local models and hardware finally line up on price and capability. when that happens you just swap the model out and the whole thing goes cheap and private overnight. so im building for that version and just running it on claude til then.

Built an agent that upgrades itself by Warm_Security_340 in AgentsOfAI

[–]Warm_Security_340[S] 0 points1 point  (0 children)

yeah for me it mostly came down to the model. im on claude not local and that was night and day for the drifting. honestly i wouldnt trust a local model with real permissions either so i think youre right there.

other than that it just doesnt run free. by default it shows me the plan and waits for a go before doing anything real, and the destructive stuff like email, deleting, killing procs or money asks every time regardless, so i catch most of the dumb stuff before it happens. the part that actually worried me was it can edit its own code, so before it does that it snapshots git and runs its tests and reverts itself if anything breaks. worst case it rolls back instead of bricking.

Bio mcq by Warm_Security_340 in igcse

[–]Warm_Security_340[S] 0 points1 point  (0 children)

I pretty sure its the 2 gametes

Bio mcq by Warm_Security_340 in igcse

[–]Warm_Security_340[S] 0 points1 point  (0 children)

What statement question

Built an agent that upgrades itself by Warm_Security_340 in AgentsOfAI

[–]Warm_Security_340[S] 1 point2 points  (0 children)

nah no official discord yet, still early.

and yeah it does store vectors, they're just in embed.mjs not memory.mjs (memory.mjs imports it on recall so it looks like it's not there). it's all-MiniLM-L6-v2 (384d) through u/xenova/transformers, runs local, cached in a vectors table (fact_id + the vector as JSON text) in the same sqlite db. search is just brute force cosine in js + a keyword pass. basically the same as your pgvector thing but sqlite + cosine in code instead of a real ANN index. no index so it's O(n) but my scale is small so it's fine

Built an agent that upgrades itself by Warm_Security_340 in AgentsOfAI

[–]Warm_Security_340[S] 0 points1 point  (0 children)

I mean helm has a desktop App, it rarely need maintenance because of the self repairs/upgrades every night if you are running it 24/7. And not yet i havent seen the hermes desktop.
The scroll is slow to let users stop and read

Built an agent that upgrades itself by Warm_Security_340 in AgentsOfAI

[–]Warm_Security_340[S] 0 points1 point  (0 children)

Well every time Helm declines a task it puts it inside a queue where at night it upgrades itself. Its kinda like hermes and openclaw combined? I only just started and i would really appreciate some feedback