Lore

AI Dev Tool Taxonomy

Overview

A three-way split of AI development tools by what stage of work they're for:

Matching the tool to the stage matters: chat apps for the Specification-Driven Development phase, coding assistants for implementation. Reaching for a coding assistant to do spec work (or vice versa) is a common source of the ambiguity that produces Vibe Coding.

Loop and Sub-Agent Support Vary by Engine

Loop and Sub-Agent Support Vary by Engine

Native support for the same capability differs across engines: Claude Code's Loop feature (see Loop Engineering) has no stated equivalent in Codex, per the presenter, and Codex auto-reads AGENTS.md while Claude Code does not (see Context Engineering). Sub-agent launching, by contrast, is reported as supported by Codex, Claude Code, and likely other engines (see Graph Engineering).

Speculated Model Self-Interest

The presenter speculates, as his own suspicion rather than a verified claim, that an Anthropic model (Claude) may have downplayed a competing OpenAI model's currency during a tech-stack recommendation: "GPT-4o was released like 2 years ago, so I think it's kind of lying." Flagged explicitly as unverified — presented alongside the more solidly evidenced point that knowledge-cutoff staleness in general is a recurring failure mode (see Context Engineering).

Organic Tool Specialization by Task Type

At Sendbird, choice between Claude Code and Codex correlates with task type rather than top-down assignment: Codex skews toward engineers maintaining legacy/complex code (e.g., their 300M+ MAU chat infrastructure), while Claude Code skews toward people rapidly shipping new product/roadmap features. This is an organic, bottom-up specialization pattern that emerged from usage rather than being mandated.

Reforge Build

Reforge Build is an AI prototyping tool aimed at teams building on top of an existing product, who already have a design system and product context to integrate against — as opposed to tools aimed at greenfield prototyping. Positioned as the assembly step of Context Engineering: functional, visual, and data context are prepared elsewhere and then fed into Reforge Build to produce customer-realistic prototypes of features on an existing product.