Skip to main content
Navigation

Settings

The Settings popover lets you customize TagDragon’s behavior to match your debugging workflow. Access it via the ⚙ (gear) button in the toolbar.

Opening Settings

Click the ⚙ Settings button in the second row of the toolbar. The settings popover opens with all configuration options organized into sections.

Performance

Max Requests Limit

Set the maximum number of requests stored in memory.

  • Default: 500
  • Range: 100–5000
  • Effect: When the limit is reached, new requests replace the oldest ones (regardless of auto-prune setting)

Auto-Prune Toggle

Enable or disable automatic pruning of old requests.

  • Default: Enabled
  • How it works: When enabled and the request count exceeds the threshold, the oldest requests are removed
  • Threshold: Same as the max requests limit
  • Memory management: Essential for high-traffic sites where thousands of requests can accumulate

When both max requests and auto-prune are active, they work together: auto-prune removes old requests before the hard limit is reached, keeping the list manageable.

Display

Default Detail Tab

Choose which tab opens by default when you click a request in the list.

  • Decoded (default) — Human-readable parameters grouped by category
  • Query — Raw URL query string parameters
  • POST — POST body data
  • Headers — Request and response HTTP headers
  • Response — Response body content

Choose based on your primary debugging focus. Most users should keep Decoded as default and switch tabs when needed.

Timestamp Format

Control how timestamps are displayed in the request list.

  • Absolute — Full date and time (e.g., 2025-07-28 14:32:05)
  • Relative — Time ago format (e.g., 2m ago, just now)
  • Elapsed — Time since the first captured request (e.g., +0:32)

When to use which:

  • Absolute — For session recording and documentation
  • Relative — For real-time debugging, seeing how recent events are
  • Elapsed — For tracing the chronological sequence of events during a session

Compact Rows

Toggle between normal and compact row height in the request list.

  • Normal — Standard spacing, comfortable to read
  • Compact — Reduced padding, more requests visible on screen

Also accessible via the Compact button in the toolbar.

Behavior

Sort Order

Set the default sort order for the request list.

  • Newest first — Most recent requests at top (default)
  • Oldest first — First captured requests at top

Also accessible via the Sort button in the toolbar. The setting persists across sessions.

Wrap Values

Enable or disable line wrapping for long parameter values.

  • On — Long values wrap to multiple lines
  • Off — Values truncated with horizontal scroll (default)

Also accessible via the Wrap button in the toolbar. Enable when you frequently need to read full URLs or JSON strings.

Auto-Expand

Automatically expand all parameter categories when selecting a request.

  • On — All categories in the Decoded tab are expanded immediately
  • Off — Only the first category is expanded (default)

Also accessible via the Auto-expand button in the toolbar. Enable for audits where you need to see everything at once.

Export

Default Export Format

Choose the default format when exporting captured requests.

  • JSON — Structured data, best for programmatic processing and sharing
  • CSV — Tabular format, best for opening in spreadsheets

See Exporting Data for details on the export feature.

Reset Filters

The Reset Filters button clears all active filters (text search, event type, method, status code, user ID).

  • Does NOT reset hidden providers — those are managed in the Provider Filter
  • Does NOT reset settings — only runtime filters are cleared
  • Useful when you’ve been filtering and want to start fresh

Persistence

All settings are stored in chrome.storage.local:

  • Persistent across sessions — Settings survive browser restarts and DevTools close/reopen
  • Global scope — Settings apply to all tabs and all DevTools instances
  • Not per-tab — If you change a setting in one tab, it affects all tabs

Tips & Best Practices

  • Set default tab to match your workflow — If you primarily debug POST requests, set POST as the default tab
  • Use auto-prune on heavy sites — Enable auto-prune and set a reasonable limit (300–500) to prevent memory issues
  • Elapsed timestamps for session debugging — Switch to elapsed format when tracing event sequences during a specific user interaction
  • Compact mode for high-traffic pages — Enable compact rows when debugging sites with many tracking providers
  • Reset filters between test scenarios — Click Reset Filters before each new test to ensure a clean state

Was this page helpful?

Start typing to search docs...