Category
Agents
Coding agents and context management.
13 published
- Agents7 min
The child process inherited nothing, so the test now walks every spawn site
Child process environment variables: config moved to a table loaded by each entry point's first import, and three scripts the bot spawns were not entry points. A test now walks spawn sites.
- Agents6 min
Four traps when merging parallel agent worktrees into one trunk
Git worktree for parallel agents: sessions edit one repo in separate worktrees and a person merges by cherry-pick. The traps are the tests, the classifier, patch-ids and the leftovers.
- Agents5 min
My LLM tracing store was 138 GB. The traces were 3.2 MB of it
ClickHouse disk usage under self-hosted Langfuse: 117 GB of it profiling its own queries. The fix sat unapplied for 18 days, and the table was too big to drop.
- Agents6 min
A restart sent 30 direct messages in 8 seconds. Then --help sent the daily report three times
Telegram bot duplicate messages, twice in three days: code that reads the live database and talks to a person is only as safe as the rows it finds, and DM is not a fallback.
- Agents6 min
The approval queue said nine fixes were waiting. Eight were already in production
Human in the loop agent approvals: the bot's pending list was its own table while people merged the same branches by hand. The fix was a check at the moment of speaking, not a sync job.
- Agents7 min
I told the agent to search its memory. It made 31 tool calls and searched zero times
LLM agent memory search: a 24-run experiment said telling the agent to search was as good as injecting notes. It measured irrelevant notes against nothing, and nobody searched.
- Agents4 min
The numbers halved and the fix never ran
Deployment verification the hard way: wall clock down 53 percent, tool calls down 47, and the line the fix exists to produce absent in both runs. The config was a symlink shared by every worktree.
- Agents6 min
The median barely moved and the spread collapsed
Claude Code speed on code review: one line naming the search command. The median barely moved, the worst case fell from 18.0 to 12.2 minutes, and tool calls did not change.
- Agents9 min
LangGraph yes, LangChain no
LangGraph vs LangChain in an agent pipeline: one earns its place by doing something I would otherwise write badly. The other is a spec I satisfy without importing.
- Agents8 min
Building the guardrails I needed after a session died
Claude Code hooks and a status line for context usage and compaction. Both read the transcript rather than an API field, and that choice is the post.
- Agents8 min
I instrumented everything except where the decisions happen
LLM agent observability with a connected, green tracing dashboard, and zero traces from the three components that actually make choices.
- Agents10 min
Context is burned by tool output, not by conversation
Claude Code context usage over a two-month transcript: the largest entries were single command results, around 300,000 tokens each.
- Agents9 min
An 80-day agent session and the wall at the end of it
Claude Code context limit on an 80-day session: fifty compactions, each starting from a full million tokens. Then one morning it stopped answering for nineteen minutes.