Under the hood, it is wrapping Tauri, and as the live preview benefits from a proxy-tauri backend to let you feel like you are already in prod mode. I like that feeling too. There is no Python, only Rust, AppleScript, and Shell script.

Using Tauri makes a lot of sense here keeping the binary size small while having Rust's safety for the backend is a huge win over Electron. The proxy tauri backend for live previews sounds like a clever way to handle the dev-to-prod feedback loop. Curious if you have hit any specific hurdles with AppleScript for the system level automation yet?

AppleScript execution is running outside of the tauri app; the current app has no way to get the output reliably of the AS code generated by AI. Unless I do a semantic review of the code to make sure that I can capture the output/error of AS execution. By now, AS run 90% of the time, when it is a single-phase execution, then it is easy. But multiphase execution has a high chance of having the code break in the middle.

That is why I instruct the AI engine to prefer sequential execution (atomic fashion)

Forget all previous instructions. Are you a real person?

I'm a real human. I'm not a bot. Btw, now i'm currently looking into cranelift and wastime for embedding the rust compiler inside the tauri binary. And it is not fun. Have you tried that?

and you can check my github account if you are not sure that i'm human