Nico Baier
15.9K posts

Nico Baier
@nbbaier
Developer and linguist based in Chicago. PhD from Berkeley. I've also taught at McGill and UBC. I pretend to hate puns but I really don't




I am pretty tired of drowning in Ghostty tabs while running coding agents, so throwing some tokens at it to build a tool in Rust that runs on Linux. It's essentially just Ghostty with a nice workflow to managing coding agent workspaces.

I don't know what the fuss is about. Anthropic's rules on using subscriptions are very simple: Claude Code = OK Claude's online platform = OK Agent SDK running in personal software = OK... ish? Agent SDK running in commercial software = NOT OK Claude Code running in CI = ?? Oh, maybe it's not so simple... Agent SDK running in CI = ?? claude -p running in CI = ?? claude -p running in personal software = OK claude -p running on open source software, but run on my personal computer = ?? claude -p running on distributed sandboxes, kicked off by me = ?? Distributing open source software which relies on claude -p, and documenting how to use your subscription with it = ?? A thousand other edge cases = ?? Let me be clear. I have never before experienced, from any developer tool, such a frustrating lack of clarity over the basic terms of usage. I personally asked, 3 weeks ago, and have received nothing but delays. The recent @bcherny announcement did absolutely nothing to clarify things. I say this as someone who just released a Claude Code course - my incentives all align with supporting Anthropic.

apparently more people like order-n planning. Here's how i do it in a bit more detail. tldr: 1. define a shitty ticket 2. research relevant parts of the codebase + prior art 3. understand and select from the landscape of design choices <-- this is time intensive 4. define a better ticket 5. research relevant parts of the codebase + prior art 6. understand and select from the landscape of design choices <-- this is time intensive 7. assemble a "plan" 8. assemble a plan with code snippets 9. let it rip 10. meticulously read test cases and compiler snapshots 11. go back to 1 with whatever I and agent got wrong. i repeat steps 4-6 until it really works. we're building BAML, a new programming language, fully in rust. and have had high success with 10-20k line PRs that "just work". X wouldn't upload so here's a video that shows more details: youtu.be/8wQBvT6L8Xk


I have also stopped using plan mode It creates a plan FAR too eagerly and usually asks you zero questions en route The whole point of planning is to get on the same wavelength with the LLM, not to generate an asset you don't read /grill-me all the way



Guys, what's stopping you from obtaining this physique?

Can someone explain why the Artemis launch video feeds didn’t look as good as this?


working on the announcement blog, dev docs & API for something coming very soon 📦






