# Google's Ax and Anthropic's Financial Services Are Trending — But Who Solves Long-Running Workflow Resilience? > Source: > Published: 2026-09-24 00:01:56+00:00 Today's GitHub Trending reveals a clear shift: Agent orchestration is moving from "can run" to "can run to completion." Let's look at three repos that tell this story: [`google/ax`](https://github.com/google/ax) brings an open agentic orchestration runtime with Google's engineering backing. The orchestration layer — how Agents are scheduled, how tasks are dispatched — is getting standardized. [`anthropics/financial-services`](https://github.com/anthropics/financial-services) targets the financial industry with agent-based solutions. Financial scenarios are inherently long-running: market monitoring, investment research, risk control — these are multi-step workflows that span hours or even days. [`DeusData/codebase-memory-mcp`](https://github.com/DeusData/codebase-memory-mcp) indexes codebases into a persistent knowledge graph. It solves the "context loss" problem in long-running agent tasks — agents don't have to re-read the entire codebase every time. Here's what I noticed: all three repos solve important problems, but there's a critical gap between them. `google/ax` manages `codebase-memory-mcp` manages `anthropics/financial-services` defines But who manages **workflow state**? Imagine an 18-step financial research workflow. Step 14 fails due to a third-party API timeout. Without state persistence, you restart from step 1. With 18 steps taking hours, that's a full day wasted. The missing piece is **workflow-level checkpoint recovery** — fail at step 14, fix the issue, resume from step 14, not step 1. [`iflytek/astron-agent`](https://github.com/iflytek/astron-agent) is an enterprise-grade agentic workflow platform that solves exactly this: This isn't just "orchestration" — it's **workflow resilience**. The difference between "can run" and "can run to completion." Pair `astron-agent` with [`iflytek/skillhub`](https://github.com/iflytek/skillhub) — a self-hosted skill registry with version management and audit logs — and you get: Every step in a long-running workflow is traceable, recoverable, and auditable. That's what enterprise-grade agent workflows look like. The repos trending today prove that the community recognizes long-running tasks as a real challenge. But most solutions focus on either scheduling (orchestration runtime) or data (persistent memory). The workflow-level resilience layer — checkpoint recovery, state persistence, fault tolerance — is where the real engineering work happens. The next frontier isn't just "agents that can be orchestrated" — it's "agents that can resume from where they left off."