podoman

> Mo is a custom agent harness for catching bugs that builds on the past 3 years of Momentic and millions of test traces from complex, real-world applications. Mo is built for recall: it finds the most real bugs, though Codex is a bit more precise at 86% vs 84%. The tradeoff is cost: Mo costs $2.67 per bug vs $0.80 for Codex, less than Claude Code and Devin.

is this good? so Mo costs more money per bug? I'm confused.

Big fan of all of the items mentioned here. I love the "intuitive split commands" -- I'll add that.

For the vim/nvim fans out there, I try my best to add "vim-style" key bindings for navigating between panes, so that e.g. ctrl-h, ctrl-j, ctrl-k, and ctrl-l can be used to move around qukcly. My dotfiles are here:

https://github.com/jay-khatri/dotfiles/blob/main/.tmux.conf

Have you considered calling this bot "intern bot"? - Jay

Put up a fix, thanks: https://github.com/highlight/highlight/pull/8571

Have heard good things about local. Clickhouse more broadly is an awesome project and they're always on standby to help our eng team team as well.

Highlight.io cofounder here. Thanks for the shout out. Glad to hear you like the product; continue to share feedback as you use it!

We've thought of that briefly. You're essentially asking for some sort of synthetic monitoring right?

Definitely something we're thinking of. If you have any particular requirements, we're all ears.

The difference is that we also expose what the user is interacting with when these traces get fired. Perhaps on mobile your aren't able to view that?

I can confirm shortly, but I believe you don’t actually need those installed locally. That might be a mistake in our docs! Have you tried the docker setup without those tools?

Some additional thoughts. For Shopify store owners, they can definitely install Highlight if they have access to the site that they're hosting (we have some customers in this space!). This can help with optimizing their user experience, etc.. For our tracing SDKs in particular, they would only really work if the shopify developers have their own proprietary code running, however, because this requires application instrumentation.

Updated, thanks: https://github.com/highlight/highlight/pull/7644/files

We collect logs across the stack. Here's some docs on our backend logging integrations (we also have connectors for major cloud providers): https://www.highlight.io/docs/getting-started#for-your-backe...

Are you referring to link [3]? And taking a look at the GitHub issue, thanks for sharing.

Sorry about that. Will relay this to the team. We're mostly a mac shop, but definitely hear you.

We use algora at https://highlight.io and love it:

1. We get OSS contributors incentivized to work on the features that we want to prioritize.

2. It acts as a great hiring funnel.

Congrats on the launch.

As other commenters mentioned, we are both comparable (pending your opinion on the MIT license).

We both charge a cloud saas fee as well:

https://www.hyperdx.io/pricing https://www.highlight.io/pricing

Looks very similar to what we're doing at https://highlight.io. Would love to trade notes at some point.

One thing to consider with your messaging is that when you start speaking to large companies, they won't see you as a datadog alternative. They'll see you as a mix of sentry + fullstory + honeycomb.

Datadog originally found its success with its metrics products, and the larger the buyer of datadog gets, the more metrics-esque use case a company finds. The session replay, logging and other things are simply products that datadog tacks on.

That being said, this is clearly a large market (which is why we're working on it). I particularly like the tracing UI that y'all have and I'd love to chat with your team at some point. Good luck.

(I'm one of the Highlight.io founders). Yep, that's the intention. And anecdotally, it works pretty well, even without fine-tuning.

We started working on this before any of the fine-tuning APIs for OpenAI came out, but we are keeping an eye out for support for fine-tuning on more OSS models. I suspect it would result in better results, especially if it were trained on only exceptions, for example.

We're big users of clickhouse at https://highlight.io. Some more details here if you're interested: https://www.highlight.io/blog/how-we-built-logging-with-clic...

Fwiw, we do the same (https://highlight.io). Heard good things about uptrace as well.

Disclaimer: I'm the founder of an observability company (Highlight.io).

OpenTelemetry has been INCREDIBLY valuable to us. Not only has it made it super fast to build out SDKs for our customers, but the fact that its maintained actively gives us confidence that we're rolling out stable logic to customers' environments.

I agree with the author that OpenTelemetry has succeeded, and its pretty obvious from the fact that most major observability vendors support.

In short, to a developer it may not seem like its particularly valuable because a metrics/logs/traces API is quite simple whether or not you use OTEL. But the fact that this is an industry wide spec is where it becomes powerful.

A few

The reality is that most people don't want to manage their own Clickhouse store, and not all engineers can operate with SQL as efficiently as with code (me included). Nonetheless, this is pretty cool!