#Claude Code

6 posts · All tags

  1. Mining a Month of Session Logs to Build Five Claude Code Mods

    I had Claude read a month of session logs for requests I kept repeating and turned them into bands, status line items, and commands; the most useful, leftovers, tracks what Claude leaves behind.

    Tools ·
    2026.10.10

  2. GPT as a Read-Only Reviewer for Claude Code: Adversarial Review With Pi

    I wrapped Pi, connected to GPT models over an API, as a read-only reviewer Claude Code can call, and found out why permission rules can't stop file writes and how adversarial review converges.

    Tools ·
    2026.10.10

  3. Letting Claude Triage Alerts Without Letting It Change Anything: Read-Only Triage Design and Pitfalls

    When an alert fires, a Claude session with read-only tools hunts the root cause and posts to Discord; here's how I drew the permission boundary and two pitfalls: rewritten command paths and Sentry noise.

    Engineering ·
    2026.10.10

  4. Clickable Bands in the Terminal: Reworking leftovers and What It Still Can't See

    After shipping my Claude Code mods, I made the bands clickable within limits like uncolorable Buttons and hover misclicks, taught leftovers absolute paths and variable substitution, and listed what command matching still misses.

    Tools ·
    2026.10.10

  5. A Full-Site Redesign: AI Scores Make a Bad Gate, So Swap Tokens First and Rework Layouts Later

    EZLO swapped dark rounded cards for a square-cornered, paper-and-ink blueprint style. AI review scores work only as a regression list; swapping token values first reskinned 90% of screens in one PR.

    Engineering ·
    2026.10.10

  6. A Monthly Bitfinex Lending Rate Report: Public Data for the Numbers, a Scheduled PR for Review

    The rate report is calculated only from Bitfinex's public candles, so anyone can reproduce it. A Claude Code cloud routine opens a PR every month, but nothing merges until a person reviews it.

    Tools ·
    2026.10.10