Congrats to Fang Cheng and Caeli on the launch

Excited for this launch Fang Cheng. These types of tedious yet simple rules based decision making is what AI agents are perfect for.

On a post by Fang ChengInventor, Entrepreneur (Multiple Exits) | Co-Founder & CEO @ Caeli | Working on making the internet benefit-ready. Partnering with people-first organizations to unlock the $200B+ benefits economy.
I am so incredibly excited to share what we have been building over the last few months. It is finally time to make the internet benefit-ready. 🚀 Every year, American workers hand back billions of dollars in unspent funds. Why?
Read Fang Cheng’s full post on LinkedIn 
  • AI agents

Keep reading

Software architectureAI agents

Absurd, a Postgres-native workflow engine for edge agents

Really cool Postgres-native workflow system. The agent's entire pause/resume state lives in the DB; the worker process can exit. For running AI agents on the edge on end client machines, this is the unlock: because the whole engine is one SQL file + stored procedures with no broker, no coordinator, no SDK-based orchestration in code. It also makes the entire execution workflow history immutable and viewable by a self-reflection agent. On local/edge where processes die routinely (laptop sleeps, browser tab closes, network drops, edge worker suspends), an agent that has already made 20 expensive tool calls resumes at step 21 instead of re-paying for everything. You get this without writing checkpoint code or a state machine; the trace of completed steps is the agent's memory. I’m a fan of the pattern where the data itself captures the state in an idempotent sort of way. earendil-works.github.io/absurd

AI agentsSoftware architecture

Separate working agents from codegen agents that build them

As agent prompts become an important part of the codebase, there needs to be an explicit separation of an agent with a prompt that does something and a codegen agent that generates another agent. An example is in scraping, a first agent uses the screenshot and DOM structure to fetch some data. And a meta codegen agent generates a piece of typescript code + prompt that is essentially the first agent. So the codegen agent is creating the prompt and agent graph the agent that does the work.