#Claude Code
6 posts · All tags
-
Claude Code Triaging Sentry Alerts Read-Only: Locking It Down With --allowedTools, and the 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.
-
Clickable Bands in Claude Code Mods: API Limits Shape the Design, and What leftovers 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.
-
Claude Code Mods From a Month of Session Logs: Five Bands, Status Line Items, and Commands
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.
-
Automating a Bitfinex Lending Rate Report: A Claude Code Routine Opens a PR, a Human Merges It
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.
-
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.
-
A Full-Site Redesign With Design Tokens: AI Scores Make a Bad Gate, and One PR Reskinned 90%
My product, dashboard, admin, and email swapped dark rounded cards for a square-cornered blueprint style. AI review scores work only as a regression list; swapping design token values first reskinned 90% of screens in one PR.