Golemry: set up recurring AI agent jobs (any model, 900+ connectors), and an overseer layer monitors every execution so failures don't slip through.
Built solo, just launched V1. Showcase below, feedback very welcome: https://t.co/OfRd7Koqti
@simonw relentlessly proactive cuts both ways. that same trait once let an agent of mine improvise straight past a broken discord connector instead of failing loudly.
@tdinh_me gpt-image-2 dropped native transparency, it's trained to complete scenes, not cut out objects. gpt-image-1.5 still does clean native alpha, recraft is the other one with real transparent output. everything else is background removal bolted on after.
@jerryjliu0 auto-routing fixes the interactive case but would scare me for automation: recurring jobs need pinned model behavior, otherwise run 40 isn't comparable to run 4. a silent router upgrade is a silent behavior change.
@swyx took me longer to build the "ping me when it fails" part than the agents themselves. the hard part is defining failed: exit codes are useless when an agent confidently succeeds at the wrong thing.
@jerryjliu0 There are many easy tasks to automate with cheaper models, be it for coding with lookup tasks, or automating mechanic background tasks. Right now most seems to be done with "just the smart" model.
@tdinh_me Congrats. 36 websites from 41 users is the impressive number here. Nearly everyone who signed up actually built something, that's the metric most launches never see
@OpenRouter Price doubled and volume didn't dent. Matches what we see for unattended agent work: people pick the model that fails least, not the cheapest one, because a wrong but plausible run costs more than the tokens.
@gregisenberg launched mine on monday. The gap between "reading about AI" and shipping is smaller than ever. But also, the bar raises from a first MVP to shipping an MLP (minimum lovable product) with a lot of competition on it.
@tdinh_me I run scheduled agents against prod for my product, so I had to solve this. Setup:
Run the agent in docker vm. Run each tool in a separate sandbox, no env variables (everything in memory).
The ultimate move is to guard certain tool calls ofc.
@TeeDevh Vercel is scalable by design, in particular if you are using serverless NextJS and has a CDN behind it.
So it also solves all your future scaling problems for free without any thoughts about orchestration
@KaiXCreator Just want to outline that this thread was likey scraped by attackers, getting a lot of attack probing since I posted here yesterday.
Be sure to check your app.
@aliByteCode If you take a stroll in r/SaaS you will see a huge amount of people who are now enabled to build things with AI and now struggle to get any users.
@KanikaBK It’s impressive how China is embracing the open-source route to be competitive. This has been outlined as an official stance in the new 5 year plan and will for sure shake things up.