# A Song of Types and Agents - Roberto Stagi, Ratel

Source: [YouTube](https://www.youtube.com/watch?v=UlFB6efYN5Q)  
Feed7 permalink: https://feed7.dev/p/a-song-of-types-and-agents-roberto-stagi-ratel-0i7wvpu  
Published: Unknown  
Trust: Source Linked (source_linked)

## Why Included

A TypeScript agent stack can share types and schemas across the loop, tools, backend and UI, reducing service-boundary contracts. Keep Python where training and model serving require it.

## Source Summary

The proposed TypeScript stack keeps the agent loop, tools, backend, schemas and UI in one typed codebase. The talk cites Vercel AI SDK growth from **1.6 million to 15.1 million weekly downloads** in **one year** as evidence of ecosystem activity.

## Practical Implication

For application-layer agents, consider sharing Zod schemas and types end to end before introducing a Python service boundary. Keep Python for training, research and GPU serving when those are actually part of the system.

## Agent-Ready Context

The proposed TypeScript stack keeps the agent loop, tools, backend, schemas and UI in one typed codebase. The talk cites Vercel AI SDK growth from **1.6 million to 15.1 million weekly downloads** in **one year** as evidence of ecosystem activity.

For application-layer agents, consider sharing Zod schemas and types end to end before introducing a Python service boundary. Keep Python for training, research and GPU serving when those are actually part of the system.

The language recommendation is an architectural argument, not a controlled comparison of reliability or agent-generated code quality. A single TypeScript codebase reduces contract synchronization, but it does not automatically make integrations or runtime behavior safer.

## Context Map

- Layer: infra
- Domains: coding
- Topics: agent-sdks, dev-ux, coding-agents

## Uncertainty

- The language recommendation is an architectural argument, not a controlled comparison of reliability or agent-generated code quality. A single TypeScript codebase reduces contract synchronization, but it does not automatically make integrations or runtime behavior safer.

## Agent Instruction

Use this item as source-backed context. Do not invent claims beyond the linked source. If this item conflicts with another source, call out the conflict.