threecheese

My suspicion is that Herdr will go this way with the YC relationship; they are keeping the runtime open source - the thing their terminal UI is built on- and there’s no reason cli needs to be their only target. Your app is very nice looking!

Am I weird or old-fashioned for relying on direnv over .env? These days my projects use a lot of different tech, and it just feels weird to me to have them all parsing .env files and hoping everything works. Especially with inference provider tokens basically connecting my checking account to the internet.

Cool cool. Could you use Apple FoundationModels to simplify the big honkin shell script? Might limit the distributability (needs modern Apple Intelligence), but those pid check could be few-shot examples in the swift codebase. This thing could be wildly useful and you wouldn’t need to update your shell script for every new tool.

As far as I know they terminate all TLS; it’s one of the tradeoffs using them.

There must have been some recent push; our $bigco SEO/GEO group just gave a demo of how to use Reddit for user research. It surprised me, it’s like the FDA recommending 4chan for product safety guidance.

Ah, another banger from InsighTits.com; thanks for all the joy you’ve brought to the world!

- sincerely, Therapist

I was accurate?? Holy heck. FP makes my brain go numb.

Ok, this is Interesting. It took me some time to figure out what the heck it was, given the documentation was either written by AI or a galaxy brain functional programmer. I’m gonna take a crack at summarizing it, in normie form: - A tool is provided which executes some user-defined workflow graph with the goal of provisioning infrastructure, using opentofu and Ansible.

- It does so by providing a library and CLI which is labeled “idempotent”, and I think I saw the term deterministic in there as well.

- That cli is built using Clojure, and there are also python and typescript implementations: these are named “green”, “blue“, and “red” for some reason.

- (the interesting part) The library ties together some Clojure/Datomic-isms (EDN graph to define the infra state, and the template library Selmer), some Emacs-isms (advice, to wrap nodes in the graph to add behavior), and some UNIX-isms (exit codes for graph steps) which is all used to implement graph execution in an environment where you may need parallelism, conditional fanout, failure handling etc because you are provisioning real things in real life and there are many unknowables.

TFA documents additional agent skills designed to use the tool for provisioning/managing some specific infra stacks (like zookeeper plus whatever). Which is the least interesting thing about this.

If we want to be pedantic, we could say that your automation is like a particularly aggressive DoorDash driver; runs into the store, grabs all items as fast as possible, and is perhaps rude to the checkout girl on the way out. And if you scale this to checking N vendors - and only buying from one - you fall right into the bad behavior.

I’m not sure if your bot is like this, but my understanding is that many of them are - and they interfere with the other shoppers and generally change the economics of it.

I think you are on the right side of this, but you are almost indistinguishable from the negative case.

That’s not all you need to do though; once you have bought all Cable Matters or Anker cables, you still need to remember which one charges your iPhone quickly, and which one is thunderbolt-capable but missing the lightning bolt, which one is charging-only, etc. I have a whole mess of cables - and several of these dongles (you need a usb-a capable one, and only that other one reads thunderbolt markers, etc). I spend the time to label any cable that I buy myself, and wish the vendors would do it instead.

From reading TT, it seems there’s just no easy solution to complexity if we want interoperability.

I didn’t hate lightning cables…

You’ve enquoted “Palantir taking your data” as if it’s not factual, but the only one with data privacy guarantees here is USA Today.

You can’t “convert the sheer scale of our audience into known, orchestrated first-party relationships” without compromising your privacy.

Moshi has an integration with Herdr; you can connect to your herdr sessions over mosh, your touches register as mouse clicks in the UI (which is minimally rendered above the shell), and there’s a shortcut bar which can issue herdr-keymapped commands.

It’s not open source, and costs a few bucks, but it works well and has live Claude/Codex/etc notifications if you are willing to install a hook daemon on your hosts with homebrew. I was looking for batteries-included “code from my iPhone” after trying a bunch of self-hosted stuff, now I connect to my Macs over Tailscale and get dropped right into multiplexer sessions with rich status notifications.

https://getmoshi.app/

Reserved! I would have paid the 249 today btw :) she looks beautiful.

I’ve been adding a “terms” section to every AI-used project due to these hallucinations. We abbreviate our company name eeeeverywhere and even Opus gets this wrong constantly. Obv I’m not adding “YES==yes” but that’s hilarious!

Nobody wants to say “Hey Nabu” though ;) Including me (and I bought one of the things)

Any comments on how you’re holding it? Just “Hey Claude use htmx”?

Same. I’m starting to believe that consumers need to own the UI/experience, so we can install blast doors around context/memory for each “slice” of our lives - something only we can know how to divide (imo). If the provider tools’ memory implementations can’t provide this multi-tenancy - or won’t because they want to Know Us, then we need to treat them as token vendors at best and adversaries at worst.

This would actually work very well - until context goes into latent space, becomes a server-side resource, and we lose sovereignty over our data. Tools like Pi and Openclaw are showing that other options exist to decouple us from the LLM provider frontend experiences, not just for orchestration and use case diversity but for pluggable memory designs.

They are imo over-relying on Claude automemory here, which is terrible at contextualizing memory access and makes huge leaps that don’t make sense - except when it’s actually useful, which makes the problem even worse for an operator who can’t see the thinking process anymore.

Yes, I worked on a related project, no I don’t want you to use those memories to make assumptions which emerge as decisions that I didn’t want. With reasoning traces hidden, I am sometimes not even sure if it used those memories or just independently decided that PCI-DSS subsection-whatever is somehow relevant to this PR that has the word “credit”.

There is no way for me to fully configure memory preferences at a granularity which would be useful, and so I continue to use context files (and other tools, sometimes) to ensure the right memories are stored and surfaced at the right times.

There’s a lot of room for agent memory improvement across the ecosystem, and I don’t think the LLM providers should try to own this vertical slice. This will never happen though, because it makes us “sticky”.

Or maybe I’m holding it wrong.

tl;dr - I really like your products, but just don’t have the cognitive resources for many learn->try->decide->use loops, and I don’t think I’m alone here. “Claude, use the sprite skill” is the vector of adoption which matches my mean available energy. —-

Some feedback on the pivot, from a user. Reading through the recent blog entries, there’s some Very Neat Stuff mentioned that integrates Sprites into tools like Hermes. I excitedly dug right in, to find that they aren’t anything usable, and the Hermes PR needs work. More salient though, that months-old Hermes PR *needs attention* if this is now your #1 business priority. Same goes for umpteen other integrations to shove the Sprites model (which is unique) into the popular agent harnesses.

I tried Sprites when sandboxes were peak exciting, and “yes I can ssh into this and run Claude” was useful but not groundbreaking. From the docs I’ve just read, I was holding it wrong, not taking advantage of its differentiating features. Great, ^H ooh look, mythos, shiny … and now it’s almost August.

And so honestly - despite my appreciation of Fly - with the firehose of Cool Shit, I don’t have the time or the inclination to learn how to hold it. Instead I want a skill/plugin/integration/llms.txt/sumerian tablet that I can give to my LLM to do that “multi-user auth and don’t worry about it you’ve got checkpoints” stuff for me. And I need this before I make any choices about investing in this thing over Bubblewrap or a VPS or the 100 other frictionless zero-knowledge sandboxy things that I am using already. Maybe you have this, and this is PEBKAC. Wouldn’t be the first time.

I’m not looking forward to our customer service future.

I called my window contractor this week, I need new skylights. Instead Janet answering, they now use an AI operator-lead-generator thing.

After a few of minutes of answering questions, I just hung up. I’m unsure why, I don’t miss Janet or even genuinely like talking to people, and Im definitely not anti-AI. I just intensely disliked the experience, enough to walk away from a vendor with whom I’ve done tens of $ks in business (I found another window guy).

Apnea sufferer here, for whom cpap stopped working after weight loss. It turned out that my mouth was opening during sleep, reducing the effectiveness of cpap, and after adding a chin strap to keep my mouth shut I have had very few apnea events.

The mouth-tapers aren’t always wrong (though we do always look silly).

I’ve relied on iCloud as well, but just learned that it allows apps to store persistent data. This data is synced between all devices, and there’s no way for you to view or manage/delete it. Even determining which apps do this requires you to enumerate the apps entitlements, which is nontrivial. And so an app you install on your iPhone can have configuration or credentials persist to each iCloud-connected device, and you have no control over it. This is certainly convenient, if that’s the behavior you want; if not, there’s no visibility or control.

I worry about this from an access continuity perspective; if a query like this caused my access to Claude to be revoked, it would affect my livelihood. Coupled with the new rigorous identity verification, you risk not being able to get replacement accounts - they don’t ban your username, they ban you.

For this reason (and others) I pay for both Team and Personal LLM plans, use a diversity of them for specific purposes, and use some LLMs very carefully; if I were to lose access to Gmail for Gemini wrongthink, it would be personally devastating.

Did you use generative AI to design this? Superpowers plugin? This is cool, but if you did use AI that’s another level of cool :)

https://github.com/markomarkovic/nena-ilo-lili/blob/main/doc...

This presumes that they won’t maintain those, which would be a valid choice to maintain PayPal’s market penetration (if that’s the goal). Diverse offerings etc

It must have been removed, given that the initial evidence of the exfil specifically demonstrated .env files being included. And .ssh/* for the user which ran this in $HOME.

I’d like it if my leadership stopped using load-bearing, and others like “shape” and “estate”.

In the past, when you saw a new term of art it came from some book being passed around leadership (like Architect Elevator) or some new training program. “Platform mindset”, “Shift-left everything” etc.

These days, they are all coming from LLMs. You can probably infer which contracts we have from the wording of all-hands messages.

I even LIKE “shape”, it’s nice and generic and everyone immediately understands it. I just see it as an obvious low-impact brainwashing, and wonder what other effects there are that we don’t notice.

That’s the fault of the SEC EDGAR tool. The Edgar MCP docs show setting an env var: ‘SEC_EDGAR_USER_AGENT="Your Name (name@domain.com)"’.

Claude just followed the instructions. Which is maybe even more risky?

The LibRedirect link in that post is 404

Same question, same scenario. I tried it on MacOS, and the first issue I experienced (don’t recall what it was) had me deep into Redhat forums to even understand what was happening. Switching to OrbStack was a no-brainer, but there are obvious tradeoffs from a features perspective.