davidvgilmore

Got it. Helpful.

Our roadmap is essentially this: [1] Additional model support (e.g. Gemini 2.5). [2] MCP support. [3] Computer use.

so in the near future we aim to have the top agentic coding models supported

That's fair! We're hoping to make Memex compelling :) thanks for the feedback

We use Haiku for a bunch of small things ... naming a conversation, naming a project (if you don't provide a name), compressing long conversations to manage context window ...

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 is an agentic coding tool at its core, so yes - I'd say it's fair to call it a Claude Code alternative.

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.

named Memex because:

(1) We are fans of the ethos of https://www.theatlantic.com/magazine/archive/1945/07/as-we-m...

(2) We are most excited about helping to accelerate technical progress by making science and engineering more productive. While we are not the same thing as a Memex, it was designed to help improve the productivity of science.

We're planning to open source some components but not the full app.

Today, all of our templates are open source and we plan to keep it that way and grow them over time.

https://github.com/orgs/memextech/repositories

thanks for the feedback. To understand the preference - would you prefer to (1) bring your own keys or (2) use different models?

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 :)

We use Tauri's "sidecar" feature

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

and thanks! we'd love to hear feedback!

Correct - not a VS Code fork. Built it from the ground up with TS+Rust+Python and Tauri