SShortSingh.
Back to feed

Docker warns AI coding agents run with full developer permissions and no sandbox

0
·1 views

Docker published the second installment of its Coding Agent Horror Stories series on July 20, highlighting a key security gap in how AI coding agents operate on developer laptops. By default, these agents inherit the developer's filesystem permissions and environment credentials, with no isolation layer between the agent and the host machine. Docker draws a parallel to self-hosted CI runners, which are already treated as a security risk unless explicitly sandboxed for the same reasons. The post outlines potential mitigations including containers, microVMs, and per-task sandboxes, each with different trade-offs in security, cost, and practicality. Docker frames this as a category-level risk rather than a specific incident, positioning the piece as part of a broader six-part series on coding-agent failure modes.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

React usePrevious Hook Bug: Why Ref-Based Implementations Can Mislead Developers

React has no built-in way to access a component's previous state or prop values, leading developers to rely on a widely shared pattern that stores values in a ref via useEffect. This classic approach returns the value from the previous render rather than the last distinct value, meaning any unrelated re-render silently overwrites the stored reference. The flaw can cause UI indicators — such as a count-change arrow — to disappear incorrectly after a theme toggle or parent re-render, even when the tracked value has not changed. The @reactuses/core library addresses this with a usePrevious hook built on useState instead of refs and effects, ensuring only genuine value changes update the stored previous value. The alternative twelve-line implementation follows patterns recommended in React's own documentation and avoids the drift and infinite-loop risks associated with the ref-based recipe.

0
ProgrammingDEV Community ·

How to Build Reliable Pagination for TikTok's Unpredictable Public API

TikTok's public web endpoints frequently return inconsistent pagination data, including underfilled pages, duplicate records, and unreliable continuation cursors. A developer building a public TikTok metadata API addressed these issues by treating pagination as a strict application-level contract rather than a simple pass-through to upstream requests. The solution enforces invariants such as ensuring the returned record count always matches the declared page count, and uses server-returned cursors instead of manually calculated offsets. Rate-limit handling is built in via exponential backoff with jitter for HTTP 429 and 503 responses, and errors include traceable request IDs without exposing credentials. The resulting paginator works uniformly across multiple TikTok endpoints, including video, user, hashtag, and music search routes.

0
ProgrammingDEV Community ·

Claude Desktop and Claude Code Maintain Separate States on Windows, Dev Guide Explains

A developer guide clarifies that Claude Desktop, Claude Code, and provider usage operate as three distinct state machines on Windows, not a single unified system. Application state tracks whether Claude Desktop is running or hidden, while Claude Code session state monitors active coding sessions, and usage state covers provider quota and credential validity. A closed window does not confirm the underlying process has stopped, and a failed usage credential should not cause a healthy coding session to appear broken. Developers are advised to preserve independently observed session states and use correct Windows activation paths rather than routing all Claude-related actions through a generic launch command. The guide is published alongside Agent Island, a free open-source status companion for Claude Code on Windows and macOS that stores data locally and does not upload session information.

0
ProgrammingDEV Community ·

x402 Payment Protocol Signs Token Details, Not the Resource Being Purchased

A developer testing the x402 payment protocol found that its payer signature does not cover the URL or resource being purchased, only the amount, recipient, token contract, and blockchain chain. By rebuilding the EIP-712 digest from the official x402 v2 spec example and running secp256k1 public key recovery, the researcher mutated 18 fields one at a time and found that 8 changes — including altering the resource URL — left the signature still valid. This means a payment can be redirected to a different resource without invalidating the cryptographic proof of payment. The researcher proposed a zero-protocol-change fix: encoding the intended resource into the 32-byte nonce that payers already choose and sign. The finding carries practical urgency as Cloudflare announced an x402-based monetization gateway on July 1, 2026, significantly expanding the number of automated agents expected to use the protocol.