Use GitHub Copilot CLI with a signed-in browser

GitHub Copilot CLI can use agent skills to guide its local terminal work, but GitHub does not document a built-in Tabbit Browser connector. To review a signed-in preview, install Tabbit Browser and its Tabbit CLI skill, then check that Copilot CLI can load the skill and run the local launcher. The site login belongs to the selected Tabbit profile. Copilot’s GitHub sign-in does not provide that website session.

That split is useful when a pull request has a preview only available behind your own login. Let Copilot CLI summarize the diff in the terminal, then use a separate named Tabbit task to inspect the preview. Save a review note for yourself and leave the PR unchanged until you approve the next step.

One r/GithubCopilot user described the CLI opening new terminals while they were working. That is one person’s report, but it points to a useful boundary: give the browser review a named task and keep its result in a separate file. Read the discussion.

Key takeaways

• Copilot CLI is the coding client; Tabbit CLI is the local browser connection. They are separate programs.

• GitHub documents skills under .github/skills, .claude/skills, .agents/skills, ~/.copilot/skills, and ~/.agents/skills. A skill directory contains SKILL.md and may include scripts.

• A visible skill only proves discovery. Check the local launcher and intended Tabbit profile separately.

• Copilot CLI’s shell permission matters because a skill can direct it to run local commands. Review the skill and keep confirmation enabled for commands you have not reviewed.

• Use a named browser task and a named review file. Verify the output and keep edits or submissions behind a human checkpoint.

The pieces at a glance

GitHub distinguishes a skill from a one-off prompt. A skill is a folder with instructions, and it may include scripts or other resources. GitHub also warns that allowing shell or bash without asking removes a confirmation step. Read the Copilot CLI skill guide and the CLI command reference before changing your setup.

1. Check Copilot CLI skill discovery

Use a personal skill if the browser workflow should be available across repositories. GitHub documents ~/.copilot/skills and ~/.agents/skills for personal skills. A project-specific version can live under .github/skills, .claude/skills, or .agents/skills in the repository.

~/.agents/skills/
└── tabbit/
    └── SKILL.md

Tabbit’s CLI quick start explains installation and the installed skill. Restart Copilot CLI after installation, or use /skills reload in an interactive session. Then inspect its skill list or ask Copilot to explain how it will run the named browser task before it does so. To invoke it explicitly, use the registered skill name with a slash. If the installed Tabbit skill is named tabbit, ask: Use the /tabbit skill to inspect this preview. Check it with /skills info tabbit; use the name shown in the list if it differs.

Discovery is only the first check. The skill must still be able to run the local launcher, and the launcher must reach the intended browser.

2. Check the local Tabbit connection

Open Tabbit Browser on the same computer as Copilot CLI. Sign in to the site you need in the intended Tabbit profile. Keep the preview read-only for the first check.

Use Tabbit’s documented launcher path for your operating system. On macOS, the quick start gives this check:

launcher="$HOME/.local/bin/tabbit-cli"
"$launcher" diagnose

Confirm that the expected browser is running before asking Copilot to start a task. If Copilot sees the skill but cannot run the launcher, check its shell approval and local execution environment. A Codespaces or other remote CLI cannot inherit a laptop’s browser profile just because both sessions use the same GitHub account.

These are separate checks:

The existing login is reused only when the task reaches the same Tabbit profile where you signed in. That does not make the website password or cookies available as prompt text. Keep credentials out of prompts and review files.

Before a longer job, use the browser agent first-task checklist to define a small read-only task. If the agent cannot see the signed-in page, compare the local and cloud browser paths and the existing-browser connection options. Tabbit’s Codex setup guide shows the same local launcher boundary for another client.

3. Compare the PR diff with its preview

Use a review that can be checked. First ask Copilot CLI to list the changed routes and the expected visible changes from the diff. Then have it inspect the matching preview through one named Tabbit task. The browser task has its own tabs, so you can continue reading the diff or a different site in your regular browser tabs.

A GitHub Copilot user who helped roll out the CLI at work described an effort to share one skill across several coding clients. Their report notes that skill metadata differed between tools and a namespaced name prevented a skill from loading in their setup. The details are version-specific, but the lesson for this workflow is simple: use the supported skill format and verify it appears in the client. Read the original post.

Try this prompt after you have confirmed the skill and browser target. It asks the agent for a local draft, not a submitted review:

Compare the current pull request diff with the signed-in preview in Tabbit Browser.
Use a new Tabbit task named "pr-482-preview-review". Inspect only the routes changed by this PR.
Do not edit the site, submit a form, post a comment, or merge anything.
Save a local Markdown draft named "pr-482-release-preview-review.md" with:
- route and visible page title
- each changed behavior checked
- a short discrepancy list, with the visible evidence for each item
- items you could not verify
Stop after saving the draft and show me its path for review.

The prompt is an example, not a test result. For an actual PR, replace the PR number and filename, confirm the preview is the correct build, and review the saved note before sharing it. If a page asks for new authentication, shows the wrong workspace, or offers a sensitive action, stop and resolve that with a person.

Use Tabbit when the browser environment is the constraint

Copilot CLI is a local coding client. Tabbit Browser provides the browser context; Tabbit CLI lets an eligible local agent ask that browser to do a task. This is a practical option when the preview login is already in Tabbit or when you want browser work kept in a separate task while you continue coding.

It is not a claim that Copilot CLI has native Tabbit support. The connection depends on the installed Tabbit skill, a reachable local launcher, and the right browser instance. GitHub’s skill documentation says that instructions and scripts can be loaded into a skill, but it does not certify Tabbit as a first-party Copilot integration. See the Tabbit CLI guide, GitHub Copilot browser agent guide, and signed-in session checklist for adjacent workflows.

Choose an integration by where the agent runs

Copilot also has remote steering features, but steering a CLI session from another device is not the same as attaching that session to the browser on your computer. Keep the browser connection and the agent’s own session model distinct.

Decide whether this workflow fits

Use the setup when the browser is already signed in and you need to compare a real page with code changes. It also fits a staging dashboard that has no public preview route, provided the site owner has authorized the review.

Skip the browser step when the same check can be made from a local snapshot, API response, or test. For sensitive production pages, never let a prompt stand in for the site’s own approval controls. Ask Copilot to prepare a checklist, then inspect or submit the changes yourself.

A useful review has an observable handoff: the named task completes, the file exists, and you can see what the agent checked. Do not treat a model’s “done” message as evidence that a page loaded or a PR was changed.

For repeatable browser checks, prefer the agent-browser CLI tutorial when a standalone fixture is enough, or read the broader browser automation overview before choosing a tool.

Secholar.L

Growth & Content at Tabbit

Secholar.L writes hands-on guides about AI browsers and agent workflows, comparing tools with real research and citing verifiable sources.