🌍 Dev.to

"200 OK" doesn't mean your AI agent did the job

Your agent says it sent the proposal. The tool call came back with an id. The trace shows a green step. The customer never got the email. I've seen versions of this enough times that I no longer trust a success response on its own. Here's why, and what I check instead. Success responses mean "accepted", not "done" Most APIs tell you they received your request. They don't tell you the end result. A mail API returns an id when the message is accepted. That's not the same...
🌍 Dev.to

pin-deep: you pinned your Actions, but your Actions didn't pin theirs

Everyone knows the drill: pin your GitHub Actions uses: to a commit SHA so a compromised tag can't rug-pull your CI. Done, right? Not quite. There's a depth problem nobody checks. The tj-actions incident (CVE-2025-30066) is the textbook case: the compromise reached victims through reviewdog, which referenced the compromised action. Pinning reviewdog itself wasn't enough — the hole was one level deeper, inside the dependency of a pinned dependency. "You pinned your Actions, but the Ac...
AI Agent Memory: Context Management Strategies for 2026
🌍 Dev.to

AI Agent Memory: Context Management Strategies for 2026

AI Agent Memory Management: How to Reduce Context Bloat Without Losing Critical Details Strong AI agent memory comes from selective retention, not from replaying full history on every step. Good context window management keeps the prompt lean by preserving durable facts, decisions, and task state while compressing transient chatter. For most agentic workflows, the practical answer is a layered memory design: use rolling summaries for token reduction, checkpoint snapshots for exact state, ...
🌍 Dev.to

dlog v0.2: two gates for the decision log — one I can enforce, one I can't

A few weeks ago I published dlog , a tiny append-only decision log for coding-agent sessions: dlog add "chose X" -r "because Y" , one JSONL line per decision. The best feedback came from reader loganilands, across four rounds of discussion. They'd run honesty experiments on frontier models: asked plainly, models answered "I don't know" correctly 0 out of 8 times; asked with leading questions, they confidently fabricated 8 out of 8. Their summary stuck with me: "Empty, verified, wrong." ...
🌍 Dev.to

Your Claude Code skills are being silently demoted. I built a CLI to catch it

Your Claude Code skills are being silently demoted, and nothing tells you. Every skill you install injects its name and description into the model's context on every turn — used or not. Claude Code budgets that listing at 1% of your context window ( skillListingBudgetFraction , default 0.01 ). When the listing overflows, it drops descriptions starting with your least-used skills. No warning in the UI. Just a --debug log line. A skill without a description has nothing left for the mode...
🌍 Dev.to

A task record is not an execution contract: a handoff template for coding agents

Disclosure: This draft was generated with AI assistance. The worked example is illustrative and has not been run against a production repository. A ticket can accurately describe a bug while leaving the executor unable to start. “CSV export loses filters” tells us what hurts. It does not identify the repository revision, the supported command, the intended output, or the person who can accept the change. When comparing task tracking with managed agent execution, compare responsibilities ra...
Modeling Game Worlds with Shapezo: A Typed Content Pipeline for Levels, Biomes, and Set Pieces
🌍 Dev.to

Modeling Game Worlds with Shapezo: A Typed Content Pipeline for Levels, Biomes, and Set Pieces

Most game documentation fails for a boring reason: it is unstructured prose about structured things. A level is a graph. It has zones, routes, sightlines, interactive props, light cues, encounter triggers, streaming boundaries, and a pacing curve, all with relations between them. Storing that as a wiki page throws the graph away and leaves you re-deriving it by hand every sprint. Shapezo's answer is to model the location first and render prose second. Content becomes typed objects with a sche...
🌍 Dev.to

I Fixed an Idempotency Bug in My Spring Boot E-Commerce Backend

Sometimes, the most useful improvements to a project come from someone asking a question you had not fully considered. While working on ShopEase, my Spring Boot e-commerce backend, I implemented idempotency protection to prevent duplicate checkout requests. My initial approach returned HTTP 409 Conflict whenever an Idempotency-Key was reused. Then Andrei Ovcharenko commented on my Dev.to article with an important observation: What if the order commits successfully, but the client nev...
🌍 Dev.to

Why an AI-written change waits for CI evidence

We learned that an AI-written change can look complete long before it’s safe to merge. The implementation may be coherent, the explanation persuasive and every review comment resolved, but none of that shows how the candidate behaved in the delivery pipeline. That gap changed how we treated the gate. It now fails closed: a positive result has to be observed independently. If the required continuous integration evidence is missing, incomplete, stale or unverifiable, the change stays blocked. ...
🌍 Dev.to

Where did the unfinished changes go?

We noticed delivery volume in the current phase had reached twice that of the early build phase, without any rise in repeated repair. Here’s how we’re testing whether completion, rather than implementation quality, has become the main constraint, and what we need to measure to find where unfinished changes accumulate. Encouraging, certainly. Reproducible? Not yet. We don’t have the raw counts, phase boundaries or cohort observation windows behind that comparison. And the completion figure ...
🌍 Dev.to

Anthropic Unveils Claude 4.5 Opus: Multi-Agent Orchestration and Autonomous Tool Synthesis

Anthropic Launches Claude 4.5 Opus for Autonomous Agent Teams Anthropic has officially launched Claude 4.5 Opus on October 9, 2026, marking the frontier research lab's most capable foundation model to date. Engineered specifically for complex autonomous problem-solving and multi-step systems engineering, Claude 4.5 Opus introduces native multi-agent orchestration, dynamic tool synthesis, and a 500,000-token context window with perfect factual recall. The release sets immediate performance...
HackerNews

I Made Terrible Games with Google's AI Playground

Article URL: https://www.wired.com/story/i-made-terrible-games-with-googles-ai-playground/ Comments URL: https://news.ycombinator.com/item?id=50052736 Points: 1 # Comments: 0
HackerNews

Cartographers of North Korea (2019)

Article URL: https://cartographers-nk.wonyoung.so/ Comments URL: https://news.ycombinator.com/item?id=50047091 Points: 241 # Comments: 44