🧪 Juno 4.0 is in beta with a built-in (vibe)coding assistant! Available for both notebooks and scripts, and it's super-fun to use (BYO API key). Juno 4 also brings refreshed UI, faster console—with a lot more coming soon. Ping me at [email protected] to try it. 🙃
🧪 Juno 4.0 is in beta with a built-in (vibe)coding assistant! Available for both notebooks and scripts, and it's super-fun to use (BYO API key). Juno 4 also brings refreshed UI, faster console—with a lot more coming soon. Ping me at [email protected] to try it. 🙃
🤖 Automate Juno with Shortcuts! Create Shortcuts that run Python code or .py scripts in Juno—pass arguments and files, capture output, and chain actions. Run code with Juno in the background or foreground (for full memory access).
Juno 3.6 is out on the App Store, with bug fixes, improved keyboard navigation, and the curl_cffi package, which restores compatibility with recent versions of yfinance.
Juno 3.5 is now live! It adds astropy and jiter (improving compatibility with recent OpenAI packages), fixes several crashes, and includes a few other stability improvements.
@d_arren_ Most likely it’s indeed a memory issue—the OS watchdog kills the app when it consumes too much RAM. I’ll see if I can at least handle this scenario more gracefully though.
@d_arren_ Hey 👋—apologies for a super-late reply, for some reason Twitter doesn’t show this mention to me… Could you please reach out to [email protected] so I can investigate this?
Seriously, this iPad/big iPhone + keyboard setup is so good for when you don’t want to be carrying a large computer around. Here’s the apps I found work the best.
@github codespaces works just fine with the iPad. Meaning you can use VSCode and copilot.
If you want a shell @BlinkShell is great.
@junoapps and @WorkingCopyApp if you want local python notebooks and version control.
🚀 Juno 3.3 is now live on the App Store—bringing bug fixes to the package manager and source editor, adding keyboard shortcuts in the Python source editor, along with other minor improvements and fixes.
@ChiefScientist You can either open individual scripts in Juno, or simply add the checked out repo directory as a file browser bookmark in Juno—in both cases all changes will be saved to the original location, i.e. in Working Copy's file storage where you can commit them. Hope this helps! 🙃