the only successful agents are Coding agents and deep research agents(somewhat ) .Agent UX pattern they have in common
1. Response streaming
2. Message Queuing
3. Interruption
4. Slash commands
5. Long running task with parrellel exection
6. Function call with Human approval
@karpathy@NirDiamantAI If you consider your coding agents as a compiler and your prompt as code then there needs to be some deterministic checks for the compiler to ground on. Your coding agent needs to be pure function.
@andrew_r@zeeg people who hate MCP are usually taking about saving tokens/ context window - there is a Token-Interop tradeoff and that should be the conversation
A client asked me to deploy a RAG solution in their Azure cloud. Looking to use microsoft foundary tools. Even got myself a certificate for their course.
https://t.co/IqK5RIc973 #MSLearnBadge
Cursor now uses subagents to complete parts of a task in parallel.
Subagents lead to faster overall execution and better context usage. They also let agents work on longer-running tasks.
Also new: Cursor can generate images, ask clarifying questions, and more.
I’m working around detecting user struggle during onboarding workflows.
The idea is to capture fine-grained client-side interaction signals (form state changes, validation failures, retries, navigation context, timing) and then use an LLM to reason over those traces to infer where and why users are getting stuck.
I’m currently thinking about where this data should be captured and modeled:
raw DOM / browser-level events
or higher-level semantic events (e.g. “attempted submit → validation error”)
From your experience, what’s the right abstraction layer to collect this kind of interaction data so it's useful for downstream reasoning?
Think of it like the game Factorio*. You start by hand-crafting individual items (authorship), but to scale, you have to build an automated factory (orchestration) .You stop caring if you personally "made the gear" and focus on designing the system that ensures the gears are produced correctly at scale.
Even @karpathy says he’s never felt "this behind" as a programmer. If he feels that way, it’s a sign that the very definition of being technical has shifted under our feet . We’re moving from a world of writing code to a world of orchestrating intelligence
@karpathy The most important divide in 2026 isn't "engineer vs. non-engineer" it’s those who can delegate vs. those who can't
Whether you’re a lawyer or a coder, you’re now climbing the same skill tree: orchestrating uncertainty without losing authority