The None That Broke Permissions: How a Single Null Crashed Hermes Agent Approvals

A tiny missing check, a silent crash, and a denied permission that should have been safe. This is the story of how I fixed it.

About me and why this matters

I am Aniruddha Adak, a full stack developer from Kolkata, working across Next.js, React, TypeScript, Python and AI agent tooling. My GitHub profile is aniruddhaadak80 with over 238 accepted pull requests during Hacktoberfest and active contributions to projects like google-gemini/gemini-cli, openclaw/openclaw, topoteretes/cognee and NousResearch/hermes-agent.

Over the last two years I have been focusing on one thing, finding bugs that hide in plain sight, especially those that appear only on edge cases, cross platform setups and agent communication layers.

This post is my submission for DEV Summer Bug Smash 2026 in the Clear the Lineup track. It is also aiming for Best Use of Google AI.

The None That Broke Permissions: How a Single Null Crashed Hermes Agent Approvals

Related reading

Building Phinq: How a Cronjob Failure Forced Me to Redesign Agent Governance…

4 Silent Failures, 2 Undocumented APIs, and a Container That Crashed Because of…

Wrapping Hermes Agent with agent-stack: six tiny libs for the boring parts

The Hermes Rescue: How an Open Agent Rebuilt My GitHub Projects from Scratch

I Let AI Agents Attack My Permission Gateway for a Week. Here's What Broke.

My Self-Hosted AI Assistant Kept Overwriting Its Own API Keys: A Zero-Trust…