Weerasak retweeted
Ghostty 1.4 is now out! Full Kitty graphics with animation (the first terminal besides Kitty to do it), scrollback compression for much lower memory usage, macOS 27 support, a new OpenGL renderer on Linux, ghostty +ssh, big performance gains, and hundreds more changes.
The highlights:
- Scrollback compression: scrollback compresses ~90+% on average, meaning your terminals use that much less live memory
- Huge memory savings across the board: no single large thing, just lots of good improvements lowers memory usage everywhere, netting anywhere from 50 to 90% less memory usage depending on workload
- Kitty graphics is now 100% complete, including animation and relative placements, after a full conformance pass against the spec and Kitty itself
- The Kitty clipboard protocol, with an image preview when a program asks to read your clipboard
- Split drag and drop on Linux, including between windows
- ghostty +ssh installs terminfo on remote hosts automatically, so things just work over SSH
- Lots of terminal emulation accuracy fixes
This release is 7 months of work from 172 contributors over 2,889 commits. It also fixes 10 security advisories, so please update.
Full release notes: ghostty.org/docs/install/rel…
Weerasak retweeted
JetBrains IDEs are now powered by libghostty! This brings huge feature and performance improvements to JB terminals! Based on their own annual reports, that's over 12.5 million active users across all platforms about to get a libghostty-powered terminal. blog.jetbrains.com/platform/…
I'll repeat myself: libghostty is and was always the primary goal of the Ghostty project (I said this in the first public talk I ever gave about Ghostty). The importance and impact of a free, liberally licensed, high quality terminal emulator library that runs anywhere and everywhere dwarfs any single terminal emulator application on its own.
I've estimated Ghostty's (GUI, not libghostty) own users at around a couple million. Overnight, 6x that are using a libghostty-powered terminal. From one integration.
Happy to see this, happy to hear JetBrains had a positive experience, and looking forward to continuing to improve and ship a stable libghostty tag soon!
Weerasak retweeted
I’m not doing a ton of coding interviews nowadays but I’d be interested to interview how people use coding agents. That itself gives me more signals about candidate’s coding skills.
The coding interview is dead, at least for my team at Anthropic. I've seen enough to know that it no longer provides signal. I removed it from loops this month.
I have a spicy, optimistic take - I think there's an opportunity for junior engineers: felixrieseberg.com/hunger-be…
Weerasak retweeted
“Our Response To The eMudhra Key Disclosure Incident” by Roland Shoemaker, on behalf of the Go Security team — go.dev/blog/emudhra-incident
#golang
Weerasak retweeted
How does Kubernetes or Docker limit CPU and memory usage for containers? They uses cgroups mechanism built into Linux kernel. The following article from @jespinog explains cgroups v2 internals in a clear language.
My article about Cgroups is out.
Namespaces make a container see its own little world, but nothing stops it from eating every CPU core and every byte of RAM. That's the job of cgroups: namespaces change what a process can see, cgroups limit how much it can use.
In this article we explore an example of how cgroups work from the interface, to how is represented internally in the code, and even going through the process of a simple cgroup limit.
You can take a look here: internals-for-interns.com/po…
#Linux #Containers #Cgroups
Weerasak retweeted
Generating code is getting easier. Knowing whether to trust it is the hard part.
Microsoft engineers share how they combine agents, testing, and formal verification to validate changes across massive codebases, including C/C++ to Rust migrations.
commandline.microsoft.com/ag…
Weerasak retweeted
If you want fast performance from VictoriaMetrics, VictoriaLogs or VictoriaTraces, make sure the process_resident_memory_bytes metric exposed by these databases at the /metrics page doesn't reach the memory limit. It is OK if it is close to the memory limit, but you'll see significant increase in disk read IO usage after the process_resident_memory_bytes reaches the memory limit. This may significantly slow down both querying and data ingestion. There are the following solutions:
- brute force solution: to add more memory (increase the memory limit or add more storage nodes in the cluster);
- smart solution: to optimize heavy queries, so they process less data, so it can fit smaller amounts of memory (RSS).
These recommendations apply to other databases, which rely on the OS page cache, such as Prometheus and PostgreSQL, after the container_memory_working_set_bytes metric reaches the memory limit.
See slides from my lightning talk at PromCon EU 2026 for more details - docs.google.com/presentation…
Weerasak retweeted
so many gems and great tips in this talk from @yminsky about how to improve your codebase for agents
• agents thrive on feedback, and types are one of the best kinds
• make illegal states unrepresentable with types, and it enforces global rules across your codebase
• property based tests, fuzzing, and even full-system deterministic simulation testing
• expect tests: just print stuff out and capture it in the test. makes behavior legible. it's very similar to how compilers have fixture tests, it reduces the review surface area
• formal methods used to be very expensive: seL4 is about 8,700 lines of C and took around 25 person-years, with 23 lines of proof for every line of C code, but agents change the roi
youtube.com/watch?v=rUYP4C29…
Weerasak retweeted
Two days ago, I was thinking that we made tooling hard for AI developers who need containers. I built aic, which works like Docker (for now) but will explore composition of images soon. Last night, generated code started to work. It runs things in isolation and copies the workspace etc.
Weerasak retweeted
Today we announce 1Password for Agents platform, building with companies @Muse, SpaceX Super Intelligence Grok @Bot, @AnthropicAI’s @Claudeai, @OpenAI, @TownAI, @Browserbase, @Browser_use, @heydana_ai, Instinct, @usekernel, @Perplexity_ai, @tryramp, @Tomo, and @wajo_ai, with more integrations on the way. 🎉
We've heard from so many of our customers who want to use these new personal AI agents to help them get more done, but want more control over what the agent can access with the same trust and ease of use they get when using 1Password directly.
1Password for Agents gives your agents access without giving up your passwords. When an agent reaches a sign-in form, it requests a credential from your vault. If you approve the request, 1Password directly auto-fills the credential in the destination site so the agent can’t see or take possession of the credentials.
The agent gets the task done, but it doesn’t get your passwords..
You stay in control. 1Password for Agents free and optional for personal and family accounts. Unless you opt-in to an agent connector, agents cannot touch your vault.
➡️Learn more: bit.ly/487da6J
Weerasak retweeted
i've been a bit quiet - working on a new companion skill that will help your agents draw these beautiful statecharts/diagrams + check them against the specs you made with /create-formal-verification-skill in pstack!
it now uses Pele from @kepano too which is why they look so good.
will release soon!
there's something really cool about asking your agent to draw a statechart (hypothetical example in this image), then using the /create-formal-verification-skill you made with pstack to find bugs through something like TLA+. you can both understand your code better and how the user flow should work, and fix issues users would otherwise see
Weerasak retweeted
AI agents are writing more code. How can developers ensure that code is correct?
Microsoft Research’s Proof-Driven Development (PDD) Kit explores a more rigorous approach: it translates a developer’s intent into a formal specification, then uses formal verification to prove that generated code meets it.
PDD Kit works with Verus for Rust and is integrated with @GitHubNext’s Chopin, bringing formal methods into an AI-assisted development workflow for teams.
See the work in action at @github Universe, Oct. 28–29, 2026.
Weerasak retweeted
How do you _guarantee_ your agent's code is correct? You prove it.
Introducing Proof Driven Development Kit (PDD Kit) from @MSFTResearch.
PDD Kit helps turn your plan into a formal spec, then proves the agent's code meets that spec for every input. No vibe verification. PDD Kit is integrated with @GitHubNext's Chopin, so you can plan as a team.
PDD Kit takes an app's login flow from intent to a verified pull request:
It discusses your code, infers your intent as it goes, and proposes a formal spec in Verus, a proof language for Rust.
Once you approve the spec, the Verus verifier automatically proves the code meets it.
Where proof isn't possible, it falls back to empirical verification with tests and computer-use agents (CUAs).
It works on Rust today. No new language, no change in how you produce the underlying code, making formal methods more accessible.
The goal is a verified software factory, where engineers review specifications instead of code.
Come see it in action at GitHub Universe, Oct 28–29. Swing by the Speakeasy and ask for GitHub Next!
Weerasak retweeted
I've never trusted code I didn't review until now.
Agents write more code than any of us can review. We often end up skimming the PR/diff and pushing. Current review methods do not prove the code is correct or does what we asked. Recent research found the best AI code reviewer caught the bug on its first try only 42% of the time.*
The evaluation bottleneck, regressions, and security incidents have forced us to find a better way.
Introducing Proof-Driven Development Kit (PDD Kit) from @MSFTResearch. PDD Kit brings assurance to AI-generated code. You describe what you want to build in plain English. PDD Kit captures your objective, what we call your intent, and uses a verifier tool to prove the code meets it for every possible input.
You never review a single line of the code or the proof. You review your plan and the defined objectives in natural language.
A simple example is login. With testing, you check that only the correct password logs in a user but with a proof on top you can verify that there is no case a wrong password allows login. You can prove correctness and security across many complex scenarios.
Not only does PDD Kit prove the correctness of your code, but also your intent so you can have confidence your code is correct and does what you asked. It provides a level of assurance that specs, code review, and tests never could. PDD Kit is in limited research preview. Video explainer below.
If you want to learn more, I'll be sharing PDD Kit at GitHub Universe next week, Oct 28–29. Swing by the Speakeasy, ask for GitHub Next, and ask me about verified code. If you're in SF, let me know.
*Yang et al., "(When) Should a Software Factory be Lights-off?", Microsoft Research and CMU, Oct 2026
How do you _guarantee_ your agent's code is correct? You prove it.
Introducing Proof Driven Development Kit (PDD Kit) from @MSFTResearch.
PDD Kit helps turn your plan into a formal spec, then proves the agent's code meets that spec for every input. No vibe verification. PDD Kit is integrated with @GitHubNext's Chopin, so you can plan as a team.
PDD Kit takes an app's login flow from intent to a verified pull request:
It discusses your code, infers your intent as it goes, and proposes a formal spec in Verus, a proof language for Rust.
Once you approve the spec, the Verus verifier automatically proves the code meets it.
Where proof isn't possible, it falls back to empirical verification with tests and computer-use agents (CUAs).
It works on Rust today. No new language, no change in how you produce the underlying code, making formal methods more accessible.
The goal is a verified software factory, where engineers review specifications instead of code.
Come see it in action at GitHub Universe, Oct 28–29. Swing by the Speakeasy and ask for GitHub Next!
Weerasak retweeted
OpenAI models helped researchers—operating as part of our Patch the Planet initiative—discover critical security flaws in PHP, an open-source programming language used to run an estimated 70% of websites.
Over the past two months, we led a coalition of maintainers, researchers, and security providers to prepare fixes and protections ahead of disclosure. This duration was necessary because the fix was quite intricate and required a major change to the PHP engine. Every site using PHP can now safely upgrade their version to stay secure, in addition to applying mitigations from various security vendors.
Due to the severity of these flaws and PHP’s widespread use, we consider this bug to be one of the most impactful vulnerabilities in recent memory. It also marks a new phase, where AI can find security bugs with internet-scale impact.
This is an example of the Defender’s Window in action: to our knowledge, frontier AI was able to find this vulnerability ahead of attackers, giving defenders time to prepare.
openai.com/index/coordinated…
Readers added context they thought people might want to know
OpenAI may claim a role in the coordinated response and patching process. But the initial discovery and exploit development, however, occurred several months earlier by an independent researcher.
x.com/lcfr_hax/statu…
Weerasak retweeted
Happy DuckDB 2.0 Day 🔥
It is now officially available in the production install
curl install.duckdb.org | bash
Weerasak retweeted
The 2026 Go Developer Survey is open! Help set Go’s priorities for next year by telling us how you use Go and where it could be better.
⏱️ 10–20 minutes
📅 Open through November 3
blink.qualtrics.com/jfe/form…
#golang