<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
  <channel>
    <title>Koda Sidecar Field Notes</title>
    <link>https://kodasidecar.com/blog/</link>
    <description>Practical guides for Fathom workflows, HAR files, browser troubleshooting, support evidence, and technical follow-through.</description>
    <language>en-us</language>
    <lastBuildDate>Sat, 27 Jun 2026 17:00:00 GMT</lastBuildDate>
    <item>
      <title>What is a HAR file? A support engineer&apos;s guide</title>
      <link>https://kodasidecar.com/blog/what-is-a-har-file/</link>
      <guid>https://kodasidecar.com/blog/what-is-a-har-file/</guid>
      <pubDate>Fri, 26 Jun 2026 17:00:00 GMT</pubDate>
      <description>Understand what HAR files contain, why support teams request them, and what to check before sharing one.</description>
    </item>
    <item>
      <title>What can a HAR file expose? Cookies, tokens, payloads, and URLs explained</title>
      <link>https://kodasidecar.com/blog/what-can-a-har-file-expose/</link>
      <guid>https://kodasidecar.com/blog/what-can-a-har-file-expose/</guid>
      <pubDate>Sat, 27 Jun 2026 17:00:00 GMT</pubDate>
      <description>Learn what sensitive data a HAR file can expose, including URLs, cookies, tokens, request bodies, response bodies, and account identifiers.</description>
    </item>
    <item>
      <title>HAR file vs console log: which one should support ask for?</title>
      <link>https://kodasidecar.com/blog/har-file-vs-console-log/</link>
      <guid>https://kodasidecar.com/blog/har-file-vs-console-log/</guid>
      <pubDate>Sat, 27 Jun 2026 17:00:00 GMT</pubDate>
      <description>Understand when support teams should request a HAR file, console log, screenshot, or both for browser troubleshooting.</description>
    </item>
    <item>
      <title>How to sanitize a HAR file before sharing</title>
      <link>https://kodasidecar.com/blog/sanitize-har-file-before-sharing/</link>
      <guid>https://kodasidecar.com/blog/sanitize-har-file-before-sharing/</guid>
      <pubDate>Fri, 26 Jun 2026 17:00:00 GMT</pubDate>
      <description>Learn what to remove from HAR files before sending browser troubleshooting evidence to a vendor or support team.</description>
    </item>
    <item>
      <title>How to redact screenshots before sending them to SaaS support</title>
      <link>https://kodasidecar.com/blog/redact-screenshots-before-saas-support/</link>
      <guid>https://kodasidecar.com/blog/redact-screenshots-before-saas-support/</guid>
      <pubDate>Sat, 27 Jun 2026 17:00:00 GMT</pubDate>
      <description>A practical checklist for safely redacting screenshots before sharing UI errors, browser issues, and support evidence with SaaS vendors.</description>
    </item>
    <item>
      <title>Browser troubleshooting evidence checklist for SaaS support teams</title>
      <link>https://kodasidecar.com/blog/browser-troubleshooting-evidence-checklist/</link>
      <guid>https://kodasidecar.com/blog/browser-troubleshooting-evidence-checklist/</guid>
      <pubDate>Sat, 27 Jun 2026 17:00:00 GMT</pubDate>
      <description>A practical browser troubleshooting evidence checklist for SaaS support teams collecting screenshots, HAR files, console logs, timestamps, and reproduction steps.</description>
    </item>
    <item>
      <title>How to ask customers for logs without creating a data leak</title>
      <link>https://kodasidecar.com/blog/ask-customers-for-logs-without-data-leak/</link>
      <guid>https://kodasidecar.com/blog/ask-customers-for-logs-without-data-leak/</guid>
      <pubDate>Sat, 27 Jun 2026 17:00:00 GMT</pubDate>
      <description>A customer-safe support workflow for requesting logs, HAR files, screenshots, and troubleshooting evidence without overcollecting sensitive data.</description>
    </item>
    <item>
      <title>Chrome DevTools Network tab: a support engineer&apos;s practical guide</title>
      <link>https://kodasidecar.com/blog/chrome-devtools-network-tab-support-guide/</link>
      <guid>https://kodasidecar.com/blog/chrome-devtools-network-tab-support-guide/</guid>
      <pubDate>Sat, 27 Jun 2026 17:00:00 GMT</pubDate>
      <description>A practical support-engineer guide to using the Chrome DevTools Network tab for browser troubleshooting, HAR capture, status codes, timing, and redirects.</description>
    </item>
    <item>
      <title>Is this Chrome extension safe? A practical checklist</title>
      <link>https://kodasidecar.com/blog/chrome-extension-safety-checklist/</link>
      <guid>https://kodasidecar.com/blog/chrome-extension-safety-checklist/</guid>
      <pubDate>Sat, 27 Jun 2026 17:00:00 GMT</pubDate>
      <description>A practical checklist for reviewing Chrome extension permissions, publisher trust, privacy policy language, updates, and data-access red flags.</description>
    </item>
    <item>
      <title>How to turn Fathom meeting notes into follow-up</title>
      <link>https://kodasidecar.com/blog/fathom-meeting-notes-workflow/</link>
      <guid>https://kodasidecar.com/blog/fathom-meeting-notes-workflow/</guid>
      <pubDate>Fri, 26 Jun 2026 17:00:00 GMT</pubDate>
      <description>Turn Fathom notes into reviewed action items, emails, and next steps without losing context after customer calls.</description>
    </item>
    <item>
      <title>Fathom action items checklist: what to review before sending follow-up</title>
      <link>https://kodasidecar.com/blog/fathom-action-items-checklist/</link>
      <guid>https://kodasidecar.com/blog/fathom-action-items-checklist/</guid>
      <pubDate>Sat, 27 Jun 2026 17:00:00 GMT</pubDate>
      <description>A practical checklist for reviewing Fathom action items before sending customer follow-up, updating tickets, or exporting meeting records.</description>
    </item>
    <item>
      <title>How to turn Fathom notes into a customer follow-up email</title>
      <link>https://kodasidecar.com/blog/fathom-notes-to-customer-follow-up-email/</link>
      <guid>https://kodasidecar.com/blog/fathom-notes-to-customer-follow-up-email/</guid>
      <pubDate>Sat, 27 Jun 2026 17:00:00 GMT</pubDate>
      <description>A practical workflow and template for turning Fathom notes into a concise, reviewed customer follow-up email.</description>
    </item>
    <item>
      <title>How to export and organize Fathom notes</title>
      <link>https://kodasidecar.com/blog/export-organize-fathom-notes/</link>
      <guid>https://kodasidecar.com/blog/export-organize-fathom-notes/</guid>
      <pubDate>Fri, 26 Jun 2026 17:00:00 GMT</pubDate>
      <description>A practical workflow for exporting Fathom transcripts, summaries, highlights, and action items into usable records.</description>
    </item>
    <item>
      <title>Fathom API key safety: what teams should know before exporting meetings</title>
      <link>https://kodasidecar.com/blog/fathom-api-key-safety/</link>
      <guid>https://kodasidecar.com/blog/fathom-api-key-safety/</guid>
      <pubDate>Sat, 27 Jun 2026 17:00:00 GMT</pubDate>
      <description>A practical guide to Fathom API key safety, access scope, storage, rotation, and meeting export workflows.</description>
    </item>
    <item>
      <title>How to safely collect a HAR file in Chrome</title>
      <link>https://kodasidecar.com/blog/safely-collect-har-file-chrome/</link>
      <guid>https://kodasidecar.com/blog/safely-collect-har-file-chrome/</guid>
      <pubDate>Fri, 26 Jun 2026 17:00:00 GMT</pubDate>
      <description>Step-by-step guidance for capturing a useful HAR file while reducing privacy and troubleshooting mistakes.</description>
    </item>
    <item>
      <title>How to turn Fathom transcripts into action items</title>
      <link>https://kodasidecar.com/blog/fathom-transcripts-to-action-items/</link>
      <guid>https://kodasidecar.com/blog/fathom-transcripts-to-action-items/</guid>
      <pubDate>Fri, 26 Jun 2026 17:00:00 GMT</pubDate>
      <description>Learn how technical teams can review Fathom transcripts and convert messy meeting output into owned next steps.</description>
    </item>
    <item>
      <title>10 common HAR file mistakes support teams see</title>
      <link>https://kodasidecar.com/blog/common-har-file-mistakes/</link>
      <guid>https://kodasidecar.com/blog/common-har-file-mistakes/</guid>
      <pubDate>Fri, 26 Jun 2026 17:00:00 GMT</pubDate>
      <description>Avoid incomplete captures, missing auth context, oversized files, and unsafe sharing when collecting HAR evidence.</description>
    </item>
    <item>
      <title>How to turn Fathom notes into tickets, docs, and checklists</title>
      <link>https://kodasidecar.com/blog/fathom-notes-to-tickets-docs-checklists/</link>
      <guid>https://kodasidecar.com/blog/fathom-notes-to-tickets-docs-checklists/</guid>
      <pubDate>Fri, 26 Jun 2026 17:00:00 GMT</pubDate>
      <description>A support-engineer workflow for turning Fathom meeting notes into tickets, docs, checklists, and customer follow-up.</description>
    </item>
    <item>
      <title>How to build a customer-safe HAR collection workflow</title>
      <link>https://kodasidecar.com/blog/customer-safe-har-collection-workflow/</link>
      <guid>https://kodasidecar.com/blog/customer-safe-har-collection-workflow/</guid>
      <pubDate>Fri, 26 Jun 2026 17:00:00 GMT</pubDate>
      <description>A repeatable SaaS support workflow for asking customers for HAR files without creating unnecessary data risk.</description>
    </item>
    <item>
      <title>How technical teams should use Fathom for follow-up</title>
      <link>https://kodasidecar.com/blog/fathom-follow-up-technical-teams/</link>
      <guid>https://kodasidecar.com/blog/fathom-follow-up-technical-teams/</guid>
      <pubDate>Fri, 26 Jun 2026 17:00:00 GMT</pubDate>
      <description>Practical Fathom workflows for support, sales engineering, customer success, and implementation teams.</description>
    </item>
    <item>
      <title>What Manifest V3 means for privacy-conscious Chrome apps</title>
      <link>https://kodasidecar.com/blog/manifest-v3-privacy-conscious-chrome-apps/</link>
      <guid>https://kodasidecar.com/blog/manifest-v3-privacy-conscious-chrome-apps/</guid>
      <pubDate>Sat, 27 Jun 2026 17:00:00 GMT</pubDate>
      <description>A plain-English guide to how Manifest V3 affects Chrome app permissions, background behavior, data access, and privacy expectations.</description>
    </item>
    <item>
      <title>Local-first Chrome apps: what it means and why it matters</title>
      <link>https://kodasidecar.com/blog/local-first-chrome-apps/</link>
      <guid>https://kodasidecar.com/blog/local-first-chrome-apps/</guid>
      <pubDate>Sat, 27 Jun 2026 17:00:00 GMT</pubDate>
      <description>A practical explanation of local-first Chrome apps, browser-based processing, privacy tradeoffs, permissions, exports, and when server-side processing is still needed.</description>
    </item>
  </channel>
</rss>
