Make a walkthrough with browser handoff
Make a help video that shows a task inside your product. Learn where to sign in, how to give control back to ngram, and what to check before sharing.
Written By Anish Muppalaneni
Last updated 12 days ago
Read before this
When to use Browser Handoff
Use this guide if you write help content for a product that asks customers to sign in. Suppose customers following your GitHub CLI article can find the repository but keep asking how to receive a notification when a new version ships. You want a short walkthrough that starts at the repository, shows the right notification choice, and ends where viewers can check their own setting.
Have the article URL, the product URL and a demo account with access to the task. You’ll use the article for the instructions and the signed-in product for the footage. If you already have a current recording that shows the entire task, you can use that recording as your source.
Watch how Browser Handoff works (MP4). Follow the notification-settings example from the first brief through sign-in and back to ngram. After you choose Done, ngram captures the remaining screens and prepares a plan for you to review.
Step 1. Check the route in a demo account
Open the GitHub CLI repository in your demo account. Open Watch, choose Custom and locate Releases. Note how the setting looks before you change it and how to reopen it afterward. This is the route your viewer will need to recognize. Use an account where changing a notification preference is appropriate.
Check what else the browser might show. A repository picker, notifications menu or account switcher can expose names unrelated to the lesson. Pick a clean starting page and decide which screen the finished walkthrough should open on.
Step 2. Give Studio the task and the product link
From ngram Studio Home, choose Prompt to video. Under Model, choose a model that supports browsing. In Video brief, tell ngram who the tutorial is for and what you want viewers to learn. Add the repository URL and, if available, the help article whose wording the video should follow.

For example: “Make a short Help Center video for people who use GitHub CLI. Show them how to subscribe to new releases at https://github.com/cli/cli and where they can check their selection afterward.” Choose Create video. The project opens and ngram reads the brief before it starts browsing.
If Live browser never appears, check that the project uses a model that supports browsing. Ask ngram to visit the product link and name the task you want to show. If the model cannot browse, start a compatible project or supply a recording.
Step 3. Sign in when Studio hands you the browser
Follow the Live browser panel while ngram visits the site. You can watch without doing anything until Studio displays “You have the browser.” That notice means you can click and type in the displayed website. In the example below, GitHub is asking for sign-in and Studio’s Done button is above it.

Sign in directly on the website and complete any verification there. Keep passwords and codes out of the Studio conversation. If the account cannot access the page, choose I can’t do this and explain which screen you could not reach. You can then supply approved screenshots or a recording from an account with the right access.
Step 4. Give the browser back to ngram
Once you’re signed in and the page where the tutorial should begin is open, click Done at the top of the Live browser panel. ngram takes control again and captures the next steps. You can follow along in the panel.
Step 5. Review the plan before creating the video
When the plan appears in Studio, read the proposed scenes alongside your help article. Check that the viewer sees where Custom opens, which box to choose, and how to apply the selection. If a scene says to watch all repository activity, request a correction in the project before approving.
Review the script and the credit estimate. Choose Approve plan when the sequence matches the task you rehearsed. Studio then produces the video from that plan.
Step 6. Try the finished tutorial as a customer
Play the export beside the written article. Pause at the first instruction and follow it in a separate demo session. Can you get from the repository to Releases without guessing? Apply the selection, then reopen the menu to verify that Releases is selected. Confirm that the narration and visible labels agree.
Check the sign-in transition and any account menus for private details. Trim or replace a scene if it exposes something the viewer does not need. Finally, open the article where a customer will read it and play through the changed setting there before sharing the link.
References and next steps
- Sources and attachments — use existing footage when the product page is unavailable.
- Revise a video — correct a scene after reviewing the export.
- Configure GitHub notifications — check the options GitHub currently offers for an individual repository.
Keep going
- Record the workflow yourself — Upload a recording when browsing cannot reach the intended screens.
- Revise a generated video — Correct a screen, step or line in the same project.
Was this helpful?
More in Start here
What is ngram?Create your first videoContinue an older projectUnderstand the agentic workspaceStill need help? Ask the team