Git 2.56 is here. ⚡ The new git add --resolved stages only paths that are still marked as conflicted, and refuses to stage them if conflict markers remain. One merge-base case dropped from 0.68s to 0.01s.
The highlights 👇
https://t.co/CxbNfofYrf
Cool it on the tab hopping 🐇
Reviewing agent code usually means switching tabs. The GitHub Copilot app puts the diff, terminal, and browser side by side to check, run, and preview.
https://t.co/NCWK8hUeFf https://t.co/Mi6tyyCDs4
We'll be spending a lot more time trying to understand the outputs of language models. A few thoughts, tips & tricks:
Writing. Something I've had success with: Ask your LLM to explain something in ASD-STE100, it's a controlled language specification originally developed for aerospace maintenance documentation. LLMs well-versed in this language and it comes with heavy constraints on clean writing style that I often find a lot more readable. Sometimes I've tried to soften it a bit e.g. ask for "80% of the way to ASD-STE100" because the spec is quite stringent. But even better:
Diagrams / images. Instead of writing, ask your LLM to create a diagram. These can be a lot easier to process, parse, and understand. But even better:
Web pages. Ask for output "in HTML" to get a beautiful, interactive webpage. LLMs are getting really good at frontend and can create beautiful experiences, animations, etc. But even better:
Explainer videos. The output format I am most bullish on is fully custom / bespoke explainer videos generated on any arbitrary topic. Experiment with things like "Create a 3b1b style video explainer on X. Use my ElevenLabs API key for audio narration". (you'd need an API key for the latter or you can ask your LLM to find you decent free alternatives that use your local compute). This is actually starting to work!
In summary:
- As LLMs get better, they will do more and more of the legwork autonomously, and a lot more of our work will rise up the abstractions into oversight and understanding.
- Luckily, LLMs can help here too because as intelligence and code are increasingly abundant, you can ask for large, custom, discardable software artifacts (e.g. web apps, video explainers) that would have never made sense to create before. Push the boundaries here and you'll be surprised.
Cool eval. Simply ask an LLM “Land or Water?” and give it a latitude and longitude coordinate as text. Ask 16,200 times, plot as image. The models know. From compressing the internet.
When Rollouts catches a regression, it finds the offending PR and opens an issue. One click starts a cloud agent to fix it.
Rollouts usage credits are included through Oct 3.
Jev is now in the AI SDK for Python.
To test it, we ran two experiments:
▪︎ Detecting Python vs. English as text is typed
▪︎ Writing Python, one decision at a time
𝚞𝚟 𝚊𝚍𝚍 𝚊𝚒
https://t.co/fWPx6k3Gw3 https://t.co/eLaAvdzGdS
It's time to get serious about Security x AI.
One of the joys of doing AIE is helping others start their own high quality conferences in their countries and domains. Every single 2025 partner has come back — and the 2nd AI Security Summit is now way more important than before. Proud to be back as a founding partner with @snyksec!
Join the event: https://t.co/2IeM4a3MGO
The landscape has completely transformed since we started this a year ago. An exploding number of rogue agents, more breaches, more AI-driven attacks. now more than ever, security must be at the center of the AI conversation. With so much more hacks and vulnerabilities, this stuff is no longer theoretical...
🐾 Meet Blobby, the VS Code Pet!
Thank you to everyone who submitted a name and helped us choose our new coding companion. 💙
Want to code with Blobby by your side? Open GitHub Copilot Chat in VS Code and enter: /vscode-pet
🏆 We’ll be reaching out to the contest winners directly with the next steps.
Welcome to VS Code, Blobby! 🐾✨
Engineers at @RogoAI build the company's internal apps on Vercel. They deployed over 73,000 times last month.
Coding agents ship to production in 5 minutes, and run everything from churn risk analysis to the sales team's deal desk.
https://t.co/PO07A4nDc3
Validate agent fixes before shipping them with LangSmith Engine v2.
Engine now tests and validates fixes automatically:
✅ Replicates the issue with the same deployment environment and same inputs
✅ Builds a fix, tests it, and iterates on improving it until it has a satisfactory solution
✅ You review the fix and deploy it with a ready-made PR
💻 Build the interface you want w/ your LangSmith data
✅ Publish it into your workspace
🙅 Skip hosting, auth, + permissions work
Get started with Custom Apps today.
https://t.co/MayBpUbhnW
The BEA's new Q2 GDP-by-state was released, but the key data is entirely in an infographic, without a text-layer.
LlamaParse's agentic parsing tier understands documents like this by default, and faithfully records data, turning the page into a 52-row table.
Source: https://t.co/0sBhstAIhM
Scope agent memory to a single user or your entire team.
Managed Deep Agents now supports user-level memory out of the box. Set it up with one file and deploy with a single command.