Hi HN,

I’ve been experimenting with LLM agents for a while and often felt that for simple workflows (chat, tool calls, small loops), existing frameworks add a lot of abstraction and boilerplate.

So I built a small Python library called PicoFlow. The goal is simple:

express agent workflows using normal async Python, not framework-specific graphs or chains.

Minimal chat agent

Each step is just an async function, and workflows are composed with >>:

  from picoflow import flow, llm, create_agent

  LLM_URL =
  “llm+openai://api.openai.com/v1/chat/completions?model=gpt-4.1-mini&api_key_env=OPENAI_API_KEY”

  @flow
  async def input_step(ctx):
      return ctx.with_input(input(“You:”))

  agent = create_agent(
      input_step >>
      llm(“Answer the user: {input}”, llm_adapter=LLM_URL)
  )

  agent.run()

No chains, no graphs, no separate prompt/template objects. You can debug by putting breakpoints directly in the async steps.

Control flow is just Python

Loops and branching are written with normal Python logic, not DSL nodes:

  def repeat(step):
      async def run(ctx):
          while not ctx.done:
              ctx = await step.acall(ctx)
              return ctx
          return Flow(run)

The framework only schedules steps; it doesn’t try to own your control flow.

Switching model providers = change the URL

Another design choice: model backends are configured via a single LLM URL.

OpenAI:

  LLM_URL =
  “llm+openai://api.openai.com/v1/chat/completions?model=gpt-4.1-mini&api_key_env=OPENAI_API_KEY”

Switch to another OpenAI-compatible provider (for example SiliconFlow or local gateways):

  LLM_URL =
  “llm+openai://api.siliconflow.cn/v1/chat/completions?model=Qwen/Qwen2.5-7B-Instruct&api_key_env=SILICONFLOW_API_KEY”

The workflow code doesn’t change at all. Only runtime configuration does. This makes A/B testing models and switching providers much cheaper in practice.

When this is useful (and when it’s not)

PicoFlow is probably useful if you:

- want to prototype agents quickly - prefer explicit control flow - don’t want to learn a large framework abstraction

It’s probably not ideal if you:

- rely heavily on prebuilt components and integrations - want a batteries-included orchestration platform

Repo:

https://github.com/the-picoflow/picoflow

This is still early and opinionated. I’d really appreciate feedback on whether this style of “workflow as Python” is useful to others, or if people are solving this in better ways already.

Thanks!

Kb_text_shape: Harfbuzz like single file C/C++ text shaping library

ADSL Works over Wet String

AI Adoption Rates by Country

Managing High Performers

The case against ultrasonic humidifiers

Unidentified Aerial Phenomena Near Nuclear Facilities – Enigma Labs

BookLore: A self-hosted, multi-user digital library

Second Win11 emergency out of band update to address disastrous Patch Tuesday

Inside Anduril's Bolt-M Kamikaze Drone Program

Bluesky CEO Jay Graber: Banning under-16s won't fix social media

Enterprises are eyeing End-To-End AI gateways

Show HN: React-meta-SEO – Rebuilding SEO for React 19 (3KB, no providers)

Shared Garden

Google's AI Detection Tool Can't Decide If Its Own AI Doctored Photo of Activist

Show HN: PicoFlow – a minimal Python workflow for LLM agents

Temporal tissue dynamics from a spatial snapshot

Building a High-Performance Rotating Bloom Filter in Java

David Patterson: Challenges and Research Directions for LLM Inference Hardware

CoCoRaHS – Community Collaborative Rain, Hail and Snow Network

SenseCAP T1000: A Compact LoRaWAN/Meshtastic GNSS Tracker

OpenAI's GPT-5.2 model cites Grokipedia

Show HN: I built a quote search engine via "vibe coding" as a junior dev

Upcoming Relay Transition

Macintosh launched on Jan 24, 1984 and changed the world – eventually (2019)

Google's AI Mode can now tap into Gmail and Photos to tailor responses

mRNA cancer vaccine shows protection at 5-year follow-up, Moderna and Merck say

Fast, reliable Postgres natively integrated with ClickHouse

Vortex Support in DuckDB

SampleBrainz: Browse music samples, curated by the MusicBrainz community

AI/LLM – Research Layers. Why Linear Chats Are Dead (and What's Replacing Them)

Show HN: L3Binance – Market surveillance engine in Rust with integrated ML

Comments