Engineering Director @Sourcegraph

Joined March 2010
Diego Comas retweeted
PHP released patches for two critical vulnerabilities, CVE-2026-109618 and CVE-2026-109619, that could allow attackers to execute code remotely without authentication. Finding every affected PHP version across hundreds or thousands of repos is a challenge. We're sharing Sourcegraph search queries and Agentic Batch Changes specs to help you find and fix #php2shell vulns. Learn more: sourcegraph.com/blog/php2she… Need help? Post a comment and we'll help you get Sourcegraph set up to find potentially affected repos and roll out patches.
2
2
3
16
3,515
Diego Comas retweeted
Agentic Batch Changes is available today. Describe a change once. It runs across 10 or 10,000 repositories, adapts where they differ, and reacts when CI fails. Agentic Batch Changes uses outcome-based pricing. You pay per changeset merged into your codebase. If a pull request doesn't merge, you don't pay for it. Read more here: sourcegraph.com/blog/introdu…
9
2
1
16
37,313
Diego Comas retweeted
Today we're launching Agentic Batch Changes in public beta, and we're proud of how it's turning out. Mercari engineer Patrick Klitzke used Agentic Batch Changes during our experimental preview to scope and begin patching a GitHub Actions security vulnerability across their codebase. "I was able to fix it with one prompt on both the Help Center frontend and backend, then extended this to all repos in Mercari. I found around 80 potential repos affected." The thing that made this work wasn't speed. It was the agent's ability to reason about each repository individually. Mercari's repos have similar setups, but not the same setup. A scripted find-and-replace would have collapsed. The agent handled the variation per repo, reacted to CI, and pushed follow-up commits where needed. Canva has been in the preview too, using it to split Batch Changes by code ownership across a Bazel monorepo. This is a public beta. There are rough edges and we're honest about that. But the core capability is working in real customer environments and we're ready to put it in more hands. Available today for Sourcegraph Cloud customers. Free during the beta period. Self-hosted arrives July 8 with Sourcegraph 7.5. Full announcement: sourcegraph.com/agentic-batc…
5
3
26
4,998
Diego Comas retweeted
Today, we're announcing Sourcegraph 7.0, a release that marks the beginning of a new chapter for our company and product. Over the past several releases, we've shifted our focus. We're doubling down on being the intelligence layer that developers and AI agents rely on to navigate, understand, and operate on large codebases. sourcegraph.com/blog/a-new-e…
1
12
6
121
19,127
Diego Comas retweeted
We made Amp Free. It's powered by great tokens and tasteful ads. Agentic coding is now free for everyone.
190
144
248
1,575
897,862
We flipped the switch: Amp Tab is now on by default for new installs. It’s our free completion engine for manual edits in VS Code. It’s fast, knows your recent changes and compiler errors, and suggests cross-file updates when needed. Already on Amp? Run `Enable Amp Tab` from cmd/ctrl+shift+p.
8
16
16
133
91,366
Diego Comas retweeted
We’ve been working with OpenAI over the last few weeks on GPT-5 in Amp. We’re still evaluating where and how to use GPT-5 (after all, it took 6 months to figure out 3.5 Sonnet’s true capabilities). Join us and try GPT-5 in Amp now:
30
22
10
152
17,683
New JetBrains integration in the Amp CLI
10
14
1
104
12,794
Diego Comas retweeted
In this episode, Beyang and Thorsten discuss strategies for effective agentic coding, including the 101 of how it's different from coding with chat LLMs, the key constraint of the context window, how and where subagents can help, and the new oracle subagent which combines multiple LLMs. 00:38 Intros 03:20 How coding with agents is very different from coding with prior AI tools 10:31 Example: fix a simple issue 14:13 Example: debugging an issue with an MCP server 21:50 Example: unifying two build scripts 25:09 How the context window is a key constraint 31:01 Why it's best to focus on one thing at a time 33:09 Subagents and context windows 33:49 The codebase search subagent 38:33 General-purpose subagents 44:05 When to use subagents 46:44 The oracle subagent and o3 51:32 Multi-model agents
1
27
5
147
25,371
Some thoughts on using coding assistants.
4
3
1
38
2,440
Diego Comas retweeted
Heard from someone who found a critical vuln in a popular site using Amp, and another who fought off a DDoS attack with Amp’s help. We want to make Amp great for security and incident response, not just coding: Amp optimizes for quality (not cost), never locks you out at critical times, and has robust (automatic) fallback to Vertex for Claude inference in case of Anthropic downtime, when you might need it most. What can we do to make Amp better for security and ops/SRE stuff?
5
17
1
101
12,526
Diego Comas retweeted
We feel this is the best way to take advantage of o3's powerful reasoning capabilities within your agentic coding workflow. It's not an agnostic model selector, but an intentional application of each model to what it does best.
5
4
2
58
6,172
Finally, finally, finally we have proof on the Amp homepage!
6
5
1
82
7,700
Diego Comas retweeted
Amp: “Whoa. Another S-tier. Holy shit. ... They're devs that love agents and they're just building the best thing."
14
25
7
289
106,413
Diego Comas retweeted
No more waitlist — Amp is now available to everyone!
15
34
14
232
95,933
🤖 Agents. 🤖 Auto-edit. 🤖 Agentic chat. 🕘Available now.
3
14
3
142
27,209
This is the GitHub contribution chart of a CEO. It's that of Quinn Slack (@sqs), cofounder & CEO of @Sourcegraph. Not a typical one: and neither is Quinn, or Sourcegraph. Today's podcast epsiode is with Quinn, and how efficient scaleups operate in 2024: newsletter.pragmaticengineer…
5
12
8
87
70,450
New blog post alert 🚨 Ever wondered how an AI coding assistant works under the hood? In this article, we do a deep dive on how ours (@SourcegraphCody) works exactly!
2
8
40
3,707