Open-source AI agent monitoring platform. Latitude automatically detects all the ways your agents fail at scale, and gives your coding agent the tools to fix it.
Replies
Best
being open source for this category is a meaningful trust signal, since teams running agents in production are often sending genuinely sensitive trace data through whatever observability tool they pick. curious whether open source here means fully self-hostable with no dependency on Latitude's own infra, or open source code but the actual product is mainly used as a hosted service, those are pretty different commitments for a team that cares about where their trace data lives
Report
The historical tracking limitation, only capturing sessions forward from installation, is worth flagging more prominently for teams evaluating this. Most agent debugging investigations start with "something went wrong last week, what happened?" If that window predates the install, you're flying blind on the incident that prompted the evaluation in the first place. Have you considered a replay or import mechanism for existing log formats (LangSmith traces, OpenAI logs) so teams can backfill context on historical incidents, even if the clustering analysis only applies going forward?
Replies
being open source for this category is a meaningful trust signal, since teams running agents in production are often sending genuinely sensitive trace data through whatever observability tool they pick. curious whether open source here means fully self-hostable with no dependency on Latitude's own infra, or open source code but the actual product is mainly used as a hosted service, those are pretty different commitments for a team that cares about where their trace data lives
The historical tracking limitation, only capturing sessions forward from installation, is worth flagging more prominently for teams evaluating this. Most agent debugging investigations start with "something went wrong last week, what happened?" If that window predates the install, you're flying blind on the incident that prompted the evaluation in the first place. Have you considered a replay or import mechanism for existing log formats (LangSmith traces, OpenAI logs) so teams can backfill context on historical incidents, even if the clustering analysis only applies going forward?