Skip to main content
The Domains page provides a centralized view of all domains visited during agent sessions, with tools to configure access controls and review domain-specific activity.

​
Overview

For each domain, you can:
  • View the number of sessions that visited the domain
  • See when the domain was last accessed
  • Configure blocking rules (visit/exit restrictions)
  • Expand to view all sessions for that domain
  • Review screenshots from domain sessions
Domains are automatically extracted from session URLs. The page groups sessions by hostname.

​
Domain Table

The main table displays all unique domains sorted by most recent activity.

​
Table Columns

ColumnDescription
DomainHostname (e.g., github.com, anthropic.com)
SessionsNumber of sessions that visited this domain
Last SessionTimestamp of the most recent session
BlockDropdown to configure blocking rules
ActionsExpand/collapse button to view sessions

​
Blocking Rules

ContextFort supports four blocking modes for each domain:

​
None (Allowed)

Badge: Green “ALLOWED”Behavior: No restrictions. Agent can visit and leave the domain freely.Use case: Trusted domains like anthropic.com or github.com

​
Block Visit

Badge: Orange “BLOCK VISIT”Behavior: Agent cannot navigate TO this domain from other sites.Use case: Prevent agent from accessing sensitive internal tools

​
Block Exit

Badge: Blue “BLOCK EXIT”Behavior: Agent cannot navigate away FROM this domain to other sites.Use case: Keep agent contained within a specific domain (e.g., documentation site)

​
Block Both

Badge: Red “BLOCK BOTH”Behavior: Fully blocked. Agent cannot visit or leave the domain.Use case: Completely restrict access to untrusted or dangerous domains
Blocking rules are enforced using Chrome’s declarativeNetRequest API for reliable navigation control.

​
Configuring Blocks

1

Locate the domain

Find the domain in the table. Domains are sorted by most recent session.
2

Open the block dropdown

Click the dropdown in the Block column.
3

Select a blocking mode

Choose:
  • No blocking (green badge)
  • Can’t go TO (orange badge)
  • Can’t leave FROM (blue badge)
  • Fully blocked (red badge)
4

Rules apply immediately

The rule is saved to Chrome storage and sent to the background script for enforcement.

​
Viewing Domain Sessions

Expand a domain to see all sessions that visited it:
1

Click the domain row

Or use the chevron button in the Actions column.
2

Review session cards

Each session shows:
  • Screenshot preview (or placeholder if none)
  • Session status (active/ended)
  • Timestamp of when it started
  • Page title and URL
  • Screenshot count
3

Open a session

Click View Session to jump to the Visibility page for detailed review.

​
Session Cards

When a domain is expanded, you see a grid of session cards:

​
Card Layout

  • Top section: Screenshot preview (or “No Screenshots” placeholder)
  • Badge indicators:
    • Green “active” for ongoing sessions
    • Gray “ended” for completed sessions
    • Screenshot count in top-right corner
  • Bottom section:
    • Session timestamp
    • Page title (truncated)
    • Page URL (truncated)
    • “View Session” button
Session cards are sorted by most recent first within each domain.

​
Empty States

​
No Domains Visited Yet

If you see this message:
  • No agent sessions have been recorded
  • Sessions exist but have invalid URLs
  • Chrome storage was cleared

​
No Screenshots

If a session card shows the placeholder:
  • The session has no captured screenshots
  • This was a brief navigation with no monitored events
  • Screenshots were cleared from storage

​
URL Blocking Rules Storage

Blocking rules are stored as tuples in Chrome storage: 
// Format: [fromDomain, toDomain]
[
  ["", "blocked-domain.com"],     // Block visiting
  ["contained-domain.com", ""],   // Block leaving  
  ["", "fully-blocked.com"],      // Block both (2 rules)
  ["fully-blocked.com", ""]
]
Empty string ("") represents “any domain”. Rules are bidirectional for “Block Both”.

​
Refreshing Data

Click the Refresh button to reload domains and sessions:
  • Data is loaded from chrome.storage.local (keys: sessions, screenshots, urlBlockingRules)
  • Domains are re-grouped and re-sorted
  • Expansion state is preserved

​
Use Cases

​
Domain Allowlisting

Create a safe list:
  1. Review all visited domains
  2. Set “Block Visit” for untrusted domains
  3. Keep trusted domains as “Allowed”

​
Domain Isolation

Keep agent contained:
  1. Set “Block Exit” on the target domain
  2. Agent can work within the domain but can’t navigate away
  3. Useful for scoped tasks (e.g., “work only on docs.example.com”)

​
Domain Audit

Review domain access:
  1. Expand each domain to see all sessions
  2. Check screenshot previews for unexpected behavior
  3. Click “View Session” for detailed investigation

​
Best Practices

1

Start with allowlist

Default to blocking unknown domains, then explicitly allow trusted ones.
2

Use Block Exit sparingly

Only use for containment scenarios. It can prevent legitimate navigation.
3

Review session previews

Always check screenshot previews before deciding to block a domain.
4

Correlate with credentials

If you grant write access to a domain (Credentials page), make sure it’s not blocked here.

​
Technical Details

The Domains page:
  • Loads from chrome.storage.local (keys: sessions, screenshots, urlBlockingRules)
  • Extracts domains using new URL(session.tabUrl).hostname
  • Sends RELOAD_BLOCKING_RULES message to background script when rules change
  • Uses Chrome’s declarativeNetRequest API for enforcement
  • Sessions are deduplicated by ID before grouping

​
Next Steps

Grant Access

Give time-limited write permissions to trusted domains

Review Sessions

See detailed screenshots and events for domain sessions

Build docs developers (and LLMs) love

Get started for freeTalk to us