CARBON — Engineering ConfidenceUser Guide
CHAPTER 06 / 60 Pro

/carbon-browser

Test a live website, local app, preview, page, element, or user flow with the coding agent's installed local browser.

Hassan · CheckoutStart & investigate

When to use it

The answer depends on interacting with a rendered page.

Before you start

Provide a reachable URL and safe test account or fixture. Record the actual clicks, inputs, observed result and browser context. Source inspection alone is not a browser test.

Try this in your coding agent.

/carbon-browser Test the checkout page in my local preview with an empty cart.

Replace sample paths with your project. Slash names are shorthand; your host may use a plugin prefix or a skill picker. Invocation help →

ILLUSTRATIVE WALKTHROUGH

Empty-cart checkout

An expanded teaching example, not a recorded or live execution. The report stays visible while the replay explains how to read it.

  1. 01Read context
  2. 02Investigate
  3. 03Show evidence
  4. 04Report

Coding-agent conversation

Read context

I’m reviewing empty-cart checkout. I’ll keep the scope and permissions explicit.

Investigate

Follow the weakest evidence link and record what remains blocked.

Show evidence

Here is the evidence trail to inspect: Open checkout → remove final item → Continue → empty order preview.

Report

Continue remains enabled after the last item is removed. No real order is submitted.

CARBON

Example report

Illustration
Follow the cart state
Follow the cart state — TestBucks teaching screen

TestBucks course screen with illustrative analysis. The screenshot supplies context; the demo does not establish a newly observed bug.

  1. Cart input
  2. Totals & state
  3. Checkout evidence

Illustrated outcome

Continue remains enabled after the last item is removed.

Evidence to inspect

Open checkout → remove final item → Continue → empty order preview.

Still untested / not established

No real order is submitted.

Ready. Read the full example or play its steps.

What a useful result contains

A bounded claim

For empty-cart checkout, state the target, revision, environment and actual work performed. Keep planned, executed, blocked and untested work separate.

An inspectable trail

Open checkout → remove final item → Continue → empty order preview. In a real run, retain the source, trace, screenshot or fixture behind the conclusion.

The qualification

No real order is submitted.

The next decision

Decide whether the evidence calls for a focused check, a reviewed fix or more context. Do not convert a plausible example into a verified finding.

Adapt the example to your project

  1. Replace empty-cart checkout with a real feature, path or decision in your project.
  2. State the expected rule and its source. Include safe fixtures, constraints and a budget where appropriate.
  3. Ask for exact evidence and remaining gaps. Approve consequential actions separately.
/jay Review the /carbon-browser result. Separate observed evidence, assumptions and untested scope, then recommend the next useful check.

Where to go next

/carbon-ui →/carbon-accessibility →

Content checked against the local command definition: skills/carbon-browser/SKILL.md. Examples adapted from the homepage’s TestBucks walkthroughs. Availability is edition- and host-dependent.