Vertical Agents Are Eating Horizontal Frameworks (May 2026)

Five vertical agent pillars — finance, OSINT, accounting, video, deep research — towering over a flattened horizontal framework grid

Look at GitHub trending today and the read is unmistakable. The number-one mover is TauricResearch/TradingAgents — a multi-agent LLM financial trading framework — putting up +3,315 stars in 24 hours on top of an already-large 64,746-star base. That is the kind of velocity you only see when an HN front-page event collides with a thesis that suddenly clicks. soxoj/maigret, an OSINT username-search tool that scans 3,000+ sites, shipped +1,117. virattt/dexter, a TypeScript autonomous deep-financial-research agent, shipped +446. AIDC-AI/Pixelle-Video shipped +478. vas3k/TaxHacker — a self-hosted AI accounting agent — shipped +106.

What you are not seeing in the top of the chart is what defined 2024 and most of 2025: a horizontal orchestration framework. No LangChain release. No CrewAI surge. No AutoGen burst. The center of gravity has moved.

This is the structural shift today’s convergence report flagged as “vertical agents eat horizontal frameworks” — and Y Combinator just ratified it on video. YC’s “SaaS Challengers” short (May 3) and “Software for Agents” short (May 2) are the recruitment pitch for exactly the companies you see trending: pick a vertical, ship the agent, eat the SaaS. Latent Space went one step further on May 2 — their AI Engineer World’s Fair Wave 2 CFP elevated Vertical AI to a first-class track, alongside Autoresearch, Memory, World Models, Tokenmaxxing, and Agentic Commerce. Twitter shitposts becoming engineering disciplines.

This piece is the directory update. We compare five trending verticals — finance execution (TradingAgents), finance research (Dexter), OSINT (Maigret), accounting (TaxHacker), and video (Pixelle-Video) — on what they automate, where the moat sits, and which horizontal frameworks they are quietly displacing. It also doubles as a teaser for the AgentConn directory entries we are shipping today for each of them.

View original post on X →

Why the Horizontal Era Is Ending

The horizontal-framework thesis from 2023–2024 was elegant: build a generic agent loop, give it tools and memory, and the application of that agent to specific verticals would be left to integrators. LangChain, LlamaIndex, CrewAI, and AutoGen all sold that vision. The implicit promise was that orchestration was the moat.

It wasn’t.

Three forces collapsed the orchestration moat in the last six months:

The loop became a CLI primitive. Codex, Claude Code, Cursor, and the OpenAI Agents SDK 2.0 all ship the while True: agent.step() loop for free. We covered this in detail in the harness substrates piece — when every major coding-agent platform gives you the loop, the loop has no economic value.
Tool calling got standardized. MCP turned tool integration from a per-framework problem into a per-server problem. Once your tools speak MCP, which orchestration framework calls them is irrelevant.
Skill bundles ate prompts. The skills-directory race we covered last week — Mattpocock, Codex, Pi Mono, and the Browserbase skills bundle — means domain expertise now ships as composable plugins, not as bespoke chains.

When loop, tools, and prompts are commodities, what’s left to differentiate? Domain depth. That’s the entire vertical-agent thesis: ship the agent that already knows the workflow, the data sources, the regulatory edges, and the failure modes of one specific job — and let the horizontal framework people fight over plumbing nobody wants to pay for.

💡 The shift in one sentence: When orchestration commoditizes, distribution and domain expertise become the only moats — and verticals are where domain expertise lives.

View original post on X →

The pricing-side evidence is identical. Once heavy power users like Jia-Bin Huang start defecting to whichever model gives them 32M tokens for a quarter, the model layer also commoditizes. The agent’s value migrates upstack — into knowing what to do with those tokens for a specific vertical.

Vertical 1 — TradingAgents: Finance Execution

TauricResearch/TradingAgents is the trending repo of the day. ★64,746 with +3,315 in 24 hours, written in Python. The pitch: a multi-agent LLM framework where each agent plays a specific role on a trading desk — fundamentals analyst, sentiment analyst, technical analyst, risk manager, trader — and the orchestration mimics how a human investment committee actually arrives at a position.

What’s interesting is what they did not do. They did not build on LangChain. They did not build on CrewAI. They built a vertical-specific orchestrator where the role definitions, the data sources (financial APIs, news feeds, filings), and the evaluation harness (backtests, Sharpe, max drawdown) are baked into the framework. The agents inherit a shared mental model of finance that you simply cannot retrofit onto a horizontal scaffold without re-implementing half the business logic.

⚠️ What this displaces: Generic LangChain “ReAct + tools + memory” recipes for financial analysis. Once a TradingAgents-shaped repo exists, anyone trying to wire LangChain into a trading workflow is doing 10x the work for 0.1x the domain depth.

The +3,315/day velocity also tells you something about audience. This is not the orchestration-framework crowd starring it for credibility points. This is buy-side and prop-shop engineers staring at a directly-applicable artifact. Pair it with virattt/dexter below and the financial-services agent surface bifurcates cleanly: execution (TradingAgents) and research (Dexter).

View on Hacker News →

Vertical 2 — Dexter: Finance Research

virattt/dexter is the same vertical’s research half. ★22,537, +446 today, TypeScript. Where TradingAgents wants to act, Dexter wants to understand. It’s an autonomous deep-research agent specifically tuned for financial questions — pulling 10-Ks, parsing earnings calls, building DCF inputs, comparing comps — and surfacing a written investment memo with citations.

The split between Dexter and TradingAgents is not accidental. The financial-services budget bifurcates cleanly: research agents (sell-side analysts, equity research, due diligence) versus execution agents (trading desks, portfolio managers, RIAs). Each side has different latency, accuracy, and audit requirements. A horizontal framework that tries to serve both ends up serving neither.

Dexter is also notable for being TypeScript. Most “research agent” projects are Python — Dexter sits inside the TS-native deep-research tier alongside Vercel’s AI SDK ecosystem and the Cursor SDK we covered last week. That’s a deliberate distribution choice: the people building investor-facing dashboards already live in the TS world.

Vertical 3 — Maigret: OSINT

soxoj/maigret is the OSINT vertical and shipped +1,117 stars today. ★23,561 total. The functional pitch: give it a username, get back accounts on 3,000+ sites with profile metadata, registration dates, photos, and adjacent identifiers. It’s the operational equivalent of every doxxing-resistance and brand-protection workflow that previously required a stack of point tools and a paid Maltego license.

Why is OSINT moving onto GitHub trending in May 2026? Two reasons:

The Reddit thread on Flock’s 80,000-camera ALPR network stalking love interests (1,979 points today, surfaced in our convergence report) is the demand-side fuel. Every individual who reads that thread realizes their own digital surface is exposed.
OSINT is a textbook vertical-agent target. It is a domain where the workflow is well-understood, the data sources are heterogeneous, the rate limits are brutal, and the failure modes (blocked endpoints, captchas, rate limits) require domain-specific recovery code. A LangChain wrapper around 50 site adapters would be a maintenance nightmare. Maigret bakes the recovery loop into the framework.

🔍 What this displaces: Every horizontal “research assistant” agent that thought it could do username pivots as a sub-task. Maigret’s site coverage and rate-limit handling is six years of accumulated domain code. You don’t reproduce that with a system prompt.

Vertical 4 — TaxHacker: Accounting

vas3k/TaxHacker is the long-tail surprise of the day. ★5,490 with +106. Self-hosted AI accounting — the pitch is “LLMs replace QuickBooks, but the data stays on your machine.” Receipt parsing, expense categorization, mileage logs, end-of-year reports, and a UI you can actually run on a Synology.

The +106/day looks small next to TradingAgents’ +3,315, but the meaningful number is the category. Accounting is one of the highest-friction, highest-data-sensitivity verticals in the SaaS map. The fact that a self-hosted, open-source agent is putting up triple-digit days at all means the wedge is open. Every accounting SaaS that priced itself as “we manage your books in our cloud” now has a “you can run this on your own machine for $0” alternative growing in the tail.

This is the YC “SaaS Challengers” thesis in concrete form. The pitch on the YC short is exactly this — pick a SaaS category, build the agent that does the same job for free or self-hosted, distribute via GitHub. TaxHacker is the textbook execution.

Vertical 5 — Pixelle-Video: Creative Production

AIDC-AI/Pixelle-Video rounds out the wave with +478 today, ★9,767. Alibaba’s contribution to the vertical-agent stack is video generation and automation — script → storyboard → scene generation → cuts → audio sync → captioning, all as an agent loop where each step is its own specialized model.

The interesting structural detail here is that Pixelle is a production pipeline as agent rather than a single-shot generator. That distinction matters. A single-shot video model (Sora, Veo, Wan) is a tool. Pixelle is an orchestrator that calls those tools across a multi-step creative workflow — and bakes in the production logic (continuity, pacing, cut rhythm) that a horizontal framework would have no opinion about. That’s the vertical pattern: the agent encodes the craft, not just the model calls.

# The pattern across all five verticals — illustrative, not from any one repo:
class VerticalAgent:
    """
    Horizontal frameworks gave you: loop + tools + memory.
    Vertical agents give you: domain workflow + domain tools +
    domain evaluation harness + domain failure recovery.
    """
    def __init__(self):
        self.workflow = DomainSpecificStateMachine()  # not a generic ReAct loop
        self.tools = CuratedDomainAPIs()              # not "any HTTP endpoint"
        self.evals = DomainBenchmarks()               # backtests / OSINT precision / books-balance check
        self.recovery = DomainFailureModes()          # rate-limit / captcha / regulatory edge handling

That’s the pattern across all five. The vertical agent is the workflow encoded as software.

The Comparison Matrix

Repo	Vertical	Stars (Δ today)	Language	What It Automates	Moat	Displaces
TradingAgents	Finance — execution	64,746 (+3,315)	Python	Multi-role trading committee → position decisions	Role-based orchestration + finance evals	LangChain “ReAct + tools” trading hacks
Dexter	Finance — research	22,537 (+446)	TypeScript	10-K/earnings parsing → investment memo with citations	TS-native + financial-doc parsers	Generic deep-research agents
Maigret	OSINT	23,561 (+1,117)	Python	Username → 3,000+ site profile pivots	6 years of site adapters + rate-limit recovery	Maltego, Sherlock, manual lookups
Pixelle-Video	Creative production	9,767 (+478)	Python	Script → storyboard → scenes → cuts → audio → captions	Production-pipeline orchestration over video models	Single-shot video tools without workflow
TaxHacker	Accounting	5,490 (+106)	TypeScript	Receipts → categorization → reports, self-hosted	Self-hosted + privacy + replaces SaaS pricing	QuickBooks Self-Employed, Wave

📊 The pattern: Each vertical’s moat is something a horizontal framework structurally cannot replicate without becoming a vertical itself. That’s the whole game.

Community Reaction — What Practitioners Are Saying

The community read on this shift is more bifurcated than the GitHub charts suggest. The vertical-agent crowd thinks horizontals are dead. The horizontal-framework crowd thinks verticals are point solutions that will eventually need… a horizontal framework underneath.

View on Reddit →

Both can be right. Read the convergence carefully:

Latent Space (Substack) put it most clearly in their AI Engineer World’s Fair Wave 2 CFP: Vertical AI is now a first-class track. The implicit message — the conference circuit, which is the leading indicator for engineering hiring, has decided this is a discipline. (source)
YC’s editorial line for Summer 2026 — across the “SaaS Challengers” and “Software for Agents” shorts — is locked in: the application-layer SaaS category is the sector to disrupt, and agents are the disruption vector.
Naval’s six-word take — “AIs replace UIs and APIs” — racked up 1.77M views and 8.1K likes for a reason. The thesis people are repeating in their own words is the same one TradingAgents and Maigret are putting on GitHub: the agent is the application now.
The dissent (HN’s morning Phish-vs-agent essay) is worth reading too. The contention there is that auto-complete had more flow state than agent coding. That’s a real cost, not a fake one. Vertical agents that ship as a workflow runner — not a chat box — are the design response.

The AI Engineer YouTube tier (Patrick Debois, Ravi Mehta) is running parallel Context Engineering tutorials this week. Translation: the practitioner skill-up cycle for vertical-agent building is already in motion. By Q3, the supply side of every high-value vertical (finance, accounting, legal, OSINT/security, content production) will be saturated. Move now or watch the wedge close.

Where the AgentConn Directory Lands

We’re shipping directory entries today for all five — TradingAgents, Maigret, Dexter, TaxHacker, Pixelle-Video — under the new Vertical Agents filter. Each entry includes the GitHub-stats overlay, install-method, framework compatibility, and the moat description from this article.

If you’re looking for the broader landscape, the Top 10 AI Coding Agents 2026 directory covers the horizontal-coding side, and the skills-directory race breakdown covers the plugin layer beneath both.

🚀 What to build next. If you are picking a vertical, do not pick one of these five — they are claimed for the next two quarters. Pick the next one. Legal contract review is wide open. Healthcare-coding (CPT/ICD) is wide open. Sales-ops pipeline hygiene is wide open. The pattern transfers: encode the workflow, curate the tools, build the evals, ship the failure-recovery code. The horizontal-framework people will not get there before you.

TL;DR

GitHub trending today is five vertical agents in the top 15. Zero horizontal frameworks.
TradingAgents (+3,315), Maigret (+1,117), Pixelle-Video (+478), Dexter (+446), TaxHacker (+106).
YC’s SaaS Challengers + Latent Space’s Vertical AI track are the discourse-side ratification.
Horizontal moats — loop, tools, prompts — are commoditized. Domain depth is what’s left.
AgentConn is shipping directory entries for all five today under a new Vertical Agents filter.

The horizontal-framework era is not dead — but it’s no longer where the money flows in. Build the agent for X. Ship it.

Sources: GitHub trending data (2026-05-03), convergence report 2026-05-03, Latent Space AIEWF Wave 2 CFP, Y Combinator video shorts (2026-05-02 and 2026-05-03), Reddit r/LocalLLaMA discussion threads, X posts from @naval and @jbhuang0604, and AgentConn editorial coverage of harness substrates.