---
title: "Ilja Nevolin (@inevolin) | Hashnode"
description: "Ilja Nevolin (@inevolin) writes on Hashnode. Read their latest articles and follow their work."
url: "https://hashnode.com/@inevolin"
---

@inevolin

# Ilja Nevolin

@inevolin · Joined October 2026

## Comments

[Not close, unfortunately. Running /compact before the break cost about 2.5x a new session, and /compact after the cache had expired was still about 9.7x. I only ran it on one 97,000 token session, so I can't say how it scales.](https://hashnode.com/posts/why-claude-code-can-cost-you-2x-to-10x-your-usage-limits/6afc9b4a952365d313983abf/comment/6afcada6b97d89faffa594a1#reply-6afcafd9bdf4e069af67315d)

Reply · Article · 14h ago · 1 · [Why Claude Code can cost you 2x to 10x your usage limits](https://hashnode.com/posts/why-claude-code-can-cost-you-2x-to-10x-your-usage-limits/6afc9b4a952365d313983abf)

[Good question. In technical work I worry less about it, because a stale fix usually fails loudly. The agent hits an error, re-checks the memory and flags or corrects it. Two distinct flags archive an entry, so nobody has to delete it by hand, and reactions feed a visible standing that lifts or sinks it in search. Business context is the real gap. A wrong claim about a customer or a policy does not throw an error, so it can spread quietly. That is where I want to go next: require agents to verify a claim before relying on it, and record when each memory was last re-checked. Today, memories over 90 days old that nobody confirmed already show a stale warning, but an explicit re-check date would make that much stronger.](https://hashnode.com/posts/unlocking-swarm-intelligence-with-big-agentic-brain-and-claude-code/6ad9e81f285c538ec2b69815/comment/6adb54682c8778db47f37778#reply-6adddb76aca973e66b127927)

Reply · Article · Oct 25 · [Unlocking Swarm Intelligence with Big Agentic Brain and Claude Code](https://hashnode.com/posts/unlocking-swarm-intelligence-with-big-agentic-brain-and-claude-code/6ad9e81f285c538ec2b69815)
