Tool Site Model Status
Category: Site Knowledge · Since: v18.35.0 · Tier: All
Show what CBrowser has learned about a site. Returns navigation graph stats, element reliability scores, known goal paths, and failure patterns.
Parameters
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
| domain | string | Yes | — | Domain to check (e.g., "example.com") |
Examples
What does CBrowser know about example.com?
Show site model stats for our staging site
Response
{
"domain": "example.com",
"navigationNodes": 24,
"navigationEdges": 47,
"trackedElements": 156,
"goalPaths": 5,
"failurePatterns": 3,
"pageFingerprints": 18,
"modelSizeBytes": 42680,
"lastUpdated": "2026-04-11T12:00:00Z",
"oldestData": "2026-03-15T08:30:00Z"
}
How Site Models Work
CBrowser builds a persistent knowledge graph for each domain.
- Navigation Graph -- Which pages link where, via which elements. Updates after every
navigatecall. - Element Reliability -- Success/failure rates for selectors. Updates after every
clickandfill. - Goal Paths -- Action sequences that achieved goals, with success rates per persona.
- Failure Patterns -- What goes wrong, on which pages, and workarounds.
- Page Fingerprints -- Structural snapshots for detecting site changes.
Data decays automatically. Elements unseen for 30 days lose 50% confidence. Entries below 0.1 confidence are pruned. Models cap at 500KB per domain.
Storage
Site models live at ~/.cbrowser/site-models/{domain}.json. They update incrementally via write-coalescing (1-second debounce).
Why This Matters
The second cognitive journey on a site is dramatically better than the first. CBrowser already knows where navigation leads, which elements work, and what paths achieve similar goals.
No competing browser automation tool keeps persistent knowledge between sessions.
Related
site_model_query— Query best path for a goalpage_understand— Real-time page analysissite_profile_status— Browser state persistence- Site Knowledge Tools — Full category docs