Marco (@itsperini) header
Marco (@itsperini) profile picture
Joined January 2018
Photo by Marco (@itsperini)Photo by Marco (@itsperini)Photo by Marco (@itsperini)Photo by Marco (@itsperini)Photo by Marco (@itsperini)Photo by Marco (@itsperini)Photo by Marco (@itsperini)Photo by Marco (@itsperini)Photo by Marco (@itsperini)Photo by Marco (@itsperini)
controlling a xArm6 with voice using the @viamrobotics MCP server, gpt-live-1 and @pidotdev harness
57
I had early access to GPT-6. This model will completely shatter your understanding of what's possible, and it will start a new era of creativity. It's hard to explain how big of a jump this is, so I'll share my tests. 1/6 Made this 3D model and animation in code from an image.
360
579
240
10,011
1,710,259
If we could turn Hermes agent into this @NousResearch @Teknium . I think agents are next agi.
21
25
4
356
25,191
Excited to dive into this - an open source agent designed with memory/continual learning in mind
24
46
4
378
76,300
Testing some realtime voice with a live agent identity swap. gpt-realtime-2 @OpenAI works very well also when switching from English to Italian and I used @opendot_ai for the control plane and webrtc connection. Still need some tuning on the audio streaming part
1
3
11
1,177
Marco retweeted
quick one for anyone migrating off Stainless: we shipped a skill that turns your OpenAPI spec into an MCP server, inside codex/claude code/cursor > npx skills add mcp-use/mcp-use/skills/openapi-to-mcp skills.sh/mcp-use/mcp-use/op…
1
1
1
7
542
Sharing the proj built this Saturday at the "AI for the Real World" hackathon in London. We used @OpenAI 's new realtime-gpt-2 audio model, @GoogleDeepMind's Local Gemma 4 and @LangChain's Deepagents harness. Github repo in the comments
1
2
9
572
Building agents requires lots of infrastructure (tracing, datasets, experiments, deployments, etc...) we've launched cmd+K global search in LangSmith for finding resources more easily
1
7
2
20
10,823
agent files agents are just defined by markdown/json files now system prompt: agents.md subagents: subagents/ tools: skills.md + mcp.json
46
77
9
813
106,688
We are hiring deployed engineers at @langchain! If you are a software engineer, but want to be in more strategic convos, understand how businesses work, work closely with customers building agents, I want to meet you. Deployed eng at LangChain is ELITE -- absolute animals and good at everything they do. We're hiring in SF, New York and major cities across the US. If you're curious, reach out or apply --langchain.com/careers?ashby_…
30
44
3
487
64,650
Langchain released a feature that clusters agent traces by behaviour patterns. I just ran it on 500 production traces. Here's what it actually does. It's an LLM analyzing your LLM traces. Specifically: 1. Takes your production traces (inputs, outputs, tool calls, intermediate steps) 2. Runs them through clustering based on semantic similarity 3. Uses an LLM-as-judge to categorize and label clusters 4. Generates a hierarchical taxonomy of usage patterns The interesting part is the clustering methodology. From the UI, you can see that it's extracting intent from the full traced context. This is applied across all traces, then similar intents get clustered. Each cluster gets labelled both by pattern type and by quality metrics. What I've found useful here is that each subcategory represents a distinct agent system and context engineering pattern. RAG retrieval, for example, has different failure modes than web scraping, even though both are "information sourcing." The system is essentially discovering that your agent has multiple operational modes, each with different context & user requirements. So now, this means I can fix categories of failures, not just individual bugs. What I really like about Langsmith and their new Insights Agent is the configuration options. You can customize clustering dimensions: - Group by usage patterns: Clusters based on what users are trying to accomplish - Group by poor interactions: Clusters based on failure signatures (user frustration signals, error patterns) - Custom attributes: Define your own dimensions for clustering Some experiments with custom attributes that I'm building now: - context_switches: Number of topic changes mid-conversation - tool_chain_length: Number of tool calls in sequence - retry_rate: How often the agent needs multiple attempts This is a great feature for strategic analysis (daily/weekly reviews). My first impression: the categorization is surprisingly good. Clusters are semantically coherent. The metrics are well-chosen for diagnosing agent issues. Useful for understanding agent behaviour at scale. Much better than manual review because it finds patterns you wouldn't notice in individual traces.
🔎🤖LangSmith Insights Agent Really excited to launch our first in-product agent This agent lives inside LangSmith and combs through traces, giving you insights into: 🧑‍🤝‍🧑how users are using your agent ⁉️how your agent may be messing up 🛃{your custom insight here} The problem we saw was that people were launching agents... and didn't know how their users were actually using them! You put a chat box in front of people, and they may ask it anything - the surface area for agents is often super wide In addition - agents would fail silently. They could give a bad response - this wouldn't show up in error logs, but its good to know. If you know what look for, you can set up LLM as a judge evaluators. But what if you don't? (most people don't initially) The best way to figure this out - as @HamelHusain says - "look at your data". But LLMs are really good at looking at your data! So can they do it for you? This is exactly what insights agent attempts to do. It's live in LangSmith today. You can read more about it here: blog.langchain.com/insights-…
9
21
1
187
23,965
Our new Insights Agent has been extremely helpful in identifying users' usage patterns across our applications. Give it a try!
🔎🤖LangSmith Insights Agent Really excited to launch our first in-product agent This agent lives inside LangSmith and combs through traces, giving you insights into: 🧑‍🤝‍🧑how users are using your agent ⁉️how your agent may be messing up 🛃{your custom insight here} The problem we saw was that people were launching agents... and didn't know how their users were actually using them! You put a chat box in front of people, and they may ask it anything - the surface area for agents is often super wide In addition - agents would fail silently. They could give a bad response - this wouldn't show up in error logs, but its good to know. If you know what look for, you can set up LLM as a judge evaluators. But what if you don't? (most people don't initially) The best way to figure this out - as @HamelHusain says - "look at your data". But LLMs are really good at looking at your data! So can they do it for you? This is exactly what insights agent attempts to do. It's live in LangSmith today. You can read more about it here: blog.langchain.com/insights-…
3
6
2,233
Finally we made it happen!! Germany's first ever LangChain Meetup in Munich!!!!! Amazing folks, inspiring devs everywhere. Loved it. Thanks @amadaecheverria for the support.
2
11
1,622
🥳Announcing LangChain and LangGraph 1.0 LangChain and LangGraph 1.0 versions are now LIVE!!!! For both Python and TypeScript Some exciting highlights: - NEW DOCS!!!! - LangChain Agent: revamped and more flexible with middleware - LangGraph 1.0: we've been really happy with LangGraph and this is our official stamp of approval - Standard content blocks: swap seamlessly between models Read more about it here: blog.langchain.com/langchain… We hope you love it!
43
86
31
572
113,215