Open source · for Claude Code and Codex
YallaFlow gives your coding agent a reviewed memory of your codebase, a workflow sized to each request, and evidence before anything is called done.
npm install -g yallaflow
Counted from the repository at v1.4.1. From the first commit on 19 Sep 2026 to 1.4.1 on 8 Nov 2026.
The console
yallaflow console opens a local web app in Arabic or English, light or dark. Write requests in your own words, watch each one move to a proven Done, and start your app with one button. These are real screens.
Real work, not a demo
DmagAI is the production studio of the دماغ AI YouTube channel: Egyptian-Arabic videos built with Claude Code, Remotion and ffmpeg, plus the tools around them. Since 21 October 2026, every change in it has gone through YallaFlow. These screens are from that project, unedited.
Two agents, one work item
Claude Code built phase 1 of an expense-approval policy, and 24 tests passed. Codex then got only Continue the work in progress.
It read YallaFlow's records, built the rest and finished with 29 tests and 9/9 acceptance criteria satisfied.
QC that only counts what ran
The agent planned QC from the acceptance criteria and ran it in a real browser. All 9 scenarios passed, including a forged request the server refused, and the agent listed what it did not cover.
Changing your mind is safe
After review, a finished item was reopened with a reason. YallaFlow raised an impact assessment, the requirements were revised first, and the item was re-verified and closed again.
The stories come from a technical showcase recorded inside DmagAI (work item PF-0051). The figures were counted from DmagAI's own YallaFlow records on 8 November 2026.
New in 1.4.1
Running your app is now part of the console. That includes the Docker stack in a parent folder, its database, and its *.localhost sites.
Your agent reads the real configuration (Compose, vhosts, the folders above the project) and proposes services, start order, ports and links. Every item carries its confidence and evidence. Its investigation is read-only and never opens .env.
You see exactly the command, folder and files the trust is bound to, then type the service id. Any later change ends the trust until you review it again.
Setup becomes your Run page. It shows one state, Start and Stop, the apps to open, and a row per service with logs. Services start in dependency order.
Watch
Why a fast coding agent still needs your project's context, and how YallaFlow structures the work around it.
Want the full walkthrough, from setup to delivery? Watch the full demo on LinkedIn (opens in a new tab) 8 min
Why YallaFlow
You describe the intent. YallaFlow keeps the durable state around the agent; the agent does the reasoning and the coding.
A reviewed understanding of your codebase, backed by evidence and flagged when that evidence changes.
Bugs, features and investigations each get a lifecycle sized to the work. Small stays light.
Nothing is done without fresh verification evidence, checked against what was asked.
Every new session and every teammate starts from the approved understanding and recorded progress.
How it works
Day to day you talk to your agent. YallaFlow calls no AI model itself and sends no telemetry.
yallaflow init connects Claude Code and Codex. Existing instruction files are kept.
Ask your agent in plain words. No need to say “use YallaFlow”.
The agent maps the codebase without changing code, shows what it found and missed, and waits for your Approve.
The request gets the right workflow, from a quick fix to a reviewed plan.
Fresh evidence first. What was learned becomes reviewed project knowledge.
After the one-time approval, your original request continues automatically. Read the end-to-end guide.
Capabilities
Core capabilities are always on. Items marked Optional run only when you ask.
First-party setup through each agent's instruction file.
A human-approved baseline that records coverage and limits honestly.
Facts, rules and decisions as files in your repository. Project memory
Resumable lifecycles for bugs, features, changes and more. Workflows
An append-only ledger of the checks that actually ran.
One understanding for the team, through ordinary Git. Shared Projects
Create work, the flow, every item's evidence, and Insights, all in your browser. Console
Agent-proposed services, trusted once, started and stopped from one page. Runtime
Idea, stack, environment and an exact review before anything is created. New project
Import a GitHub, Jira or Azure DevOps ticket as a preserved source.
Browser checks planned from acceptance criteria; passed only if actually run.
You approve the scenarios before anything is recorded. Not test evidence. Tickets, QC and demos
Install and upgrade
Works on a new or an existing repository. Requires Node.js ≥ 20.16.0. Install it as a tool, never as a dependency of your app.
TerminalInstall once, connect each project
$ npm install -g yallaflow
$ cd your-project
$ yallaflow init
$ yallaflow console # optional: open it in your browserStarting fresh? Use All projects → New project in the console instead of init.
PromptThen ask Claude Code or Codex
These are messages to your agent, not terminal commands.
UpgradeWhen a new version is out, you decide when to upgrade
$ npm install -g yallaflow@latest # or an exact version: yallaflow@1.4.1
$ yallaflow upgrade status # read-only: what, if anything, needs attention
$ yallaflow agent refresh # only if the agent contract is reported outdated
$ yallaflow doctorYallaFlow never updates itself. Your work items, project memory and sources are kept as they are. Restart yallaflow console so the browser loads the new version. Updating in detail
Built in the open
Every change to YallaFlow goes through YallaFlow. That means a routed work item, its checkpoints, fresh verification evidence, and a knowledge review before it is called done. The records are public, in the repository's .yallaflow/ folder.
The maker
I built YallaFlow because a fast agent without project context still ships the wrong thing. It is built the way it asks you to work: together with AI coding agents (Claude Code and Codex), with YallaFlow governing every change.
Resources