Claude Code dynamic workflows move abstraction up a level

Claude releases workflows. This moves the abstraction layer one level up again. Rather than having to craft a multi-agent harness for your codebase, this allows Claude to intelligently come up with the harness.

The workflow is modeled as a DAG with agents as nodes. So its a generic computation construct. Elegant!

claude.com/blog/introducing-dynamic-workflows-in-cl…

table
  • Coding agents
  • 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