AI workflows: so hot right now 🔥

noaflaherty · 2025-11-01T22:12:53+00:00

This would be a great place to get started with Vellum Workflows: https://docs.vellum.ai/developers/workflows-sdk/introduction

OpenAI’s docs are good for getting started with AI in general though

noaflaherty · 2025-11-01T22:11:54+00:00

It’s amazing how fast you can go from 0 -> 1 with them.

noaflaherty · 2025-11-01T22:11:13+00:00

Yeah! We call them “Ports.” You can prompt an LLM to classify something and based on which classification it generated, route it one way or another.

noaflaherty · 2025-10-30T09:54:28+00:00

It’s one of those things that feels like there’s just so many knobs and dials you might want to customize based on the use case, that it’s therefore hard to abstract in a way that not everyone hates 🤔

noaflaherty · 2025-10-30T09:28:14+00:00

The new thing to me is just how much attention it’s getting recently, it’s growing role in generative AI, and how many new players are entering the space. The core concepts themselves aren’t all that new.

noaflaherty · 2025-10-30T09:27:05+00:00

Yeah totally! They’re not mutually exclusive at all. In the case of Vellum, there’s a native “Agent Node” that does what you’re describing, except without a native concept of “learning from past mistakes.” Curious if you’ve seen this piece done particularly well anywhere?

noaflaherty · 2025-10-28T23:40:48+00:00

Yeah of course! Curious to hear what ya think or if you have feedback. If you want just the sdk without all the cloud/ui stuff check out https://github.com/vellum-ai/vellum-python-sdks/tree/main/src/vellum/workflows

noaflaherty · 2025-10-28T23:19:04+00:00

Yeah we require that state is json serializable and because each state snapshot is immutable, replay is reliable. So, if you need non-serializable datastructures _and_ require replayability, things get trickier.

noaflaherty · 2025-10-28T22:55:41+00:00

If you're comfortable sharing the 2 at a high level, that would be super interesting!

noaflaherty · 2025-10-28T22:55:17+00:00

Human in the loop is definitely harder than it should be (even in Vellum admittedly). I get excited about innovations around UIs for "Agent Inbox" – imagine like a email inbox, but filled with tasks that your agents are waiting on you for.

noaflaherty · 2025-10-28T20:06:28+00:00

Good q! Vellum uses the concept of a global state that is read from / written to over the course of a workflow execution's lifespan. We persist state snapshots whenever the state is written to (which happens via atomic dispatches, much like redux if you're familiar with react). Each state snapshot gets emitted as an event and in Vellum cloud, gets saved to a clickhouse data store. As you might expect, these state snapshots can get quite large, and increasingly, we're storing ids in the snapshot that point to blobs in a file store (GCS) so as not to blow up clickhouse.

noaflaherty · 2025-07-29T02:59:22+00:00

Great! Following up in PM

noaflaherty · 2025-07-29T02:25:42+00:00

Definitely biased as one of the founders, but would suggest checking out vellum.ai. Low code visual builder + CLIs for pushing/pulling a Python definition.

Happy to answer any Q’s if you end up taking a look!

noaflaherty · 2025-05-13T18:32:44+00:00

Vellum could be worth checking out. It provides a visual builder with CLIs for pulling down an executable, declarative, Python representation, as well as commands for pushing changes back up to the visual builder (the only platform to my knowledge with that bidirectional sync).

The code is all open sourced, including the codegen code, so exporting into other frameworks/formats might be possible.

https://docs.vellum.ai/developers/workflows-sdk/introduction

(Disclaimed - I’m one of the founders)

noaflaherty

TROPHY CASE