<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>Islo Blog</title><description>Islo deploys and runs autonomous coding agents in secure environments connected to your tools, so they can finish real engineering work.</description><link>https://islo.dev/</link><language>en-us</language><item><title>A host-file disclosure vulnerability in Harbor&apos;s benchmark regrading</title><link>https://islo.dev/blog/benchmarks-as-an-attack-vector/</link><guid isPermaLink="true">https://islo.dev/blog/benchmarks-as-an-attack-vector/</guid><description>How a Harbor regrade vulnerability let task-authored code read a host file, and what it means for enterprise evaluations and RLVR training.</description><pubDate>Thu, 22 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Our agent rewrote its score in Harbor&apos;s separate verifier</title><link>https://islo.dev/blog/verifier-tampering/</link><guid isPermaLink="true">https://islo.dev/blog/verifier-tampering/</guid><description>In a controlled Harbor run, the tests failed and a fairness judge caught the cheat, yet submitted code overwrote the final score. We examine the trust boundary inside verification and the Terminal-Bench community&apos;s work to secure it.</description><pubDate>Thu, 15 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Your agent evals are wrong</title><link>https://islo.dev/blog/your-agent-evals-are-wrong/</link><guid isPermaLink="true">https://islo.dev/blog/your-agent-evals-are-wrong/</guid><description>Replaying real engineering work sounds straightforward until the agent needs the internet. The eval has to freeze that internet at the moment the work was done.</description><pubDate>Mon, 28 Sep 2026 00:00:00 GMT</pubDate></item><item><title>How ARIMLABS runs 500,000 agent executions a day on Islo</title><link>https://islo.dev/blog/how-arimlabs-runs-agent-evaluations-at-scale-on-islo/</link><guid isPermaLink="true">https://islo.dev/blog/how-arimlabs-runs-agent-evaluations-at-scale-on-islo/</guid><description>ARIMLABS moved agent evaluations from local machines to an always-on Islo workflow with isolated computers, parallel trials, and inspectable reruns.</description><pubDate>Tue, 15 Sep 2026 00:00:00 GMT</pubDate></item><item><title>AI coding has outgrown the laptop</title><link>https://islo.dev/blog/ai-coding-has-outgrown-the-laptop/</link><guid isPermaLink="true">https://islo.dev/blog/ai-coding-has-outgrown-the-laptop/</guid><description>AI coding began on developer laptops. Autonomous work needs shared, persistent, observable and governable cloud environments.</description><pubDate>Mon, 14 Sep 2026 00:00:00 GMT</pubDate></item><item><title>What is a software factory? 5 products to evaluate in 2026</title><link>https://islo.dev/blog/what-is-a-software-factory-5-products-to-evaluate-in-2026/</link><guid isPermaLink="true">https://islo.dev/blog/what-is-a-software-factory-5-products-to-evaluate-in-2026/</guid><description>What is a software factory? Compare Devin, Cursor, Linear, Factory, and Islo across autonomy, infrastructure, verification, governance, and fit.</description><pubDate>Mon, 17 Aug 2026 00:00:00 GMT</pubDate></item><item><title>Introducing Islo BYOC for enterprise teams</title><link>https://islo.dev/blog/introducing-islo-byoc/</link><guid isPermaLink="true">https://islo.dev/blog/introducing-islo-byoc/</guid><description>Run Islo coding agents on infrastructure you own—your AWS account or on-prem Linux machines—while Islo keeps operating the product for you.</description><pubDate>Thu, 30 Jul 2026 00:00:00 GMT</pubDate></item><item><title>How Alien uses AI &quot;Sims&quot; to continuously test its deployment platform</title><link>https://islo.dev/blog/how-alien-uses-ai-sims-to-continuously-test-its-deployment-platform/</link><guid isPermaLink="true">https://islo.dev/blog/how-alien-uses-ai-sims-to-continuously-test-its-deployment-platform/</guid><description>Alien runs AI agents called Sims on Islo to test deployment scenarios across clouds, architectures, and customer-controlled environments.</description><pubDate>Wed, 29 Jul 2026 00:00:00 GMT</pubDate></item><item><title>OpenAI could have stopped the Hugging Face attack</title><link>https://islo.dev/blog/openai-could-have-stopped-hugging-face-attack/</link><guid isPermaLink="true">https://islo.dev/blog/openai-could-have-stopped-hugging-face-attack/</guid><description>How OpenAI&apos;s model escaped its evaluation sandbox through an allowlisted package proxy, and why host-level allow and deny is the wrong granularity for containing AI agents.</description><pubDate>Sun, 26 Jul 2026 00:00:00 GMT</pubDate></item><item><title>How Obert built a software factory it can trust on Islo</title><link>https://islo.dev/blog/how-obert-built-a-software-factory-it-can-trust/</link><guid isPermaLink="true">https://islo.dev/blog/how-obert-built-a-software-factory-it-can-trust/</guid><description>How Obert uses Islo to turn well-scoped product work into trusted agent workflows and give a small AI-native team more engineering capacity.</description><pubDate>Thu, 23 Jul 2026 00:00:00 GMT</pubDate></item><item><title>How we stopped working for our agents</title><link>https://islo.dev/blog/how-we-stopped-working-for-our-agents/</link><guid isPermaLink="true">https://islo.dev/blog/how-we-stopped-working-for-our-agents/</guid><description>We automated implementation first and it backfired. Starting with review and verification instead, and wiring it all together with webhooks and label-driven triggers, gave us an autonomous engineering loop where a Linear label goes in and a merged PR comes out.</description><pubDate>Wed, 15 Jul 2026 00:00:00 GMT</pubDate></item><item><title>Using sandboxes to stop agents from cheating</title><link>https://islo.dev/blog/reward-hack-bench-sandbox-stops-agent-cheating/</link><guid isPermaLink="true">https://islo.dev/blog/reward-hack-bench-sandbox-stops-agent-cheating/</guid><description>Introducing RewardHackBench, an open-source benchmark for measuring whether sandbox policies prevent reward hacking in agent evaluations.</description><pubDate>Mon, 15 Jun 2026 00:00:00 GMT</pubDate></item><item><title>When you should use Kubernetes Agent Sandbox</title><link>https://islo.dev/blog/agent-sandbox-why-should-i-use-it/</link><guid isPermaLink="true">https://islo.dev/blog/agent-sandbox-why-should-i-use-it/</guid><description>A technical look at what Agent Sandbox solves inside Kubernetes, what it leaves to the platform team, and how to decide if it&apos;s the right primitive for your setup.</description><pubDate>Tue, 26 May 2026 00:00:00 GMT</pubDate></item><item><title>Coding Agents Need a New Primitive, and It&apos;s Not a Sandbox</title><link>https://islo.dev/blog/coding-agents-need-new-primitive/</link><guid isPermaLink="true">https://islo.dev/blog/coding-agents-need-new-primitive/</guid><description>Fast boot times are useful for request-shaped compute. Coding agents need something closer to a secure, persistent, workstation-shaped runtime.</description><pubDate>Sun, 17 May 2026 00:00:00 GMT</pubDate></item><item><title>What 100 Conversations Taught Us About Autonomous Coding Agents</title><link>https://islo.dev/blog/four-layers-of-software-factories/</link><guid isPermaLink="true">https://islo.dev/blog/four-layers-of-software-factories/</guid><description>A framework for evaluating what you need to run AI coding agents at scale and where most teams get stuck.</description><pubDate>Mon, 30 Mar 2026 00:00:00 GMT</pubDate></item><item><title>The missing layer of the agent development stack</title><link>https://islo.dev/blog/how-we-accidentally-built-doubleagent/</link><guid isPermaLink="true">https://islo.dev/blog/how-we-accidentally-built-doubleagent/</guid><description>Stateful fake servers for GitHub, Slack, and Stripe that work with official SDKs  -  built for AI agent development.</description><pubDate>Tue, 17 Feb 2026 00:00:00 GMT</pubDate></item><item><title>Monty and Islo: Sandbox the Snippet, Isolate the Agent</title><link>https://islo.dev/blog/why-islo-loves-monty/</link><guid isPermaLink="true">https://islo.dev/blog/why-islo-loves-monty/</guid><description>Monty sandboxes runtime-generated Python. Islo gives coding agents a zero-setup environment. Here&apos;s what Monty blocks, what can still crash, and how the layers fit.</description><pubDate>Tue, 10 Feb 2026 00:00:00 GMT</pubDate></item><item><title>Best 5 Sandboxes for Claude Code</title><link>https://islo.dev/blog/competition-docker-daytona-e2b-sprites-coder/</link><guid isPermaLink="true">https://islo.dev/blog/competition-docker-daytona-e2b-sprites-coder/</guid><description>Here are five sandbox options that work with Claude Code (or with AI coding agents in general), and how they compare.</description><pubDate>Sun, 08 Feb 2026 00:00:00 GMT</pubDate></item><item><title>Understanding Sandbox Security</title><link>https://islo.dev/blog/understanding-sandbox-security/</link><guid isPermaLink="true">https://islo.dev/blog/understanding-sandbox-security/</guid><description>Why sandboxing matters for AI agents - isolation, boundaries, and blast radius so you can run agents unattended without risking credentials or production.</description><pubDate>Sun, 08 Feb 2026 00:00:00 GMT</pubDate></item><item><title>You shouldn&apos;t run Clawdbot on your computer</title><link>https://islo.dev/blog/how-secrets-can-be-stolen-clawdbot/</link><guid isPermaLink="true">https://islo.dev/blog/how-secrets-can-be-stolen-clawdbot/</guid><description>How I sent my own database credentials to a server I control using Clawdbot - and why prompt injection and full machine access make that possible in about 20 minutes.</description><pubDate>Sat, 07 Feb 2026 00:00:00 GMT</pubDate></item></channel></rss>