owaislone

This project has been so impressive and exciting. I hope power management is a serious concern once they nail all the reverse engineering and functionality. Battery life would be a huge differentiator for the day to day macbook usage and traditionally Linux has been terrible at that due to lack of proprietary & highly tuned drivers

Good for you. Nobody is challenging what a web app can or cannot do. I love PWAs but services I need every day either don't have a web interface at all, have limited features or are unusable on a small screen let alone having a PWA. This is not about technical abilities but about what companies actually do.

Nothing is stopping you. You're free to use a desktop web app that either doesn't work or is terribly slow or has limited features on a mobile web browser. I'd love it if all apps were PWAs but that is not the case.

Apps. We'd love a completely different OS and it is viable on desktop because web almost does everything but on mobile you're basically locked out of very essential functionality like banking, transit, messaging etc. The compatibility layers aren't good enough (yet) to offer a seamless experience.

Thanks. Just set my shell and all IDEs to this. Perfect!

I check HN a few times a day. Anything I miss is probably not worth it anyway. Never felt I need to "keep up" with it.

Looks so nice. What is the easiest way to use this in ghostty+fish?

Exactly. This is how I design agents as well. I essentially treat the agent as the web/mobile app, cli tool os API library not as part of my backend even though there is where it runs. The backend doesn't treat the agent in any special way. It simply gates all action based on the permissions of the user/guest that is using the agent.

In my experience, Dart/Flutter has been so much better than React. Go has been really good for the backend. Basically if the framework/language gives you structure and one way to do things, agents tend to create less mess with less guardrails from you.

Exciting! Maybe techniques like these can enable systems with 30-60GB memory and very fast SSDs of the future run very large models hopefully.

oh boy

- discuss the plan, dos-and-donts, instructions and have them add it to a PLAN_FEATURE.md with the goal, non-goal, non-negotiables, technical details on the top. - come up with phases to implement your thing. P1, P2, ... P8.. whatever - in each phase add simple one line TODOs with as much explanantion of the task as needed e.g, - [ ] Update DB schema, - [ ] Generate migrations - Ask the agent to go one phase or todo at a time depending on complexity. - if the context fills up, /clear the window and just ask it to do the next line. - if you wrote up all you care about in the plan properly, it'll follow what you need it to do.

Sure - define your project standards in the repo or agent's skill and tell it just that.

You have to treat it like a co-worker send you PRs for review. You review, ask to improve/cleanup stuff and it'll follow up. You can even ask it to remember so it follows the patterns in future. Even better, if you work with it to come up with a design first and then send it coding, you often don't need as much cleanup as the desired architecture is agreed upon early.