<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
     xmlns:atom="http://www.w3.org/2005/Atom"
     xmlns:dc="http://purl.org/dc/elements/1.1/"
     xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>ClipGate Blog</title>
    <link>https://clipgate.github.io/blog/</link>
    <atom:link href="https://clipgate.github.io/blog/feed.xml" rel="self" type="application/rss+xml" />
    <description>Notes on local-first clipboard workflows, secret hygiene, terminal productivity, and the small ways context gets lost — and recovered — during a developer's day.</description>
    <language>en-us</language>
    <copyright>Copyright 2026 ClipGate</copyright>
    <lastBuildDate>Mon, 27 Apr 2026 10:00:00 +0000</lastBuildDate>
    <pubDate>Mon, 27 Apr 2026 10:00:00 +0000</pubDate>
    <ttl>1440</ttl>
    <generator>ClipGate static site</generator>
    <image>
      <url>https://clipgate.github.io/assets/icons/icon-192.png</url>
      <title>ClipGate Blog</title>
      <link>https://clipgate.github.io/blog/</link>
    </image>

    <item>
      <title>macOS Clipboard History: What Gets Logged, What Leaks, and How to Audit It</title>
      <link>https://clipgate.github.io/blog/macos-clipboard-history-what-leaks/</link>
      <guid isPermaLink="true">https://clipgate.github.io/blog/macos-clipboard-history-what-leaks/</guid>
      <pubDate>Mon, 27 Apr 2026 10:00:00 +0000</pubDate>
      <dc:creator>ClipGate</dc:creator>
      <category>security</category>
      <category>macos</category>
      <category>privacy</category>
      <category>audit</category>
      <description>A 2026 audit of how the macOS pasteboard, Universal Clipboard, and popular clipboard managers actually store your copies — what's logged, what leaks, and a five-step check to find traces of your last password.</description>
      <content:encoded><![CDATA[<p><strong>Your last password copy probably still lives somewhere on disk.</strong> The macOS pasteboard, Universal Clipboard handoff, and popular clipboard managers all keep more state than most users expect. This 2026 audit shows what gets logged, where it leaks, and gives you a five-step check to surface traces still sitting on your machine.</p><p><a href="https://clipgate.github.io/blog/macos-clipboard-history-what-leaks/">Read the full post →</a></p>]]></content:encoded>
    </item>

    <item>
      <title>How to Auto-Save Every Snippet You Copy in Chrome — and Pipe It to Claude or ChatGPT</title>
      <link>https://clipgate.github.io/blog/auto-save-chrome-snippets-for-claude-chatgpt/</link>
      <guid isPermaLink="true">https://clipgate.github.io/blog/auto-save-chrome-snippets-for-claude-chatgpt/</guid>
      <pubDate>Mon, 27 Apr 2026 09:30:00 +0000</pubDate>
      <dc:creator>ClipGate</dc:creator>
      <category>extension</category>
      <category>ai</category>
      <category>workflow</category>
      <category>productivity</category>
      <description>Stop losing research across 30 tabs. Install one Chrome extension that auto-captures every snippet, URL, and code block you copy — then bundle a session into a single block for Claude, ChatGPT, or Cursor.</description>
      <content:encoded><![CDATA[<p><strong>Auto-capture is the productivity unlock most developers never tried.</strong> Stop losing research across 30 tabs. One Chrome extension can record every snippet, URL, and code block you copy, then bundle a whole session into a single, paste-ready block for Claude, ChatGPT, or Cursor — no manual stitching, no lost context.</p><p><a href="https://clipgate.github.io/blog/auto-save-chrome-snippets-for-claude-chatgpt/">Read the full post →</a></p>]]></content:encoded>
    </item>

    <item>
      <title>How to Pipe Terminal Output to Claude Code, Cursor, and Aider — Safely</title>
      <link>https://clipgate.github.io/blog/pipe-terminal-output-to-claude-cursor-aider/</link>
      <guid isPermaLink="true">https://clipgate.github.io/blog/pipe-terminal-output-to-claude-cursor-aider/</guid>
      <pubDate>Mon, 27 Apr 2026 09:00:00 +0000</pubDate>
      <dc:creator>ClipGate</dc:creator>
      <category>workflow</category>
      <category>ai</category>
      <category>cli</category>
      <category>terminal</category>
      <description>A practical 2026 guide to piping terminal output — errors, logs, build failures — straight into Claude Code, Cursor, and Aider with zero copy-paste and automatic secret redaction.</description>
      <content:encoded><![CDATA[<p><strong>Pipe once, hand off forever.</strong> Stop copy-pasting tracebacks and build logs into AI chats. This 2026 guide shows how to pipe terminal output — errors, logs, failures — straight into Claude Code, Cursor, and Aider with automatic secret redaction, so the assistant gets the full context and your tokens never leave the box.</p><p><a href="https://clipgate.github.io/blog/pipe-terminal-output-to-claude-cursor-aider/">Read the full post →</a></p>]]></content:encoded>
    </item>

    <item>
      <title>Benchmarking ClipGate v0.1.4: Where the 5ms Promise Comes From</title>
      <link>https://clipgate.github.io/blog/clipgate-benchmarks-v0-1-4/</link>
      <guid isPermaLink="true">https://clipgate.github.io/blog/clipgate-benchmarks-v0-1-4/</guid>
      <pubDate>Thu, 16 Apr 2026 14:00:00 +0000</pubDate>
      <dc:creator>ClipGate</dc:creator>
      <category>engineering</category>
      <category>performance</category>
      <category>cli</category>
      <category>benchmarks</category>
      <description>Preliminary latency numbers for cg copy and cg paste, the methodology behind them, and a reproducible harness you can run on your own machine. Published ahead of the formal v0.1.5 benchmark suite.</description>
      <content:encoded><![CDATA[<p><strong>Preliminary numbers — final suite lands with v0.1.5.</strong> We talk about "5ms end-to-end" on the home page. This post opens the hood: what exactly we measure, how the numbers break down between classification, encryption, and disk, and how you can reproduce the measurements on your own machine with <code>hyperfine</code> before v0.1.5 ships the formal benchmark suite.</p><p><a href="https://clipgate.github.io/blog/clipgate-benchmarks-v0-1-4/">Read the full post →</a></p>]]></content:encoded>
    </item>

    <item>
      <title>Stop Losing Errors, Commands, and Paths in Your Clipboard</title>
      <link>https://clipgate.github.io/blog/how-to-stop-losing-errors-commands-and-paths/</link>
      <guid isPermaLink="true">https://clipgate.github.io/blog/how-to-stop-losing-errors-commands-and-paths/</guid>
      <pubDate>Mon, 13 Apr 2026 14:00:00 +0000</pubDate>
      <dc:creator>ClipGate</dc:creator>
      <category>workflow</category>
      <category>cli</category>
      <category>terminal</category>
      <category>devops</category>
      <category>productivity</category>
      <description>How to stop losing errors, commands, and paths in your clipboard. A workflow-first guide to reducing context loss in shell-heavy sessions and recovering faster without scrollback hunts.</description>
      <content:encoded><![CDATA[<p>Shell-heavy sessions overwrite the clipboard dozens of times an hour. The painful part is not the copy itself, it is the recovery loop: re-running commands, re-finding paths, and rebuilding the exact error you needed for a ticket or handoff. This post lays out a workflow-first way to cut that context loss down.</p><p><a href="https://clipgate.github.io/blog/how-to-stop-losing-errors-commands-and-paths/">Read the full post →</a></p>]]></content:encoded>
    </item>

    <item>
      <title>Your AI Coding Assistant Is Watching Your Clipboard (2026)</title>
      <link>https://clipgate.github.io/blog/ai-coding-assistant-clipboard-secrets-2026/</link>
      <guid isPermaLink="true">https://clipgate.github.io/blog/ai-coding-assistant-clipboard-secrets-2026/</guid>
      <pubDate>Wed, 08 Apr 2026 19:27:43 +0000</pubDate>
      <dc:creator>ClipGate</dc:creator>
      <category>security</category>
      <category>ai</category>
      <category>devops</category>
      <category>productivity</category>
      <description>AI coding assistants are the fastest-growing source of accidental secret exposure in 2026. Here's a developer-friendly playbook for keeping tokens out of Copilot, Cursor, and Claude Code — without slowing down.</description>
      <content:encoded><![CDATA[<p>You pasted a failing `curl` into Copilot chat to ask why it returns 401. The paste included the `Authorization: Bearer eyJhb...` header. Your token is now in the Copilot request log, and — depending on your org's settings — in a model provider's cache too. You didn't "leak" it in the old sense. No commit, no push, no public repo. But it left your machine.</p><p><a href="https://clipgate.github.io/blog/ai-coding-assistant-clipboard-secrets-2026/">Read the full post →</a></p>]]></content:encoded>
    </item>

    <item>
      <title>I Accidentally Pasted a Password or API Key — What to Do Next (and How to Stop It Forever)</title>
      <link>https://clipgate.github.io/blog/accidentally-pasted-password-or-api-key/</link>
      <guid isPermaLink="true">https://clipgate.github.io/blog/accidentally-pasted-password-or-api-key/</guid>
      <pubDate>Tue, 07 Apr 2026 09:00:00 +0000</pubDate>
      <dc:creator>ClipGate</dc:creator>
      <category>Security</category>
      <category>Incident response</category>
      <category>Secrets</category>
      <description>A calm, step-by-step recovery playbook for the moment you accidentally paste a password, API key, or token into Slack, GitHub, a screen share, or a doc — plus how to stop it from happening again with a secret-aware, locally encrypted clipboard.</description>
      <content:encoded><![CDATA[<p>Take a breath. This happens to senior engineers, security people, and everyone in between. The post walks through a 60-second triage, an 8-step damage-control playbook, scenario fixes for Slack, GitHub, screen shares, and docs, the myths that make leaks worse, and how a secret-aware clipboard quietly closes the entire category of "I just pasted the wrong thing."</p><p><a href="https://clipgate.github.io/blog/accidentally-pasted-password-or-api-key/">Read the full post →</a></p>]]></content:encoded>
    </item>

    <item>
      <title>Best Clipboard Manager for Developers in 2026: Local-First, Terminal-Friendly, and AI-Ready</title>
      <link>https://clipgate.github.io/blog/best-clipboard-manager-for-developers-2026/</link>
      <guid isPermaLink="true">https://clipgate.github.io/blog/best-clipboard-manager-for-developers-2026/</guid>
      <pubDate>Tue, 07 Apr 2026 08:00:00 +0000</pubDate>
      <dc:creator>ClipGate</dc:creator>
      <category>Workflow</category>
      <category>Secrets</category>
      <category>Terminal</category>
      <description>Why generic clipboard history breaks down for developers, and how to evaluate local-first, terminal-friendly, secret-aware clipboard managers in 2026.</description>
      <content:encoded><![CDATA[<p>Developers waste real time losing commands, errors, and paths in the clipboard. This post lays out a practical evaluation framework for local-first, terminal-friendly, secret-aware clipboard tools — and explains why semantic retrieval matters more than a longer history list.</p><p><a href="https://clipgate.github.io/blog/best-clipboard-manager-for-developers-2026/">Read the full post →</a></p>]]></content:encoded>
    </item>
  </channel>
</rss>
