December 10, 2025
Collaborate on traces with your team
Comments are now on neatlogs. Pin context directly to any span, highlight what you're referencing, and tag the right person, without leaving the trace.
Updates
- Write detections in codeSeptember 7, 2026
- Review traces with AI evaluatorsJuly 27, 2026
- Replay an agent run step by stepJuly 1, 2026
- See cost, latency, and errors across every runJune 16, 2026
- Triage in Your EditorMay 29, 2026
- Import Your Traces from LangSmith and BraintrustMay 28, 2026
- Ask your trace data anythingMay 1, 2026
- Keep sensitive data out of your tracesApril 12, 2026
- Version your prompts like codeMarch 5, 2026
- Instrument multi-turn conversationsJanuary 20, 2026
- Collaborate on traces with your teamDecember 10, 2025
- See exactly what your AI agent didNovember 18, 2025
- Catch issues before your users doNovember 5, 2025
- Zero-config observability for every frameworkOctober 22, 2025
Discuss traces where the work happens
Keep feedback attached to the trace instead of scattered across chat messages and issue trackers.
Comment directly on any output, failed tool call, suspicious span, or attribute. Every comment stays attached to the exact part of the trace you're discussing, making it easy to review findings and collaborate without losing context.
Use @mentions to bring teammates into the conversation and reactions to keep discussions organized.
Release notesv0.7.0Leave comments directly on tracesDecember 2025
Debugging context now stays attached to the exact span, output, or tool call your team is reviewing.
- FeaturePin a comment to any span, highlight the specific content you’re referring to, and tag teammates with @mentions when you need another set of eyes
- FeatureComments are team-wide, persist across sessions, and support reactions for quick acknowledgement
- EnhancementDiscuss agent behavior right where it happened instead of moving screenshots into Slack or losing context in side threads