Is your plan to open-source this or open-source its core in the future?

It's a good question, one that we are discussing a bunch.

We are planning to first open-source our Rust UI framework, and then parts and potentially all of our client codebase. The server portion of Warp will remain closed-source for now.

You can see how we’re thinking about open source here: https://github.com/warpdotdev/Warp/discussions/400 TLDR;

As a side note, we are open sourcing our extension points as we go. The community has already been contributing new themes [https://github.com/warpdotdev/themes]. And we’ve just opened a repository for the community to contribute common useful commands. [https://github.com/warpdotdev/workflows]

Is your framework well-integrated with accessibility tools on Mac OS? If so, will you continue to integrate with those tools on other platforms?

We are actively working on a11y! It's still a work-in-progress, but the goal is to a) make Warp the most accessible terminal there is and b) make a11y be an integrated part of the UI framework, so creating accessible apps in rust would be a no-brainer for future users of our framework.

And yes - once we go cross-platform, we will work on the a11y support there too.

Glad to hear it! I'm working on a Rust GUI accessibility library that might interest you:

https://github.com/AccessKit/accesskit

If you'd like to email me so we can compare implementation approaches and perhaps avoid duplicated effort, my email address is in my HN profile.