@Mofedul Alam Joy Thanks for the reply! I tested your suggestion, but I still don't think it is simple enough for non technical users. Ultimately, it doesn't feel much different from using VSCode. Since I have a tech background, this setup is easy for me, but for them, it is still too complicated. I have a much simpler solution in mind, but thanks for the idea anyway!

@Brennan Cheung Hi! Answering your questions: 1 - I thought of a local app running Electron or something along those lines. 2 - They would use this app to: - create articles - handle PDFs - run other workflows using ICM - manage ICM workflows - "the whole package" 3 - Skill level: From an electrical engineer who teaches IT, to a teacher who really struggles with tech. But they all know what a file or folder is. 4 - I want to teach them to create their own ICM workflows. At the very least, a cleaner way to configure and use these setups. I hope that answers your questions :) The summary is this: what I had in mind is practically the same thing that Jake created in his SaaS, but running locally, look at this: It would be a local app where: - A home page where the user can: - create new workflows - see all ready-made workflows listed - open an existing workflow - Upon opening a workflow: - they see: - file management - a chat panel - easy access to edit files. Since I work a lot with content creation, having an editor with easy access helps a ton. With a panel like this, users could build anything using ICM. I know that the desktop version of the OpenCode app has almost everything, almost: it is only missing a file browser and a built-in editor. Right now it only lists conversations, and the "file manager" is just a diff output that you cannot edit. I also tested T3 (https://t3.codes/), but it also has the same problem of not having an easy way to edit files. The system Jake built is easy and simple. A local version of that would be a dream! Maybe it is a bit of an ambitious goal, but an interface like this would make even my life here a lot easier.

READY

@David Vogel I thought of a quick move to help solve this problem while you guys are building the AI system, and to cut down on onboarding support requests in the meantime, what if you create a visual map as a JPG or PNG, desktop wallpaper size, styled like a Monopoly game board? Each major space on the board would be a specific step for the student to follow. This would help beginners visually navigate the content and orient themselves right away. Does that make sense?

Congrats on the presentation, it looks really cool! Just a quick heads up, if you are going to use this to pitch to actual clients, consider buying a custom domain. Sending a pitch with a URL like this can look a bit sketchy, to the point where clients might think it is a scam. Since you work with digital transformation, having your own domain is definitely worth it.

@Pedro Costa hmmm got it.

I like to keep things simple. Here is how I structure my thinking: 1. Break the task down into smaller, manageable pieces. 2. Create an ICM stage for each piece. 3. If a stage needs to perform a highly repetitive, technical task, decide between: - A Skill, if you need a specialist to do something for you (e.g., a skill to evaluate if your web design actually "smells good" / looks clean). - A Script, if you need a strictly DETERMINISTIC result (e.g., generating a PDF report with a predefined design using HTML + Python). Now, when it comes to clients, always remember: **It doesn't matter what color the cat is, as long as it catches the mouse.** Clients don't care how your folder system works under the hood. They just want to know the bottom-line benefits of using it. My key selling points to pitch to a client are: - No vendor lock-in: you can use Claude, GPT, or any other AI model. - You own the system: if your developer disappears, you aren't left holding the bag. It's on your local drive. - Token economy, it’s way cheaper to run structured stages than going "Wild West style", throwing a giant, messy prompt at the AI and hoping for the best. - Fully auditable, everything is written in plain, readable English. - Open standard, anyone with basic tech skills can jump in, make modifications, and improve the system. At the end of the day, clients only care about two things: 1. How it makes them money. 2. How it saves them time. Keep your conversations within those two parameters and you’ll do great. If you ever get stuck explaining things to a client, just remember the cat. ;)