Since the first devlog, JishAtlas has grown from a basic AI prototype into a much more complete file organization tool.
llama.cpp.%LOCALAPPDATA%\JishAtlas\models\..env.Scan
↓
Project Detection
↓
Content Analysis
↓
Local AI / Gemini
↓
Organization Plan
↓
Validation
↓
Preview
↓
Apply
JishAtlas has now moved from a development project toward a public release.
Built and refined the official JishAtlas website with a professional product-focused design.
Added:
Packaged the PyInstaller build into an MSIX package using the Windows App Development CLI and Windows SDK tools.
The package includes:
The package was rebuilt after correcting the Microsoft Store package identity and publisher information.
Prepared JishAtlas for Microsoft Store distribution.
Completed:
The first public alpha is available as:
JishAtlas v0.1.0-alpha
The standalone Windows executable is distributed through the official GitHub release while the Microsoft Store submission is undergoing certification.
The next focus is completing the Microsoft Store release, improving the installation and update experience, gathering feedback from early users, and preparing future JishAtlas releases.
I made the links scroll smoothly which was very bad and choppy before, changed the button which were giving some errors in the console and added a nice grid.
I started building JishAtlas with a simple goal: create a tool that can look at a messy folder and suggest a more logical way to organize it.
The first version focuses on getting the core pipeline working from end to end rather than trying to solve every edge case immediately.
The initial AI organization pipeline is now working with Google Gemini.
JishAtlas can provide Gemini with information about the files and existing folders in a directory and receive an organization plan containing suggested folders, moves, and filenames.
This establishes the basic foundation of JishAtlas:
Folder
↓
Scanner
↓
File information
↓
Gemini
↓
Organization plan
The v1 of JishWorks is finally complete! I added the projects and contacts section.
A added a skills section with nice cards along with a about section.
Added a nice hero section.
I made a nice topbar !
I added a maximize button!
I finally completed the README.md and Welcome app, JishOS is now ready to ship! here is the github repo: https://github.com/J1234D/jishos
This was one of the biggest development sessions for JishOS so far. The Python IDE went from a basic code runner to something that feels much closer to a real desktop IDE.
Introduced desktop widgets to enhance the operating system experience.
Features:
Terminal displays Python output.
Color-coded messages:
Auto-scroll implemented.
Fixed several scrolling and layout bugs.
Implemented a lightweight package manager.
Supported command:
pip install <package>
Features:
pyodide.loadPackage()
Successfully tested with:
Added the first version of the Plot Viewer.
Current implementation:
This is considered a temporary v1 solution before moving to a custom renderer in a future version.
Improved the desktop window manager:
Today involved learning about:
Instead of delaying the first release, these features have been postponed to v2:
main.py, main2.py, data.csv, notes.txt)This update focused on making the JishOS desktop feel much closer to a real operating system.
What’s new:
This update significantly improves the overall desktop experience and lays the groundwork for future features like minimizing, maximizing, and window snapping.
Progress Update (Past 2 Days) 🚀
Over the past two days, I built the core desktop environment for JishOS, including:
🖥️ Desktop layout
📌 Top bar
🪟 Reusable window component
📂 Desktop icons
📝 Notes app
🖱️ Custom window dragging system built from scratch using React (no drag library)
Next, I’ll add localStorage support for notes, multiple named notes, improved window management, and more desktop applications.
I made the boot screen! I made this using React JS
Today I completed the design of the top case. I added all the required cutouts, including the Cherry MX switch openings, OLED display window, rotary encoder hole, USB Type-C opening, and the mounting holes. Most of the time was spent adjusting dimensions and fixing clearances, especially around the USB-C port, to make sure everything fit properly.
Note: The Lapse website was offline for most of the day, so although I worked for around 3 hours, only about 30 minutes of the session was recorded.
Time spent: 3 hrs
Lapse: Day 6
Today I redesigned the mounting system to use M3 × 5 × 4 mm heat-set inserts. I updated all the standoffs, added chamfers to make installing the inserts easier, created counterbores for the screws, and rounded the outer corners of the enclosure to give the case a cleaner and more polished appearance.
Time spent: 2 hrs
Lapse: Day 7
Today I finished the enclosure by adding the final colours, refining the rounded corners, and making the last design adjustments. After completing the CAD work, I started learning CircuitPython and wrote a temporary firmware so the macropad would be functional for the initial build. With everything ready, I completed the documentation and submitted the project for shipping.
Time spent: 4.5 hrs
Lapse: Day 8
These updates cover only the final stages of the project. The complete development journal, including the PCB design, CAD iterations, troubleshooting, firmware progress, and the entire build process from the beginning, can be found here:
📖 Full Journal: https://github.com/J1234D/ByteBoard/blob/main/JOURNAL.md
I started ByteBoard after seeing my friend Sunrit Hazra build a macropad through Hack Club Blueprint. The project inspired me to design one completely from scratch while learning PCB design, electronics, firmware, and CAD along the way.
I began by studying the fundamentals of schematic design and PCB layout, creating a simple practice PCB before moving on to the real project.
Time spent: 3 hours
After that, I designed the complete schematic for the macropad, including a 3×3 key matrix powered by the Seeed Studio XIAO RP2040, a rotary encoder, and a 0.91” OLED display.
Time spent: 5 hours
Once the schematic was complete, I designed the PCB, added SK6812 MINI-E RGB LEDs around each switch for underglow, placed the mounting holes, and routed the entire board. After several iterations and design rule checks, the PCB was successfully completed and exported.
Time spent: 8 hours
With the electronics finished, I started learning Autodesk Fusion to design the enclosure. After practicing with a small bracket model, I began creating the case for ByteBoard.
Time spent: 2 hours
I designed the bottom plate, added standoffs and walls, and fixed multiple clearance issues around the USB Type-C connector to ensure the board would fit and remain fully usable inside the enclosure.
Time spent: 7 hours
I continued refining the case design and resolving fitment issues to improve usability and structure.
Time spent: 3 hours
So far, I’ve spent over 28 hours on the project, learning both PCB design and mechanical CAD while documenting my progress through Hack Club Lapse timelapses. The next steps are to finish the enclosure, manufacture the PCB, solder all components, write the firmware, and assemble the final macropad.
Timelapses
I added jso-hello command which says Hello!