timwis

For those interested in this I also recommend autobase, a set of ansible roles for a highly available postgres cluster on hetzner or other clouds: https://github.com/autobase-tech/autobase

Just FYI, those discussions might be ending because your analogy comes across as a threat to punch them in the mouth, rather than because it convinces them.

My interpretation of the concern is that propagate implies that the new value is being pushed out to other resolvers, when in fact those other resolvers pull the new value (once their cached value expires).

I started using this today and am really enjoying the notifications when agents are awaiting input, and the status indicators!

But it feels odd to have it outside of tmux. I've got everything else in tmux, but I have to switch to another terminal tab to get to my agents, and then back to my normal shortcuts. I find that a bit jarring... Is that what other folks are doing?

Can you say more about what it gives you over tmux alone? I've assumed it's just native tmux tabs

Does this mean adding instructions to AGENTS.md saying to end everything with the bell character? Or do harnesses have this in their settings somewhere?

Really interesting! I wonder if using a different communication channel (eg Discord) could eliminate the cost to reply to everyone?

Forgive me if I'm being naive, but can't you just tweak the compaction prompt to differentiate? Presumably that's what you would do in the separate prompt anyway, right?

Can you say more about how this applies to long-running conversations? I've been thinking about them as well, but can't write wrap my head around how this would be better than (or even different to) standard compaction.

I agree. I was hoping for a few positive examples, but didn't see any. The only one I know of is the OIDC discovery endpoint.

Came here to say the same thing. How could the author possibly illustrate the point of the book without at least 4 case studies and a reference to prehistoric humans?

You could also use nsenter if curl is installed on the host, eg

docker inspect -f '{{.State.Pid}}' container-name

# let's imagine that outputs 814538

nsenter -t 814538 -n curl example.com

I've tried most of the tools out there but have used cursor most consistently. Sure, some of the UI quirks get in the way sometimes, but I've found its auto complete predictions to be unparalleled. More importantly, these days I mainly use its Ask mode, Plan mode, and Agent mode. I like that I can use Opus via subscription pricing without Claude Code's wild and buggy harness. And I find cursor's plan mode to perform better than Claude's, but that may just be my personal preferences. I know cursor stopped being the cool thing a few months back, but I genuinely feel most effective with it!

But I'll stop using it now, for the same reason I wouldn't buy a Tesla, or support that maniac in any other way. And I'm sad about that :(

I read this article and was surprised when I reached the end because the whole thing felt like it was setting the stage for some announcement or new thing. But nothing came..? Forgive me if I'm being thick but what was the takeaway?

Dark Forest theory, anyone?

For real this time...

I think that only applies to the messages app

We have some enterprise customers who require all data be processed in the UK or AU. We've been limited to using Azure OpenAI, which only has older models in those regions (eg 4o, 4.1-mini). I was hoping we'd see the newer models in those regions once they got to AWS, but it looks like the newer models are only available in the US at the moment :(

Rails has several database-backed job backends, but the convention is always to make jobs do one thing, and ideally be very short-lived. This makes building workflows a bit contrived: we end up enqueuing the second job on the last line of the first one, enqueuing the third one on the last line of the second one, etc. The job backend treats these as independent jobs rather than showing them as a connected workflow, and you have to read through a bunch of job classes to wrap your head around the workflow at even a high level

Rails recently introduced a 'continuable' concept, allowing you to checkpoint and resume steps within a job, but it still feels like the convention is too keep jobs with a single responsibility, so it feels odd to use them for true workflows.

Has anyone else experienced this or found a solution to it?

I've just spotted Opus 4.8 in the list of models available on claude!

Different harness (pi), but this blog post may partially answer your question: https://mariozechner.at/posts/2025-11-30-pi-coding-agent/

Ooh, that's clever. Thanks for sharing.

That looks interesting, but unless I'm missing it, it still leaves you with things like ~/.aws/credentials in plaintext on disk, doesn't it?

Love that feeling when you read through a repo and think, "Wow, this looks cool," and go to star it, and see that you already have, and clearly forgot about it

Anyway, thanks for sharing. It doesn't look like it handles cli auth though (aws, npm, etc. all leave tokens sitting in your home directory). What do you use for those?

What do folks here do to avoid having plaintext credentials on disk? I try to use 1Password's plugins where I can. I find the SSH key (and got signing) experience flawless, but the cli experience (eg aws cli) pretty clunky - they often break, and they don't even have a gcp plugin last I checked.

I wish an alternative to JS for the front end would catch on and be something more than obscure... I'd love to use something like clojurescript, but I struggle to imagine doing so for anything but a personal side project :/ Maybe this is easier to adopt if you're already a clojure shop for the backend?

I've had some incredible product ideas while asleep, down to very intricate technical detail. The problem has been that when I wake up, reality kicks in, and I realise that, say, even if I built that incredible messenger app for dogs, they still wouldn't be able to communicate with us.

Really sad to see this. I had only recently learnt about this project, and was really impressed by it. I was planning to set it up this weekend (via autobase). I've also been under the impression that it's likely to be what powers the backups in RDS, Cloud SQL, etc., but I may have misunderstood.

I wondered the same! FWIW I'm currently migrating from managed postgres to self-managed on hetzner with [autobase](https://autobase.tech/). Though of course for high availability it requires more than one server.

We've started calling it dopus at work :(