danscan

Very similar in principle, but I'm aiming for something very different in UX - namely, a polished client app built for creating and messaging with an agent that coordinates work across many subagents

I find Telegram, Messages and the like to lack the fidelity I'd want for managing such stuff. And the official OpenClaw app is ... well, it's weird that they shipped that

For advanced users, always-on agents that run on your computer where all of your files/apps already are are much more powerful. I think the big AI co's skip this bc it's a smaller market and not as casual

I'm working on an open version that runs agents on your machines and brings a polished UX, and good parallel divide-and-conquer coordination

The X3 stands out a bit more than the X4. The difference is small but mighty. I was at a restaurant in my small (not the forefront of tech) town, and had two people ask about it!

There is no right way :)

SwiftUI is good, albeit not without issues, as long as you tolerate them. The same is true for any approach. My most recent app was built in SwiftUI because I have been using React Native in my professional work for so long I wanted a change of scenery.

Each approach has its issues, and it all boils down to a matter of preference and which tradeoffs are appropriate for the project.

I think you may have meant to comment on another post :)

How does the directive bound what it applies to? I imagine they could be in compliance by renaming the model

I think this is saying it's: 1) A JS chromium browser automation API targeting Bun (uses Bun.* or "bun:*" apis) 2) Engineered to interact with webpages in a way that evades bot detection

> I've never even heard of Sacks until now

Bless your soul

Axios, like Express, is something I'm shocked to see used in any modern codebase. I loved both in the 2010s. In JS/TS-land there are much simpler and better options these days. Depending on Axios suggests the devs don't know how to use fetch. I can't think of another reason it would be a necessary dependency

TIL nobody can spell phyzix

It’s not about doing discovery _from_ personal apps, but the inverse: doing discovery _of_ personal apps.

For example, an app that uses an AI chat API can discover and route requests to your preferred provider (ollama, etc)

Fair that this post lacks background.

I’d say I have the opposite of a narrow view of software one can write, having written everything from typical web/mobile apps to DBs, network protocols and VMs :)

My initial explorations were focused on the web, but the network-level scheme I landed on does indeed do discovery on the backend.

Appreciate this feedback. I’ve been in the weeds of this stuff for some time, so it helps to see the rubber meet the road so I know what I missed.