Regarding (2), we haven't supported other models yet because they each come with their own peculiarities regarding system prompting / tool use / etc. By focusing on just Sonnet+Haiku, it's allowed us to focus more time on other features (e.g. checkpointing ...).

Regarding BYOKs - a lot of our beta users didn't actually have keys setup, so it was easier for them to get started without bringing their own keys. The folks that have been interested in BYOKs have mainly wanted to bring their Bedrock/Vertex keys and are interested in enterprise/team features. Hence structuring it this way.

But we're posting here to get feedback and we are willing to make changes :)

https://v1.tauri.app/v1/guides/building/sidecar/

Regarding the GUI focus: we did that so it's more approachable to both tech folks and people not as accustomed to using a terminal (e.g. PMs, sales engineers, etc.). But a lot of our beta users are devs.

Also, when using its agentic search and data viz capabilities, some users prefer to not do that in the terminal.

Sonnet is the real workhorse, though. E.g., for all the thinking and tool use

Thanks and looking forward to any feedback you have! It was definitely a lift+risk to start from scratch instead of forking.

It's not for everyone, but as agentic coding gets better we expect it will become a more common usage pattern.

Looking forward to your feedback!

Mind describing your workflow?

I admit our branding isn't great. But heck - we pivoted twice in 18 months on just a pre-seed and still have half our cash left.

Hopefully we'll be able to grow and afford a better logo later :)

on (1) re: multi tasking ... that's a known UX limitation. You can "command+click" the logo in the top left to open a new window, then just keep the convos open. That's the way to multi-task with it today. We definitely want to clean this up in a future version.

(2) noted - yeah, a global git diff is a good feature request

on (3) in the settings (wrench icon) there's a toggle for "Manual" code execution. To be clear - you also want to be able to approve file edits, not just command execution?

(4) doh - that's a good point

(5) we actually run a shadow git repo that commits on every turn the agent takes. It's aware of your .gitignore too. We only expose checkpoints on user messages right now, but we're planning on doing more on this front.

We like the ethos of peaceful scientific progress.

And we're most passionate about advancing technological progress, which is what the original Memex aimed to do by increasing scientists' productivity.

Our Memex is a small contribution to technological progress, but it's one I am at least proud to make

That clause is only meant to keep people from reselling our app, Memex, itself. But I agree it's super confusingly written and we're going to fix that.

To be 100% clear: we do not prevent anyone from using Memex to build a Memex competitor. That clause was boilerplate our lawyers included, and it doesn't reflect how we operate or what we intend to enforce. I should have caught it and we'll fix it.

On the Usage Data side, your code is never stored anywhere other than your machine when you use Memex. And you can enable "Privacy mode" to not have your prompts stored either.

We've heard loud and clear from the HN community that bringing your own key is important, and we're going to fix that.

Regarding multiple models -- that's next up in the roadmap. We're a small team - we were three and just had two more join recently. So we decided to add checkpoints / shadow git repo before adding multiple model support.

(p.s. sorry this comment got buried!)

We're cooking

To anyone reading this exchange: I wrote the Show HN attempting to be as clear and to the point as possible according to the "Show HN" guidelines. And everything I wrote is factual. It's available for free for you to try yourself on our website.