
CEO of @gitbutler, cofounder of @SCNE_io, previously cofounder of @github.
Berlin, Germany
Joined December 2006
- Tweets5.1K
- Following1K
- Followers18.5K
- Likes9.7K
Scott Chacon retweeted
No more scrolling endless logs during Linux boot!
Visualize systemd services come to life in real time.
Powered by @ratatui_rs 🐀
codeberg.org/wvhulle/bootvin…
#rustlang #ratatui #linux
Scott Chacon retweeted
Asahi Linux is moving everything from the MIT licence to GPLv2-or-later.
Asahi is the volunteer project that reverse-engineers Apple Silicon Macs so they can run Linux. In today's Linux 7.3 progress report, developer James Calligeros explains why: people have been using the permissive licence to take the team's work. "In some extreme cases, in-development feature code was being lifted straight out of our personal forks and published without attribution or lazily rewritten with LLM assistance to obfuscate its origin."
The report points to WINE, which switched from MIT to LGPL in 2002 for the same reason: "Those who do not learn from history are doomed to repeat it."
The same report brings real wins too. M3 Macs now install without the EXPERT flag, Thunderbolt support (USB3 and networking for now) is shipping to users, and the team got GTA IV and Fallout: New Vegas running outside the muvm VM using Google's per-process page size patches.
Scott Chacon retweeted
At this point the whole EU Inc negotiations are so lost in the details that everyone forgot the main goal: Creating a standard.
Basically, allow founders to raise quickly globally and use stock options to hire competitively.
Let’s say it quite clearly:
1) If EU Inc isn’t providing a standard it’s useless. We already got 30+ legal entities in Europe. Experienced founders use Delaware Inc already because of this.
2) If EU Inc doesn’t fix stock options Delaware Inc is still the better option.
I understand the there are complex details and people are worried about loopholes. But you can’t lose the actual goal of it because of it.
An EU Inc that doesn't provide a standard is pointless. Nobody will care about intricacies of compromises reached in political committees if the market can't use the outcome.
If you are in contact with your political leaders (prime ministers, presidents, et al) please reach out to them. Or to founders/investors in your network who might have that access.
🔥🇪🇺✌️
teapawt.net/euinc_petition/status/…
Scott Chacon retweeted
Replying to @icyphox
@icyphox is speaking tomorrow at Git Merge at 16:15/4:15 PM (UTC+1)! Tune in for the keynote: the Git forge must be hackable, on the @gitbutler.com YouTube channel.
The (virtual) popcorn is on us 🍿
youtube.com/@gitbutlerapp/li…
Scott Chacon retweeted
The free software movement started with an idea: anyone should be able to make a computer do what they want. AI is making it possible for people who never saw themselves as programmers.
I built keepsake.sh for this new kind of builder.
What would help you build?
Scott Chacon retweeted
Scott (@chacon) constantly improves his screencast game. Of course the topic itself is interesting but have a look at the screencast itself! Just the video. The lighting, the editing, the font size in the terminal. A lot of "small" things which makes them really good. WOW!
youtube.com/watch?v=DsejRSPi…
Scott Chacon retweeted
Replying to @rustacular_com @gitbutler
GitButler is indeed agent friendly but quite good with manual coding as well.
It quite helps with parallel branching stacked branching etc, without worrying about creating and cleaning up the worktree. I’d say AI agents are optional but switching to gitbutler a should have but not must have.
From now on I will reject any candidate using legacy git and not gitbutler (jk) 😜
Scott Chacon retweeted
Finally got into the groove of using @gitbutler for a new project with agents and it is Pretty Great, makes it so much more pleasant to work on more than one thing at a time or like "I have a server PR and a client PR going, but I need them both in my workspace at once"
Scott Chacon retweeted
I told GPT-6 Astra to review Podgagement's code and suggest easy performance improvements, separate each fix into a @gitbutler branch, and run tests on each feature to report speed improvements.
I'm not sure what's going on with Lodash, but I'm happy with these results.
Disclosure: I've never run this kind of prompt on any other LLMs to know how they would handle it, so I can't compare this to anything else.
Today we’re launching Endeavor 1.0, the most capable model we have built @flwrlabs. For me, the most important thing about this launch is not simply that we have another model. It is that Endeavor is genuinely operating at the frontier, while being built around a rather different idea of what a frontier model should be.
We have spent the last few weeks putting Endeavor in front of early preview users alongside models from OpenAI and Anthropic, including informal blind Pepsi/Coke challenges. From what I have seen, they can’t tell the difference.
But the part I am personally most interested in is how we got there. A lot of frontier AI development still follows the same basic pattern. One organization builds the entire system, keeps it closed, and everyone else accesses the resulting intelligence through an API. We started from a different set of principles.
Certain forms of AI capabilities are becoming almost commoditized. Strong open-weight models already provide excellent language understanding, public knowledge and coding ability, so we do not think it makes sense to recreate all of that from scratch. Instead, we build on what the ecosystem already does well and focus our effort on the gaps that still matter at the frontier, adding Flower’s own training, post-training, model integration and capabilities for reasoning, software development and long-horizon agent work.
And we all know by now that a frontier model is much more than its weights. Reasoning effort, context, tool use and recovery from failures matter enormously. We have put a lot of work into those parts of Endeavor as well, developing and evaluating it across different coding and agent environments rather than around a single harness.
The same applies to evaluation. Many public evals are increasingly saturated, so we need signals that reach beyond benchmark scores. Through FlowerBench, we evaluate models on repeatable, high-value work, exposing failure modes that standard benchmarks often miss and feeding those signals back into Endeavor’s post-training and system development.
That is part of what makes Endeavor different. We are trying to show that frontier AI can be built on different principles, including who controls it. You can use Endeavor through Flower or deploy it on infrastructure you control, so the agents, evals, data pipelines and improvement loops you build around it do not have to remain permanently tied to a single external API.
Four months ago we released Lizzy. Today we are launching a model that competes at the frontier.
Frontier AI, under your control.
Scott Chacon retweeted
⋈ GitButler v0.22.0 is out with full support for native @github stacked PRs.
It's the easiest way to get your Claude Code or Codex to fluently stack.
Have multiple agent sessions operate on different parts of the stack in parallel, it 'just works'
docs.gitbutler.com/ai-agents…
Replying to @github
Took us a minute, but stacked PRs are now on GitHub 🥞
github.blog/changelog/2026-0…
Scott Chacon retweeted
The nightly version of GitButler has full support for native GitHub stacks (as of a few days ago).
ngl, agentic stacking with the `but` CLI has never been this good.
gitbutler.com/nightly
Scott Chacon retweeted
Excellent time with @chacon at the @gitbutler office today. Thanks for having me!
Scott Chacon retweeted
Sad none of my "joke" proposals made the final cut.
Ten selected design proposals for the next series of euro banknotes have been unveiled.
Explore the proposals and tell us which ones you prefer.
Have your say surveys.ecb.europa.eu/10b/ec…
Scott Chacon retweeted
just realised that we had ZERO docs on the GB tui - and it is a pretty neat tui if I may brag.
it has a bunch of tricks that the desktop app doesn’t
so here’s the first batch of GitButler TUI docs - docs.gitbutler.com/gitbutler…






























