Why does Warp only support the Mac experience?

Why does Warp require login?

Why does Warp send telemetry events?

Why is Warp not open source yet?

Why is Warp connected to the cloud?

forest trees marked with question marks

Warp, the Rust-based modern terminal, is now in public beta! That means you do not need an invite code anymore!

So, there is an exponential bomb in the GitHub issue list because of the public beta release.

And now, In this article, we answer the top 5 Why of Frequently Asked Questions.

Alright, Let we get into these questions!

Why does Warp only support the Mac experience?

Right now we are Mac only.


The answer is just that every additional platform that we decide to support entails additional engineering overhead, which means that we would not have as much time to build out all those cool features that we want to build.

So we decided to focus on building the best terminal for one single platform, that platform being the Mac.

But the good news is that we plan on adding support for Web, Linux, and Windows, in that order.

Here is the issue that you can subscribe to notifications as we build out support for all of these platforms:


Build Warp for Linux

Build Warp for Windows

Why does Warp require login?

When you download Warp, it asks you to log in with a GitHub account.

We had two main reasons for this.

Number one is that we wanted to build team features in Warp - Things like sharing commands with teammates or running wikis and READMEs directly in the terminal. These things usually require users to have accounts.

Number two is that we wanted to be able to improve our product during beta, which is the stage we are in right now.

By having you log in, we can do things like reach out to you when we investigate crash reports or measure aggregate feature usage.

That way, we can understand which features users are engaging with the most, and therefore which features are worth investing the most time into.

Btw, A lot of people were wondering about this understandably since it’s not something you see in your normal terminal experience.

But we think it’s one of the cooler and more innovative things about Warp that allow us to build out these cool features you don’t see anywhere else(ie our OpenAI feature).

Here is the Issue Discussion: Login required without a reason

Unable to log in ?

check it out:

How to Troubleshooting Login Issues is here :

How to fix the confusing login flow issue is here:

How to fix the proxy issue is here:

Why does Warp send telemetry events?

We send telemetry because it makes it easier to reach out and get feedback when something goes wrong.

However - we only track metadata, NEVER console input or output, and we do not measure your keystrokes.

So for example, if you run git status to see a list of your edited files, Warp would not be able to see your outputted file list or even that you ran git status to begin with.

What we can see is metadata, so things like the fact that you created a block to begin with.

Did you read through our welcome tips?

Did you change your keybindings?

Did you skip our onboarding survey?

These are very generic user actions that tell us HOW you’re interacting with Warp,

But don’t reveal any private information about you as a person.

For an exhaustive list of events that we track, see here: Privacy - Warp Documentation

Why is Warp not open source yet?

It’s been amazing getting these comments because it just shows that people are excited to contribute to our codebase and get involved.

Unfortunately, open sourcing doesn’t happen overnight. it takes time and effort to prepare a codebase to be open source.

For example, we need to provide a development workflow.

What are our design principles?

How is the discussion going to be facilitated?

And are there enough developers who are willing to contribute and add code?

It’s a lot of work But for those of you who are interested, we HAVE open-sourced certain parts of our extension points.

The first one is for contributing new themes, and the second (which we just added recently) allows you to contribute to our Workflows, AKA a list of commonly used commands - which you can access in Warp.

A GitHub Discussion to talk through the pros and cons of the Open Source paths Warp can take: Open sourcing Warp and business model

Why is Warp connected to the cloud?

That is a good question.

And honestly it’s one of the things that excites me most about Warp.

For the individual, it means being able to sync settings across multiple different devices.

So for example, let’s say I had my personal computer where I had my terminal set up with custom keyboard bindings and theming, and then I got a brand new MacBook for work.

Instead of manually setting up my terminal again on that laptop (which could take a long time), Warp would allow me to sync between my personal computer and my work computer which gets the job done a lot more quickly.

For teams, so for more collaborative environments, it means we can build collaborative features.

You could asynchronously share terminal settings or command history with your team.

You also get increased knowledge-sharing because you can run wikis and READMEs directly in the terminal.

Also, you could do things like integrated password-management and audit logging to make the terminal more secure.

We hope this article answers some of your burning questions and helps you understand our viewpoint as a team and a company, both from an engineering and product perspective.

Our goal is to be transparent.

Our goal is to build a quality product.

Our goal is to be awesome.

And for more team behind-the-scenes, educational content, and updates on the product, please subscribe to our Youtube Channel.

If you are still having issues please join this Warp discord channel or open a new Github issue.

Originally published at Embiid’BLOG.