Secure AI Coding at the Source.
San Francisco, CA
Joined January 2025
- Tweets147
- Following9
- Followers1.6K
- Likes94
Corridor retweeted
Today, Corridor is joining Cognition! Together, we’ll be taking Devin Security to the next level.
We started Corridor almost two years ago with the mission of accelerating secure and autonomous software development. Since then, we’ve seen security go from a niche concern to one of the most pressing issues of our time.
We’re grateful to our team, our customers, our investors, and everyone who’s supported us along the way. We can’t wait to show you what we build next!
Today, Cognition is acquiring @corridor.
Securing the world’s software is the most important problem in technology today.
Let’s get to work!
Corridor retweeted
Turns out you don’t need a trillion parameter model and 67 data centers in Virginia for every task.
Thanks to @baseten and @LangChain for their support here!
Corridor retweeted
@farzaankai and I are so excited to share what we've been working on over the last few months.
Introducing Argos: Corridor's first security model.
Special thanks to @baseten and @LangChain for all your support.
Corridor retweeted
.@corridor used smithtune’s trace-based workflow to build the training data for Argos, a fine-tuned 9B model that scores the highest of the 14 models they tested on their security context benchmark.
🧵 Full thread ⤵️
Corridor retweeted
LangSmith for Startups Spotlight: @corridor
@Corridor uses LangSmith to develop + run novel agentic security evaluations, build + trace inference pipelines, and manage memory graphs that provide specialized context across various product surfaces.
Get a demo: corridor.dev/demo
Corridor retweeted
Today, @corridor and @TransluceAI are disclosing new evidence of AI agents probing and attempting rudimentary vulnerability exploits against U.S. and Canadian government agencies.
Read more: transluce.org/us-canada-gov
Corridor retweeted
Google's models hacked into real companies.
While we should be glad that Google's agent didn't cause further harm, I pushed back on the idea that this was business as usual. Agents hacking into real companies is serious and the public deserves to know.
More from @erinkwoo and @bobmcmillan in @WSJ:
Google said it didn't disclose the hacks because they didn't cause harm, and because the models stopped when they realized they accessed real companies. It's part of a broader conversation about how—and when— firms should disclose AI safety/security incidents.
ft @jackhcable
Corridor retweeted
Corridor is proud to join @OpenAI and other industry leaders in calling to strengthen cyber defenses in the face of increasingly capable models.
Beyond just finding vulns, the focus has to shift to wide-scale remediation and prevention, and that's what we're doing at Corridor.
Corridor retweeted
New research from @corridor: we found that coding agents - even with models like Fable - can be trivially tricked into running malware.
We connected coding agents to our support system, filed a ticket, and got them to exfil secrets and run malware.
corridor.dev/blog/coding-age…
Corridor retweeted
The way every enterprise builds software is changing. I wrote about what this means for security - and where it goes from here.
Corridor retweeted
Corridor has joined leading AI companies in signing Microsoft and NVIDIA's letter on Open Weights and American AI Leadership.
Last month, I testified to Congress on the importance of maintaining America's lead in AI through open-weight models. Increasingly capable open-weight models are only more reason to do so -- defenders must have access to best-in-class models to shore up their defenses.
Corridor retweeted
Ashwin wrote up how he got into cybersecurity (and how we met) when he hacked Stanford and ended up in my office getting advice on how most CISOs were going to be much less chill than Stanford's.
Corridor retweeted
@skeptrune if you want to handle security and compliance right with auto-approval… use @corridor as a required CI check along with your auto-approver. See how we did it: corridor.dev/blog/making-cod…
Corridor retweeted
thanks @ClaudeDevs for the shoutout and being extremely responsive as always!! shipped a fix to a bug @corridor reported in `claude mcp add` 🙏
Corridor retweeted
We just did something crazy at @corridor: we made human code review optional. We use an AI reviewer and @corridor's own security checks. The results:
Median merge time: 21hrs → <3hrs
PRs shipped: 2-3x
Reversion rate: 1.2% → 0.7%
corridor.dev/blog/making-cod…
Corridor retweeted
Today, @Corridor is releasing hookshot, an open source library that makes it super easy to build hooks into coding agents. Write one Go script and instantly support Claude Code, @cursor_ai, @FactoryAI, Codex, and Windsurf across all OSes.
Check it out: github.com/CorridorSecurity/…
Corridor retweeted
@corridor is actively hiring across every role! corridor.dev/jobs, SF
Corridor retweeted
Introducing Athena: the industry coalition to protect open source software from AI attacks.
Athena is operational today. More than two dozen members. It's processed 20,000+ findings and generated 2,000+ patches across 500+ open source projects.
Join us: chainguard.dev/athena
Corridor retweeted
Proud to sign the letter led by @alexstamos calling for the US government to lift export controls on Mythos and Fable.
As I testified to Congress a few weeks ago, it's imperative to get frontier models in the hands of cyber defenders ASAP. Restrictions only give our adversaries more time.
Read and sign here: freefable.org/
