Onboarding Teardown: What Warp Teaches Us About Activating Developers

Developers are one of the hardest audiences to onboard. They skip tutorials, close pop-ups by reflex, and leave the moment a tool gets in their way. A terminal is an especially tough product to introduce, because every developer already has one they've used for years.

That's why Warp is an interesting case study. It began as a modern, Rust-based terminal. By 2026 it describes itself as an "Agentic Development Environment", where you can type a shell command or ask an AI agent to do the work in plain English. In April 2026 it also open-sourced its client.

Warp has also been unusually open about how it onboards new users. Its blog has an activation write-up, and its weekly changelog shows the team adjusting the onboarding flow throughout 2026. Here are seven lessons from that history that apply to any product, not just developer tools.

1. Use data to find your "aha" moment

In 2022, Warp's growth team watched more than a dozen onboarding sessions and studied their funnel and retention data. They organized the user journey around four stages: sign-up, setup, the "aha" moment and the habit moment. Then they looked for the experience that best predicted whether someone stuck around.

The answer was blocks: Warp groups each command and its output into a unit you can select, copy and share. It was Warp's most distinctive feature, yet most new users didn't understand it, so they never reached the moment that made the product click.

The lesson: Don't guess what your aha moment is. Look at which early actions your retained users have in common, then design onboarding to lead every new user to that action.

2. Don't start new users on an empty screen

The same research found a "blank screen" problem. New users opened the app, saw an empty prompt and had no idea where the value was. A terminal is about as blank as a product gets.

Warp's fix, which it called "Onboarding 2.0", put first-time users on a welcome block instead of an empty prompt. The welcome block was itself an example of the feature they needed to learn. It also pointed to a permanent resource center with a gamified "Getting Started" checklist. That resource center is still part of the product today. A 2026 changelog entry even moved the feedback form into its footer.

The lesson: An empty first screen is a missed chance to teach. Show an example, a starter template or a first step. Then give users a help area they can return to later, because nobody remembers everything from a one-time tour.

3. Let people try the product before you ask for an account

Warp used to require an account before you could use it. That got a lot of pushback from developers, and Warp later dropped the requirement. The installation docs now have a section titled "Log in to Warp (optional)", and the terminal works without an account.

Warp didn't drop accounts completely, though. It ties them to the features that actually need one. AI features require a Warp account, and the 2026 AI setup step offers "Set up later" next to the subscription option. In March 2026, Warp also started showing premium models to free users during onboarding, greyed out with a clear upgrade path, instead of hiding them.

The lesson: Ask for commitment only when it unlocks something. If the core value works without an account, let people reach it first. When you ask later, the value of signing up is obvious.

4. Ask early about choices that change the product

The most interesting addition to Warp's 2026 onboarding is a question about AI autonomy. New users choose how much freedom the agent gets to run commands: Full, Partial or None.

The question works because the answer changes how the product behaves from the first minute. A cautious user gets an agent that asks before it acts. A user who wants speed gets an agent that just works. This is a good fit for an onboarding question.

The changelog also shows how easy it is to get this wrong. In April 2026 Warp shipped a fix because these choices weren't being applied to the default execution profile. Users had answered the question, but the product ignored their answer.

The lesson: Only ask onboarding questions that change the experience, and then make sure the product actually respects the answers. If an answer changes nothing, the question just adds friction.

5. Know when not to show onboarding

A surprising number of Warp's 2026 onboarding updates are about turning onboarding off:

• Shared links: Onboarding should no longer interrupt users who open a workspace from a shared session or an agent conversation link (September 2026).
• Shared transcripts on the web: Unneeded first-time banners and prompts were removed from these pages (August 2026).
• Automation: The agent tutorial no longer runs when Warp is used headlessly through its SDK or CLI (May 2026).

Each of these is a user who arrived with a specific job to do. Someone opening a teammate's shared session wants to see that session, not a welcome tour.

The lesson: Before you start a tour, check how the user got there. Deep links, invitations and automated sessions usually need fewer interruptions, not more.

6. Treat new and existing users differently

When Warp added support for third-party coding agents, existing users saw an "Introducing universal agent support" announcement. New users should have gone through the regular first-run flow instead. A September 2026 fix addressed new users who quit sign-up partway and then saw the existing-user announcement on their next launch.

The fix itself is minor, but the idea behind it matters. Onboarding and feature announcements are different jobs. A new user needs the basics in a sensible order. An existing user needs only what's new, explained in the context of what they already know.

The lesson: Track where each user is in their journey, including people who abandon sign-up halfway, and show each group the right flow.

7. Keep onboarding going after day one

Warp doesn't treat onboarding as a single event. Since early 2026, rotating agent tips appear right under the indicator shown while the agent is working. They teach features at the moment users are already paying attention, instead of all at once on day one.

The changelog also shows how much ongoing work onboarding takes. In 2026 alone there are entries for the new onboarding flow (January), slides cutting off navigation buttons in small windows (March), accounts not being marked as onboarded (April), and a simplified agent onboarding flow (July).

The lesson: Onboarding is a feature you keep improving, not a one-time project. Give it an owner, measure it and expect to change it as your product changes.

One more lesson: protect the setup moment

The 2022 research had one more finding that's easy to miss. Experienced developers were leaving because their existing shell configuration broke the first time they opened Warp. They didn't know why, so they assumed the product was buggy.

No tour can fix that. If the setup step breaks something a user already depends on, they won't stay long enough to see your aha moment.

Applying these lessons to your own product

Most of these lessons come down to showing the right guidance to the right user at the right time. Here's how a few of them look with Intro.js:

const params = new URLSearchParams(window.location.search);
const cameFromSharedLink = params.has("shared");

// Lesson 5: don't interrupt users who arrived with a job to do.
// Lesson 6: only show the first-run tour to genuinely new users.
if (!cameFromSharedLink && user.isNew) {
  introJs.tour()
    .setOptions({
      steps: [
        {
          title: "Welcome 👋",
          intro: "Let's run your first command together.",
        },
        {
          element: "#first-command",
          intro: "Try it here. This is the one thing to learn first.",
        },
      ],
      dontShowAgain: true,
      dontShowAgainCookie: "first-run-tour",
    })
    .onComplete(() => track("onboarding_completed"))
    .onExit(() => track("onboarding_exited"))
    .start();
}

// Lesson 7: keep teaching later with hints next to the features themselves.
introJs.hint().addHints();

Keep the first tour short and focused on your aha moment. Track completions and exits so you know whether it works. Use hints to introduce secondary features over time. For the code behind this in a React app, see our guide on how to add a product tour to a React app.

The bottom line

Warp's onboarding works because it keeps changing along with the product. The team found its aha moment in the data, replaced the blank screen with a first step, made the account optional for the core product, and asked only questions whose answers change the experience. It also learned when to stay out of the way.

None of this requires an AI agent or a Rust terminal. It requires paying attention to how real users arrive, what they need first and when guidance helps them instead of getting in their way.

This article is based on Warp's public blog, documentation and changelog as of November 2026. Intro.js is not affiliated with Warp.