Diego Comas

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-era…

Big news! Sourcegraph & @AmpCode are becoming two separate companies. Read why: sourcegraph.com/blog/why-sourc…

I use Deep Search all the time, and it helps my teams onboard faster, investigate issues, and find what we need across the codebase in seconds. Huge productivity boost.

We made Amp Free. It's powered by great tokens and tasteful ads. Agentic coding is now free for everyone.

Add this to your workflow! Early detection of dependency issues will definitely reduce headaches.

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.

@matthewdfuller Sounds like a Mission Impossible scene, love it! but not sure if the holidays were as chill as you planned!! Respect! 🤣👏 I hope they didn’t ask for the Cloudformation code too, right?

So I’m standing at the back of this boat, bouncing, can’t hear jack, trying to debug how to create a cross account IAM role. Miraculously, we get it working.

I was catching up with my old cofounder from CloudSploit recently and was reminded about the time we closed our biggest customer (and arguably the deal that put us on track to acquisition). Looking back, the whole series of events was pretty wild…

VS Code blocked this malicious extension quickly, but in an alternative marketplace (Open VSX, used by forks like Cursor/Windsurf) it still hit 54K+ installs. A fake “Solidity Language” highlighter, it was malware stealing $500K in crypto. Vetting extensions and their sources is just as critical as securing the code we write.

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:

New JetBrains integration in the Amp CLI

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

Some thoughts on using coding assistants.

@rockorager @Sourcegraph @AmpCode Welcome!!

Crazy excited to join @Sourcegraph working on @AmpCode!

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?

Excited to join the upcoming State of DevSecOps 2025 livestream hosted by @christophetd and organized by @datadoghq, with Clea Ostendorf and Fred Blaise. Learn the latest insights on modern DevSecOps practices pulled from real-world organizations. At @Sourcegraph , we have seen how these challenges evolve when you are building AI-powered tools like @AmpCode and supporting a fast-moving global engineering team. I am looking forward to sharing what has worked for us and hearing from others in the thick of it too. 📅 Live on July 15 🔗 Register here : datadoghq.com/event/devsecop…

@rez0__ So we’ve reached the stage where prompt injections are the new SEO keyword stuffing… but for research papers. Just sprinkle the right prompt to get noticed or approved, even if the paper isn’t that strong 😅

People are putting prompt injections in their research papers

@GergelyOrosz @fnthawar @Pragmatic_Eng Makes sense to me! Using AI tools can really boost productivity. If that’s how the team works day-to-day, then the interview is a good place to see how candidates adapt to new tools and ways of working. It’s not just about skills, but also how people stay up to date.

Shopify doesn't ban using AI tools in their interview process: they encourage it! From @fnthawar in a live podcast with @Pragmatic_Eng:

@FeifanZ @zain_hoda @AmpCode @Sourcegraph @zain_hoda we move fast but also what @FeifanZ said! We have a great platform with secure foundations that we were able to leverage!

@zain_hoda @diegocomas @AmpCode @Sourcegraph i imagine they have most of the basics in place from Sourcegraph already

. @AmpCode is now SOC 2 Type II certified! ✅ Enterprise-grade security from the start — zero exceptions, strong controls, fully audit-ready. 🛡️ This adds to @Sourcegraph's ISO 27001, GDPR, and CCPA compliance. We’re building secure, scalable AI from day one. 🔐 Learn more → ampcode.com/security