<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>AWF — AI Workflow Framework CLI</title><link>https://awf-project.ai/cli/</link><description>Recent content on AWF — AI Workflow Framework CLI</description><generator>Hugo</generator><language>en</language><copyright>Copyright (c) 2025-2026 AWF Project</copyright><lastBuildDate>Sun, 05 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://awf-project.ai/cli/index.xml" rel="self" type="application/rss+xml"/><item><title>New release! v0.6.0 brings workflow packs to the AWF ecosystem</title><link>https://awf-project.ai/cli/blog/new-release-v0.6.0-brings-workflow-packs-to-the-awf-ecosystem/</link><pubDate>Sun, 05 Apr 2026 00:00:00 +0000</pubDate><guid>https://awf-project.ai/cli/blog/new-release-v0.6.0-brings-workflow-packs-to-the-awf-ecosystem/</guid><description>&lt;p>Last week was a blast! I had many great discussions about AWF and AI in general at Symfony Live.
These conversations convinced me that the AWF ecosystem definitely needs a way to share workflows.&lt;/p></description></item><item><title>AWF Plugin improvements</title><link>https://awf-project.ai/cli/blog/awf-plugin-improvements/</link><pubDate>Mon, 30 Mar 2026 00:00:00 +0000</pubDate><guid>https://awf-project.ai/cli/blog/awf-plugin-improvements/</guid><description>&lt;h2 id="key-improvements-in-this-release">Key improvements in this release&lt;/h2>
&lt;p>Since the last release, I’ve been working on enhancing the plugin ecosystem, and I’m excited to announce that &lt;strong>

&lt;a class="link link--text" href="https://github.com/awf-project/cli" rel="external">v0.5.0&lt;/a>&lt;/strong> is now live!&lt;/p></description></item><item><title>AWF Is Live</title><link>https://awf-project.ai/cli/blog/awf-is-live/</link><pubDate>Sat, 21 Mar 2026 00:00:00 +0000</pubDate><guid>https://awf-project.ai/cli/blog/awf-is-live/</guid><description>&lt;p>This has been a major week: AWF is now officially released.&lt;/p>
&lt;h2 id="from-building-to-shipping">From &amp;ldquo;Building&amp;rdquo; to &amp;ldquo;Shipping&amp;rdquo;&lt;/h2>
&lt;p>Over the past two weeks, I focused on minor tweaks and bug fixes discovered while using devcontainers for my AI projects, rather than adding new features.
I also wrote a 

&lt;a class="link link--text" href="https://alex.balmes.co/fr/blog/l-ia-au-service-de-l-industrialisation-passer-de-30-de-reussite-a-100-de-fiabilite" rel="external">blog post (in French)&lt;/a> about determinism in AI, which I plan to translate into English as soon as possible.&lt;/p></description></item><item><title>Introducing AWF</title><link>https://awf-project.ai/cli/blog/introducing-awf/</link><pubDate>Sat, 14 Mar 2026 00:00:00 +0000</pubDate><guid>https://awf-project.ai/cli/blog/introducing-awf/</guid><description>&lt;p>For the past few months, I&amp;rsquo;ve been working on a side project called AWF (AI Workflow Framework).
The code for the main CLI tool is now 

&lt;a class="link link--text" href="https://github.com/awf-project/cli" rel="external">available on GitHub&lt;/a> for everyone — including a dedicated 

&lt;a class="link link--text" href="https://github.com/awf-project/awf-marketplace" rel="external">Claude skill&lt;/a>.&lt;/p></description></item><item><title>Page not found</title><link>https://awf-project.ai/cli/404/</link><pubDate>Tue, 17 Feb 2026 13:06:19 +0100</pubDate><guid>https://awf-project.ai/cli/404/</guid><description>&lt;p>Sorry, we can&amp;rsquo;t find the page you&amp;rsquo;re looking for.&lt;/p>
&lt;p>Use the navigation above or go back to the 

&lt;a class="link link--text" href="https://awf-project.ai/cli/">homepage&lt;/a>.&lt;/p></description></item><item><title/><link>https://awf-project.ai/cli/docs/adr/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://awf-project.ai/cli/docs/adr/</guid><description>&lt;h1 id="architecture-decision-records">Architecture Decision Records&lt;/h1>
&lt;p>This directory contains the Architecture Decision Records (ADRs) for this project.&lt;/p>
&lt;h2 id="format">Format&lt;/h2>
&lt;p>Each ADR follows this structure:&lt;/p></description></item><item><title>001: Hexagonal Architecture</title><link>https://awf-project.ai/cli/docs/adr/001-hexagonal-architecture/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://awf-project.ai/cli/docs/adr/001-hexagonal-architecture/</guid><description>&lt;p>&lt;strong>Status&lt;/strong>: Accepted
&lt;strong>Date&lt;/strong>: 2025-12-01
&lt;strong>Supersedes&lt;/strong>: N/A
&lt;strong>Superseded by&lt;/strong>: N/A&lt;/p>
&lt;h2 id="context">Context&lt;/h2>
&lt;p>AWF is a CLI tool that orchestrates AI agents through YAML workflows. The core domain (workflows, state machines, execution context) must remain independent from delivery mechanisms (CLI today, API/MQ future) and infrastructure choices (YAML parsing, JSON state store, shell execution).&lt;/p></description></item><item><title>002: Error Taxonomy with Exit Codes</title><link>https://awf-project.ai/cli/docs/adr/002-error-taxonomy-with-exit-codes/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://awf-project.ai/cli/docs/adr/002-error-taxonomy-with-exit-codes/</guid><description>&lt;p>&lt;strong>Status&lt;/strong>: Accepted
&lt;strong>Date&lt;/strong>: 2025-12-01
&lt;strong>Supersedes&lt;/strong>: N/A
&lt;strong>Superseded by&lt;/strong>: N/A&lt;/p>
&lt;h2 id="context">Context&lt;/h2>
&lt;p>AWF is a CLI tool used in scripts and CI pipelines. Consumers need to programmatically distinguish error categories to decide retry strategy, user messaging, and escalation. A single non-zero exit code forces callers to parse stderr text, which is fragile and locale-dependent.&lt;/p></description></item><item><title>003: YAML State Machine for Workflow Definition</title><link>https://awf-project.ai/cli/docs/adr/003-yaml-state-machine-for-workflow-definition/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://awf-project.ai/cli/docs/adr/003-yaml-state-machine-for-workflow-definition/</guid><description>&lt;p>&lt;strong>Status&lt;/strong>: Accepted
&lt;strong>Date&lt;/strong>: 2025-12-01
&lt;strong>Supersedes&lt;/strong>: N/A
&lt;strong>Superseded by&lt;/strong>: N/A&lt;/p>
&lt;h2 id="context">Context&lt;/h2>
&lt;p>AWF needs a way for users to define multi-step workflows that orchestrate AI agents and shell commands. The definition format must be human-readable, version-controllable, and expressive enough to handle branching, parallelism, retries, and loops — without requiring programming knowledge.&lt;/p></description></item><item><title>004: Domain Operation Registry with Infrastructure Coexistence</title><link>https://awf-project.ai/cli/docs/adr/004-domain-operation-registry-with-infrastructure-coexistence/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://awf-project.ai/cli/docs/adr/004-domain-operation-registry-with-infrastructure-coexistence/</guid><description>&lt;p>&lt;strong>Status&lt;/strong>: Accepted
&lt;strong>Date&lt;/strong>: 2025-12-01
&lt;strong>Supersedes&lt;/strong>: N/A
&lt;strong>Superseded by&lt;/strong>: N/A&lt;/p>
&lt;h2 id="context">Context&lt;/h2>
&lt;p>AWF supports plugin operations (GitHub, notifications, HTTP) that extend workflow capabilities. Operations need registration, discovery, and execution. The question is where the registry lives: domain (pure, testable) or infrastructure (concrete, direct access to adapters).&lt;/p></description></item></channel></rss>