EdTech Tracker

← Coding lens

agent workflows

architecture judged 89% likely a named technique or architecture

First seen
2024-01-24
Independent sources
16
Articles
54
Last 4 weeks vs prior
0 vs 20

See how it has spread across media tiers

Mentions over time

Articles per week (by publish date) using the term, in any spelling.
07142024-W042026-W152026-W41
Table view
WeekArticlesSources
2024-W0411
2024-W2011
2024-W2511
2024-W5311
2025-W3111
2025-W3611
2025-W4711
2026-W0211
2026-W0311
2026-W0521
2026-W0911
2026-W1011
2026-W1161
2026-W1411
2026-W1511
2026-W1611
2026-W1711
2026-W1822
2026-W2432
2026-W2511
2026-W2911
2026-W3111
2026-W3211
2026-W3411
2026-W3611
2026-W3811
2026-W3933
2026-W40145
2026-W4122

In their words

The Orchestration Problem: Why Cron Breaks for Agents Cron is fine for “run this script at 02:00.” Agent workflows are not that shape.

Model usage is only one cost component of an agent workflow.

Benchmark: https://www.kaggle.com/benchmarks/karmendra8386/cost-per-correct Tooling: tokenecon — my open-source cost accounting for agent workflows · Preprint: https://doi.org/10.5281/zenodo.23195511 A single model call has a predictable price.

In agent workflows, input tokens can add up quickly as more context is carried across multiple model calls.

While developing Susan AI, I get to explore: AI API integration Prompt engineering AI UX Web application architecture Authentication concepts State management API design Error handling AI response streaming File processing Agent workflows Deployment Performance Product design The project is therefore both a product experiment and a learning laboratory .

The goal is to reduce redundant API traffic and lower the risk of hitting provider rate limits as agentic workflows scale.

The danger begins when you apply the same logic to dynamic applications: agent workflows, user‑driven tools, real‑time document processing, and multi‑turn conversations with shifting context.

But when you start building agent workflows across several applications, you end up dealing with many of the same problems repeatedly: permissions, application state, references, dependencies, artifact transfers, and checking what actually happened.