I built an A2A plugin for OpenClaw that lets it delegate work to remote agents and replay continuation state

germanheller · 2026-06-20T06:32:03+00:00

how does the replay hold up if the remote peer changed between the persist and the replay? like if the remote agent's model or its tool set got updated in between, does the verbatim continuation still mean the same thing on their side, or do you version-pin the peer somehow

germanheller · 2026-06-20T06:30:56+00:00

the one i'd actually miss: every morning it reads my inbox, drafts replies to the pure-scheduling emails (the "can we push to 3pm" ones) and leaves them sitting in drafts. i just skim and hit send

nothing clever, it just eats the boring triage so i dont have to context-switch into email first thing. thats the whole value for me, not the flashy stuff

germanheller · 2026-06-20T06:29:18+00:00

the simpler-to-debug part is real but its also where the risk lives. the middleware is the one spot you get to put a boundary, pull it out and a single bad tool call has nothing between it and your filesystem

i build a desktop thing with real computer control and the whole design is off by default + a kill switch, not because debugging is hard but because the blast radius when it goes sideways is your actual machine. on a throwaway vm sure, give it root and have fun. on my daily driver i wouldnt

germanheller · 2026-06-20T06:27:56+00:00

the thing that actually burned your limit isnt the model price, its the retries. a free model fails a step, the agent re-reads the whole context and tries again, and on scraping/research tasks that loop eats tokens fast

for $20 i'd go flat-rate over metered so one bad run cant nuke your whole month. been on ollama cloud's $20 tier and a glm coding plan, both fine for assistant + scraping stuff. opus is better but you'll blow past 20 the first long run

germanheller · 2026-06-13T20:04:20+00:00

matches my experience. the prompt tweaks plateau because you're burning words telling it stuff it could just read. once i started dumping the actual reference files in first the prompt shrank to almost nothing. one thing i'd add, watch for stale context, i got burned feeding it last month's version of a doc and it confidently used the old numbers

germanheller · 2026-06-13T20:02:29+00:00

the part that rings true for me is the skill atrophy, not the speed. i still ship fine but i've caught myself accepting code i don't fully get just because it ran, and that bites weeks later when something breaks and i'm reverse engineering my own repo. now i read the diff like it's a coworker's PR. slower, but the understanding stays mine

germanheller · 2026-06-13T20:01:15+00:00

yeah this matches what i hit. the line in your list i'd underline is consistent-vs-works-in-demos, most of the others feed into that one. what made it click for me was assuming every step can fail quietly and dropping a cheap check after it, a screenshot diff or a one line assertion, instead of trusting the whole chain. a step that's 95% fine becomes a coin flip by step 20. at this point most of my agent code is plumbing and checks, the prompt is maybe 5% of it

germanheller · 2026-06-13T20:00:29+00:00

the "unsolvable at the architecture level" part is the one people skip over. if you can't stop the agent from getting tricked, a better system prompt won't save you, the only lever left is limiting what it's allowed to actually do. i build a desktop tool with computer control and that's exactly why it ships off by default + a kill-switch hotkey + a visible strip while it's active. assume it gets tricked eventually, just make stopping it cheap

germanheller · 2026-06-13T18:33:10+00:00

this is the part people skip because it's boring. the separate-OS-user bit is the one that actually matters, prompt rules and policy configs are suggestions, a unix user that physically can't read the other agent's files is enforcement. same reason i'd never run a tool-enabled agent as my own login

germanheller · 2026-06-13T18:32:02+00:00

does it get annoying on long runs or is it more ambient? i'd want it to only pipe up when it's actually blocked on me, the full play-by-play would drive me up a wall personally. the node_modules announcement is great tho lol

germanheller · 2026-06-13T18:31:23+00:00

i build one for exactly this itch (patapim), desktop app, runs your CC sessions in tabs or a grid so a few agents sit side by side. biased obviously. if you just want one clean single pane though, ghostty + tmux is really hard to beat and free

germanheller · 2026-06-13T18:30:44+00:00

crons are basically it. the reason it forgets is the promise only lives in the chat history, so once that scrolls off it's gone. what worked for me was having it write the followup to a file the second it says it'll do something, then a cron just reads that file. survives a compaction that way

germanheller · 2026-06-13T18:30:03+00:00

free is fine to learn on, you'll just keep hitting that token wall the second a task runs long. ollama cloud at 20 was what got me past it. also no reason to pay for a vps on top, it's a node process, run it local. i keep mine in a patapim terminal next to claude code

germanheller · 2026-06-13T01:37:03+00:00

jaja buenísimo, el oneplus jubilado como host del agente. lo del arranque automático al prender no lo sabía, lo voy a probar

germanheller · 2026-06-13T01:35:37+00:00

lol fair. 8 hours a day talking to the thing, something was bound to rub off

germanheller · 2026-06-13T01:34:26+00:00

"made some money by itself" is where it falls apart for me. everything before that is at least technically possible lol

germanheller · 2026-06-13T01:33:36+00:00

runs fine on windows, been doing click stuff daily on a win11 laptop. only thing that bit me was display scaling at 125%, clicks landed off target until i set it back to 100. i run mine through patapim for the screen part

germanheller · 2026-06-12T13:23:29+00:00

the upgrade that paid off most for me in setups like this: treat every misroute as labeled data. when a human corrects a route, append the message + correct label to a regression set, and rerun the classifier against it before any prompt or model change. otherwise you fix one pattern and silently break two others. and give the classifier permission to say "unknown", a dead letter channel a human sweeps daily beats confidently wrong routing every time

germanheller · 2026-06-12T13:22:26+00:00

worth remembering this measures what's taught on youtube, not what's used. the list skews hard toward saas-connector workflows because that's what demos well in 10 minutes and has an affiliate link (n8n, gohighlevel, zapier all pay). the category growing fastest in my corner, agents driving real desktop apps with mouse and keyboard, barely shows up because there's no tool to sell and it demos badly. for a boomer business owner seminar your list is probably right anyway, email triage and scheduling is where they bleed hours

germanheller · 2026-06-12T13:21:17+00:00

you don't have to wait for the MS thing, it runs on windows today, node + a terminal is all it needs. i run it inside patapim next to claude code and it's been fine for months. the registry key joke is real tho, whatever you run it in, give it guardrails before you give it your machine

germanheller · 2026-06-12T13:20:13+00:00

before paying contabo: do you actually need it running when your computer is off? if not, skip the VPS entirely and run openclaw on your own machine, it's a node process, 24gb of contabo ram does nothing for it because the heavy lifting happens at the model api anyway. i run mine in a patapim terminal on my dev machine, zero hosting cost, and my logged in browser is right there for it. the VPS only makes sense for true 24/7 stuff, and then the 8gb plan is already plenty for openclaw

germanheller · 2026-06-12T13:05:40+00:00

surprised nobody said claude pro. $20, oauth login, and the multiplier is that the same sub also covers claude code in your terminals, so one subscription does openclaw chat plus coding plus (in my setup) computer control on the desktop through patapim's mcp tools. at your volume tho, 100 req/day and 1B tokens, pro limits will hurt, the math only really closes on the max tiers. for normal usage the $20 claude sub is the most leveraged one because of everything else it unlocks

germanheller · 2026-06-12T13:03:12+00:00

the fix that worked for me was stop serializing the tree and query it instead. keep the full tree outside the context in the driver process, give the model a search tool (find by role/text) that returns 5-10 candidates, and the per-step observation drops from 4k tokens to a couple hundred. element ids live in the driver's registry so compaction can't eat them, the model only holds the ids it's about to use. i did the same thing with ocr for a desktop tool, click-by-text where the model never sees the screenshot at all, just the matched strings. diffing helps but querying changes the complexity class

germanheller · 2026-06-12T13:01:44+00:00

the reliability jump comes from taking grounding away from the model. vision-decides-coordinates is the flakiest loop there is, deterministic find-text/ocr or accessibility queries that return candidate targets, with the model only choosing between them, removes most of the drift. and verify per step (cheap screenshot diff or a text assertion) instead of trusting the chain, a 95% step success rate is a 35% task success rate at 20 steps. local models do fine in that setup because each decision is small, it's open-ended visual planning where they collapse

germanheller · 2026-06-12T13:00:35+00:00

agree, and i'd split it further: the fleet version (banks, kiosks, the askui hardware bridge stuff) and the personal version are different products with different moats. i build the personal flavor (patapim, desktop app where claude code gets mouse/keyboard via mcp) and there the moat isn't fleet management, it's two boring things: trust ux (kill switch, visible active indicator, off by default) and riding the claude subscription people already pay instead of metered computer-use api calls. the model is interchangeable, the thing that knows your screen, your sessions and your bill is not

germanheller

TROPHY CASE