Sending an email shouldn't feel like reviewing a pull request
Approval cards designed for code reviews carry too much chrome for conversational AI. Here's how we redesigned them for the Telegram thumb.
Your AI coding assistant is powerful — but who watches it while you are away from your desk? We write about the architecture, the trade-offs, and the hard-won lessons behind building an intelligent layer between Claude Code and your phone. From three-tier classification pipelines that auto-answer routine questions to approval engines that learn your patterns after three taps — every article is a deep dive into the systems that let you ship code from a park bench without losing sleep.
Approval cards designed for code reviews carry too much chrome for conversational AI. Here's how we redesigned them for the Telegram thumb.
CodePulse Real-life Mode turns Telegram into a single interface for Gmail, Calendar, Drive, Linear, Slack, and your codebase — all driven by Claude with explicit approval.
We built a CI test gate, ran two adversarial reviews on it, and found four ways it could silently report green on broken code. Here's the layered defense that survived.
A reusable shift-left pattern: run the target runtime's own parser against every interpreted-language file in CI before any expensive build step.
Claude Code v2.1.85 added an `if` field that scopes hooks to specific tool calls. Here is how to use it from CodePulse via HOOK_IF_FILTERS.
Our approval pipeline held HTTP connections open for 360 seconds per pending decision. CLI v2.1.89's defer permission rewrote the contract. Here is the migration.
A Claude Code CLI wire-format bug shipped past every unit test we wrote. The tests had encoded the wrong contract. A field guide to false-confidence testing.
Four months of release-pipeline hardening tagged successfully. None of it ran. A post-mortem on the workflow_dispatch default-branch gotcha.
v2.3.111 broke every install. The v2.3.112 hotfix introduced a new bomb of the same class. A field guide to PowerShell 5.1's silent encoding traps.
Adding a feature to CodePulse used to take 4-8 hours and touch 5-7 files. Here is the framework refactor that brought it down to 1-3 hours and 2-3 files.