Today, we're launching Security Enforcement for long-running agents. Code is written by agents and nobody is watching. Traditional security reviews aren’t built for this approach, but Corridor is. Today we launched Security Enforcement for long-running agents. We built this to keep security in the loop by enforcing your organization’s security guardrails at commit time. Live for teams on Devin, Claude Code web, Codex, & Cursor: corridor.dev/long-running-ag…

Argos was built by @aditinaraa and @farzaankai, trained on Baseten Loops, with LangSmith Traces and Engine for inspecting selections in production. Full post, benchmark setup, and results: corridor.dev/research/argos If you’re securing the code your agents write, we’d love to talk: corridor.dev/demo

Agents call Argos every time their plan changes, so latency compounds. Argos starts streaming in 740 ms on average, fastest of the models tested, and returns a full validated selection in 1.37 s median, at just 68 generated tokens per call.

The results on SecReT, our security context selection benchmark: Argos scored 0.655 micro F1, highest of 14 models. Gemini 3.6 Flash led the general models at 0.643. Fine-tuning took the base Qwen3.5-9B from 0.480 to 0.655.

Argos reads a coding agent’s plan and selects the security guidance that applies before the agent writes code. For “add a file upload endpoint,” that means the auth middleware, the project access check, the upload helper, and the size limit become part of the plan, not a fix after review.

Introducing corridor-argos-1, Corridor’s first security model. A Qwen 3.5 9B fine-tune that outperforms frontier models including GPT-6 Astra and Claude Opus 5.5 on security context selection, with the lowest time to first token of the 14 models we tested. Thread 🧵

Last week in New York, we brought together a small group of security, AI and engineering leaders from companies including @clay, @figma, @crosbylegal, and Numerix, along with analysts from Latio, for dinner and a candid conversation about the problem everyone is feeling right now: AI is writing code faster than ever, and security hasn't kept up. A lot of the industry is focused on using AI to find and patch vulnerabilities. Around the table, the view was that this misses the point. Securing existing codebases matters, but if the code agents are writing today isn't secure, teams are creating problems faster than they can fix them. Our takeaway: autonomous development, done well, should make software stronger, not riskier. Thanks to everyone who joined us.

We recently demonstrated that TypeSafe’s Jev could be used to gate when our security scan should be run. Since then, OpenAI, Microsoft, Perplexity, and a dozen others shipped decision models of their own. So we ran all of them through the same benchmark for this task. The top two models are Perplexity's Decider and TypeSafe's Jev 1.14. At any budget for latency, cost, or precision, Decider or Jev catches the most vulnerable posts. The rest are at or below the performance of an LLM gate. Full results and the dataset in our latest post: corridor.dev/blog/decision-m…

This time next week, Corridor will be in NYC! 🏙️ ​Join us for happy hour on Thursday, October 15th and hear from @JamesBerthoty and @Guy_Flechter about approaches to securing agentic coding plus @jackhcable's recent research on AI Agents targeting government websites. Come for free food and drinks but stay to exchange best practices in this new age of appsec 🍕🍻 Register today: luma.com/corridor-wkbl

Coding agents now open PRs and push commits in long-running sessions where humans barely look. Our security enforcement for long-running agents scans every change before the agent commits, but a full scan on every commit is slow and expensive, and many commits are obviously safe. So we put a gate in front of each scan to decide which commits need the full check. We tested five gates: Jev (a decision model), CLM-8B, and three LLMs prompted for a confidence score. Jev halved our scanning costs and raised precision with minimal loss in recall. LLM gates helped, but less. CLM-8B off the shelf did not work as a gate. We wrote up what we learned in our latest blogpost: corridor.dev/blog/decision-m…

Just a few more weeks until the Corridor team hits the road and we're in NYC! Join us on Thursday, October 15th for discussions on the state of appsec today, lightning talks on agentic development and security's role to play. Plus free food and drinks all night! 🎤🍻🍕 RSVP today: luma.com/corridor-wkbl