Skip to main content
Software Engineering Daily

Building AI Agents on the Frontend with Sam Bhagwat and Abhi Aiyer

57 min episode · 2 min read
·

Episode

57 min

Read time

2 min

Topics

Artificial Intelligence, Software Development

AI-Generated Summary

Key Takeaways

  • TypeScript-first architecture: Maastra targets JavaScript developers by providing AI agent primitives in TypeScript rather than Python, eliminating language switching overhead and enabling full-stack development with consistent tooling across frontend and backend components.
  • Agent complexity spectrum: Agentic behavior exists on a spectrum from single LLM calls with tools to multi-agent networks. Agents struggle with more than 8-10 tools simultaneously, requiring workflow orchestration to group tools into manageable categories for reliable execution.
  • Workflow determinism pattern: Engineers often know the exact steps needed for complex tasks. Maastra workflows let developers write deterministic code paths while using LLMs only at specific execution points, avoiding unreliable model-driven orchestration for predictable processes.
  • MCP integration strategy: Model Context Protocol servers function as decentralized integration hubs, allowing Maastra agents to access third-party tools written in any language. This eliminates manual integration work while expanding agent capabilities through community-built MCP servers.

What It Covers

Sam Bhagwat and Abhi Aiyer discuss Maastra, an open-source TypeScript framework for building AI agents with primitives like workflows, tools, and RAG, addressing the gap in frontend-focused AI development tooling.

Key Questions Answered

  • TypeScript-first architecture: Maastra targets JavaScript developers by providing AI agent primitives in TypeScript rather than Python, eliminating language switching overhead and enabling full-stack development with consistent tooling across frontend and backend components.
  • Agent complexity spectrum: Agentic behavior exists on a spectrum from single LLM calls with tools to multi-agent networks. Agents struggle with more than 8-10 tools simultaneously, requiring workflow orchestration to group tools into manageable categories for reliable execution.
  • Workflow determinism pattern: Engineers often know the exact steps needed for complex tasks. Maastra workflows let developers write deterministic code paths while using LLMs only at specific execution points, avoiding unreliable model-driven orchestration for predictable processes.
  • MCP integration strategy: Model Context Protocol servers function as decentralized integration hubs, allowing Maastra agents to access third-party tools written in any language. This eliminates manual integration work while expanding agent capabilities through community-built MCP servers.

Notable Moment

The team initially built Maastra with a GUI-first approach in October 2024. After respected developers responded with polite disinterest, they completely rebuilt it as code-first within weeks, keeping only the playground visualization component.

Know someone who'd find this useful?

You just read a 3-minute summary of a 54-minute episode.

Get Software Engineering Daily summarized like this every Monday — plus up to 2 more podcasts, free.

Pick Your Podcasts — Free

Keep Reading

More from Software Engineering Daily

We summarize every new episode. Want them in your inbox?

Similar Episodes

Related episodes from other podcasts

Explore Related Topics

This podcast is featured in Best Cybersecurity Podcasts (2026) — ranked and reviewed with AI summaries.

Read this week's AI & Machine Learning Podcast Insights — cross-podcast analysis updated weekly.

You're clearly into Software Engineering Daily.

Every Monday, we deliver AI summaries of the latest episodes from Software Engineering Daily and 192+ other podcasts. Free for up to 3 shows.

Start My Monday Digest

No credit card · Unsubscribe anytime